function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
JasonRogersJasonRogers 

Trouble calling back into Salesforce from API

We have a situation where we use a custom link in Salesforce to call our servlet. Within that call we send the userId and the sessionId. The following code was working this morning in the sense that we were able to get user information, but starting around 5:00 PM EST today (March 15, 2004) it fails with the following exception stack (below the code snippet) when calling "binding.getUserInfo(sUser);". Any clues? Did something change in the API?

[code snippet]
try {
SoapBindingStub binding = (SoapBindingStub) new SforceServiceLocator().getSoap(new URL(sServerURL));

_SessionHeader sh = new _SessionHeader();
sh.setSessionId(sSessionID);
binding.setHeader(PARAM_SFORCE_SERVICE, PARAM_SESSION_HEADER, sh);

GetUserInfoResult userInfo = binding.getUserInfo(sUser);

if (userInfo.getUserEmail().trim().length() > 0) {
return true;
}
} catch (...) {
}
[/code snippet]

[exception]
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader
faultActor:
faultNode:
faultDetail:
{urn:fault.enterprise.soap.sforce.com}fault:
INVALID_SESSION_ID
Invalid Session ID found in SessionHeader
[/exception]
JasonRogersJasonRogers
Correction, this started happening around 15:00 EST, March 15, 2004 (I originally posted that it started happening around 17:00). I have a case logged in customer support and will keep this thread up-to-date with anything from there.