xhiena / excel-connector

Automatically exported from code.google.com/p/excel-connector
0 stars 0 forks source link

Exception Code 5103 Querying Table #81

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Describe Table
2. Select fields and query criteria
3. Activity fails with internal server error and Exception Code 5103

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?  With
what Salesforce.com edition?

Please provide any additional information below.

Original issue reported on code.google.com by swbueh...@gmail.com on 21 Jan 2013 at 5:46

GoogleCodeExporter commented 8 years ago
this appears to happen if there are duplicate fields in the query.  try just 
constructing a query with 

Account
Id, Name

if that works, then add one field at a time to get the desired results.

a future fix will be to check that there are no dups on the actual query that 
gets sent to Force.com

Original comment by vneh...@gmail.com on 28 Jan 2013 at 5:16

GoogleCodeExporter commented 8 years ago
Thanks for this hint, I wonder how a field becomes a duplicate field?  Keen to 
see a fix for this.  PS love the connector and couldn't lve without it!

Original comment by 123goodg...@gmail.com on 14 Feb 2013 at 2:19

GoogleCodeExporter commented 8 years ago
with the duplicate fields... you may have the same label name (for different 
reasons).  You may want to change the setting under the "Use Names" tab to use 
the API_Names.  This may help.

Original comment by jbvi...@gmail.com on 26 Mar 2013 at 3:45

Attachments:

GoogleCodeExporter commented 8 years ago
Hi,

I've the same problem even when I check "Use API Names".
I've two fields:
- one named "Name" with "Name" as label...
- one named "MyAppli__Name__c" with "Name" as label

Thanks for your help.

Original comment by fb011...@gmail.com on 12 Jun 2013 at 3:59

GoogleCodeExporter commented 8 years ago
We were getting this 5103 error and it turned out our network crew had made 
many changes to our firewall.  They said they "whitelisted" the salesforce.com 
url for the specific IP addresses that require Salesforce Connector, and that 
made this issue go away.  

Original comment by e.joseph...@gmail.com on 10 Sep 2014 at 1:40