BizTalk 2010 Installation and Configuration – Disable the Shared Memory Protocol (Part 7)

Posted: October 23, 2010  |  Categories: BizTalk

Under certain stress conditions (such as clients accessing SQL Server from the same computer), the SQL Server Shared Memory protocol may lower BizTalk Server performance. You can resolve this problem by disabling the use of the Shared Memory network protocol in the SQL Server Client Network Utility.

To disable the Shared Memory protocol for SQL Server

  1. Click Start, point to All Programs, point to Microsoft SQL Server 2008 R2, click Configuration Tools, and then click SQL Server Configuration Manager.
  2. In SQL Server Configuration Manager, expand SQL Server Network Configuration, and then click Protocols for MSSQLSERVER.
    sql configuration manager
  3. Right-click Shared Memory, and then click Disable.
  4. Click SQL Server Services, right-click SQL Server (MSSQLSERVER), and then click Stop. After the service has stopped, right-click SQL Server (MSSQLSERVER) again, and then click Start.
    sql configuration manager
  5. Close SQL Server Configuration Manager.

Related links

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

5 thoughts on “BizTalk 2010 Installation and Configuration – Disable the Shared Memory Protocol (Part 7)”

  1. Thanks for the Blog.
    After I disabled Shared Memory and stopped the SQL Server, now sql server is not starting again and failing with an error message:

    “The request failed on the service did not response ina timely fashion. consult the event log or other applicatble error logs for detail.”
    Error 1 in Event Log: SQL Server could not spawn FRunCM thread.
    Error 2 in Event Log: Could not start the network library because of an internal error in the network library.
    Error 3 in Event Log: TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error.
    Error 4: TDSSNIClient initialization failed with error 0xd, status code 0x4. Reason: All protocols are disabled. The data is invalid.

    I reenable the Shared Memory and SQL Server started just fine.


Leave a Reply

Your email address will not be published. Required fields are marked *


Back to Top