You need to sign in to do that
Don't have an account?
ColoradoMike
Suddenly getting " Invalid Session ID found in SessionHeader: Session timed out"
I've built an application that logs in to a couple of different instances of Salesforce. For each instance, it does the typical login and setting of the SessionId into my binding object.
My trouble is that suddenly with one of my instances (a Professional Edition instance), every once in a while I'm getting:
Invalid Session ID found in SessionHeader: Session timed out
It doesn't happen every time, so I'm having a devil of a time tracking this down.
Anyone know have a suggestion as to why one might see that error sporadically?
Naturally I've triple-checked the credentials used by the application. "Lock IP Addresses" is off and the default session timeout is set to 8 hours.
My trouble is that suddenly with one of my instances (a Professional Edition instance), every once in a while I'm getting:
Invalid Session ID found in SessionHeader: Session timed out
It doesn't happen every time, so I'm having a devil of a time tracking this down.
Anyone know have a suggestion as to why one might see that error sporadically?
Naturally I've triple-checked the credentials used by the application. "Lock IP Addresses" is off and the default session timeout is set to 8 hours.
Regards, Ben
For the most part, the error has disappeared, thankfully. I asked a couple of folks at Salesforce about it and no one was aware of any issue.
I wish we had some real information about this issue and whether it's been corrected, but at least for now, my application seems okay.
How did you get in touch with the SalesForce folks? At the moment I don't know what to do - my application is delivering a couple of thousand emails an hour to my inbox, so I've had to switch it off. I'm not sure I have any way of debugging this problem as like I say, this application has been running in it's current form without problems for years...
Cheers, Ben
Thanks, Ben
It's nearly a month later and unfortunately I'm still having that same issue. It disappeared for a while, but now it happens every couple of days.
I've logged a case with Salesforce support as well as with partner support, and alas, no one has been able to determine anything.
How're things going for you with regard to this error?
Mike