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

Posted: October 23, 2010 in BizTalk
Tags: , ,

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 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.
  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.
  5. Close SQL Server Configuration Manager.

Related links

Tags: BizTalk 2010 | Installation | Configuration

  1. BizTalker says:

    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.


  2. Anonymous says:

    Is there any way to disable shared memory from command line or registry

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s