You need to sign in to do that
Don't have an account?
tannershamrock
New API Broke ALL Applications and many s-controls: Invalid Session ID
I am not very pleased with this rollout of API 12. This subsequently broke all of our integration applications using Java and the API, all of our Cast Iron orchestrations, and many of our s-controls.
I thought there was supposed to be reverse compatibility?
We are getting Invalid Session ID errors on everything and it is costing us a TON of money to fix these problems.
Is anyone else having these problems throughout the board? Any suggestions on how to deal with this on a large scale?
I thought there was supposed to be reverse compatibility?
We are getting Invalid Session ID errors on everything and it is costing us a TON of money to fix these problems.
Is anyone else having these problems throughout the board? Any suggestions on how to deal with this on a large scale?
we are experiencing exactly the same problem in our sandbox.
It was working fine for a very long time... then not working at all, there have been no changes to our code.
We can obtain a connection successfully, login and get a session id ... but when we try to use the session id in any subsequent transactions we receive the INVALID_SESSION_ID error message.
this problem seems to be common as there is another post with the same issue.
http://community.salesforce.com/sforce/board/message?board.id=NET_development&message.id=5766
Any help would be greatly appreciated... as previsouly stated.... this is extremley frustrating to have your applications suddenly stop working without receiving any details of the changes from SalesForce.
regards,
Adrian
All of the details are.....
We currently have a java application that talks to salesforce using webservices.
We are able to log into salesforce and obtain a session id.... and until some time last week.... we were able to reuse this session id.
Now, when we try to use this session id to execute a subsequent web service call we receive the error "INVALID_SESSION_ID: Illegal Session ID found in SessionHeader: Illegal Session".
The subsequent calls are executed almost immediately after obtaining the session id... so the session has not exceeded the timeout as set in salesforce.
I'm more then happy to provide any further information anyone would like
just let me know what you would like to know.
thanks,
Adrian
no we haven't logged a support case. The username is webapp@pctfiler.com and we are only receiving the error in the sandbox.
cheers,
Adrian
thx.
cheers,
Adrian
Hey Simon,
You can see an example of one of the faulty xml requests at:
http://www.rebuildresources.com/badrequest.xml
Thanks,
Josh