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
limjhlimjh 

System.ServiceModel.FaultException: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash.

Hi,
We encouter this error recently (it was working 3 months ago) while trying to connect to salesforce SOAP service method; importProducts.

Do you have any idea why this happen?
Error:
System.ServiceModel.FaultException: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session. Session not found, missing session hash: cWDoKsK9fIn01hr05uV2ZaCI+c6Q1iuM4xAtxMSCPxs=
This error usually occurs after a session expires or a user logs out.
 
Information:

<endpoint address="https://test.salesforce.com/services/Soap/c/28.0/0DFw00000000ePf" binding="basicHttpBinding" bindingConfiguration="SoapBinding"
        contract="Salesforce.Soap" name="Soap"/>
      <endpoint address="https://cs17.salesforce.com/services/Soap/class/SpiderProductImportWebservice" binding="basicHttpBinding"
        bindingConfiguration="SpiderProductImportWebserviceBinding" contract="SalesforceProductsList.SpiderProductImportWebservicePortType"
        name="SpiderProductImportWebservice"/>
      <endpoint address="https://cs17.salesforce.com/services/Soap/class/SpiderContractPriceImportWebservice" binding="basicHttpBinding"
        bindingConfiguration="SpiderProductImportWebserviceBinding" contract="SalesforceContractPricesList.SpiderContractPriceImportWebservicePortType"
        name="SpiderContractPriceImportWebservice"/>

Kind regards,
Faizan
Marco Venanzoni 17Marco Venanzoni 17
Hi Faizan, 

we are having the same issue you had. 

It has worked for longer than a month.
But then after 18 January , we are getting the same error randomly. So the thing is that it does appear only sometimes.

Have solved this?

Regards,
Marco
 
James TrachyJames Trachy
We are receiving the same calls into SOAP apis.  Had been working fine for 5 years prior to recently it becoming a problem, and the same token seems to work when we perform calls into SF Rest APIs that we built.

Any insight would be greatly appreciated.

James