Frequently Asked Questions About SOAP Sessions
This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
The following answers to several frequently asked questions might help you resolve common issues that you may experience when you work with SOAP sessions.
Why am I getting either no SOAP response from the server or a "bad session ID" response?
First, make sure that the names of optional header elements or attributes used to initiate a session are correct. Specifically, verify that they are using the correct mixed case names such as sqlSession and sessionId. If the case is incorrect, the server will either ignore the header or return a bad session ID fault in the SOAP initiation response.
Why do I see a SOAP fault in the response that indicates the session I requested is disabled?
Make sure that the HTTP endpoint has had the SESSIONS property enabled for its SOAP properties. By default, sessions are not enabled when an HTTP endpoint is created, unless you explicitly set SESSIONS=ENABLED in the SOAP-based options for the endpoint by using either CREATE ENDPOINT or ALTER ENDPOINT.
I am trying to use a SOAP session with a WSDL request, but it does not work. Why?
SOAP sessions support is not available for Web Services Definition Language (WSDL) requests. For more information about WSDL, see Using WSDL.