- General Development
- Schema Development
- Apex Code Development
- Visualforce Development
- Formulas & Validation Rules
- Force.com Sites & Site.com
- Chatter Development
- Java Development
- .NET Development
- Perl, PHP, Python & Ruby
- Desktop Integration
- APIs and Integrations
- Visual Workflow
- Apple, Mac and OS X
- VB and Office Development
- AppExchange Directory & Packaging
- Salesforce Labs & Open Source Projects
- Other Salesforce Applications
- Jobs Board
01-02-2013 02:17 PM - edited 01-02-2013 02:18 PM
I'm now getting this same error as well. I use the connector daily including this morning and it worked fine. I do not see any login errors to my instance, just successful logins. I've tried adding my token as well with no success.
01-07-2013 08:16 AM
Now this one really has me foxed. I'm using the Excel Connector to query a custom object Purchases__c which is related to Contacts. The excel connector returns the 5103 error only when certain fields are selected. I don't get API errors using other tools for querying like Jitterbit or DataLoader. I'm at a loss why the excel connector fails on certain fields where the other tools don't.
01-24-2013 10:54 PM
I'm also having the problem at the end of several days of extensive Excel Connector usage without a problem. The problem is probably not with the Excel connector code as the reported error is actually coming from the Salesforce.com servers. The temporal nature of the problem could point to a transient problem on the servers or some change to the underlying Excel software triggering a problem after extended usage.
If I had to guess though, I'd say there's something not right with the APIs on the server side. I don't know if it's just the older APIs as I only use the Excel Connector. I don't think anyone has reported this error with the Data loader as far as I can tell, which suggests it is the older APIs that are problematic.
Salesforce.com only officially commits to supporting the current API version and two older versions. That said, given the significant number of Excel connector users and the absence of any equivalent replacement, the older 13.0 and 16.0 API versions would still be actively used as a result; they should see this in the API usage statistics. Hopefully someone on the server-side just accidentally broke it and it's an easy fix.
02-26-2013 01:16 PM
I think amen-intech is right. When I attempt to query and get an error (which doesn't happen all the time but still does periodically) I usually get a link in the error message, something like https://na14-api.salesforce.com/services/Soap/c/16
If I try to go to that link, it's often an error saying
HTTP Error 405
Problem accessing /services/Soap/c/16.0/[INSERTIDHERE]. Reason:
GET not supported
Salesforce must be messing with something creating this result....
02-27-2013 05:39 PM
Also you can turn on API names and see if there this will allow you to see if duplicates are present.
I suggest trimming down to something very simple like
and see if this works, then add back columns one or two at a time and you may have luck if the problem is duplicate column names
03-04-2013 10:40 AM
I reset the internet explorer settings and it fixed the problem for two different users. Windows XP, IE 8: Tools > Internet Options > Advanced > Reset
Hope this helps!
04-04-2013 04:20 PM - edited 04-04-2013 04:24 PM
I am getting the same 5103 error. I receive the error not on login but upon querying the table. The error is followed by an error thrown by the Salesforce Excel Add-in stating No data returned for this query.
The funny thing is that I can query from the Accounts table with no problem. It is only when I query Opportunities that I receive the 5103 error. The error renders regardless of which server I am connected to. I have also played around with choosing which fields to display, which filters to have, etc. It does not appear to make a difference whether they are standard or custom fields that I display or filter. I have also tried playing with settings in Internet Explorer as the previous user mentioned.
I am pretty bummed because Opportunities is the only thing I report off of. If anyone has any tips it would be greatly appreciated.
Edit: I have been using 32 bit Microsoft Excel 2007 with the addin. I previously installed it with Office 2010 (tried both 64 and 32 bit versions. I have also tried password + security token versus just password and log in both ways no problem. If I can get this working it would save me 20 hours per month!