function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
sf@143sf@143 

UNKNOWN_EXCEPTION: An unexpected error occurred.

Hi,

I am using Tooling API in C#.net. When using login() method i am getting below error.

UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1084601297-62065 (1318667741)

 

is their any one already face same problem and fix it. Please provide solution for this.

 

 

KrishSFDCKrishSFDC

Hi,

 

What your receiving is an unhandled / unexpected exception from Salesforce. Only Salesforce support can decode internally the error message behind it and hopefully give you a clue as to what might be going wrong to cause this. As its unhandled / unexpected its likely you've found a bug of some kind. However its also likely the correct passing of information can be found once more is known, as I suspect this a issue in the API's internal validation code. As the message says I would contact Salesforce support and provide them with the codes.

 

The below link might help you.

http://salesforce.stackexchange.com/questions/5187/why-would-this-chatter-rest-api-http-post-return-a-500-server-error

 

 

Thanks

Gopi

DBSync LLC

www.mydbsync.com
sf@143sf@143
did you fix the problem
KrishSFDCKrishSFDC

I am sorry. didnt get your question. I could not have fixed it from my end.

 

Thanks

Gopi

DBSync LLC

www.mydbsync.com
sf@143sf@143
above article shows regarding the chatter but i am using Tooling API wsdl file. if you have solution please provide.
JCripeJCripe
Through a Premier Support case submitted in mid December, I learned there is a bug with SOAP logins in the Tooling API.

This is the quote from SF support: "Currently there is no date scheduled for the fix, but here the bug number for your reference is: W-1895722"
JCripeJCripe
I got word that there is a new "Known Issue" for the bug now so you can track it's resolution: https://success.salesforce.com/issues_view?id=a1p30000000T2GcAAK
JCripeJCripe
Please raise the priority of the fix with Salesforce support by clicking the "This Issue Affects Me" button when you go to the issue: https://success.salesforce.com/issues_view?id=a1p30000000T2GcAAK