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
- Click Start, point to All Programs, point to Microsoft SQL Server 2008 R2, click Configuration Tools, and then click SQL Server Configuration Manager.
- In SQL Server Configuration Manager, expand SQL Server Network Configuration, and then click Protocols for MSSQLSERVER.
- Right-click Shared Memory, and then click Disable.
- 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.
- Close SQL Server Configuration Manager.
Related links
- BizTalk 2010 Installation and Configuration – Enable Internet Information Services (Part 1)
- BizTalk 2010 Installation and Configuration – Install Microsoft Office Excel 2007 (Part 2)
- BizTalk 2010 Installation and Configuration – Install Visual Studio 2010 (Part 3)
- BizTalk 2010 Installation and Configuration – Install SQL Server 2008 R2 (Part 4)
- BizTalk 2010 Installation and Configuration – Install SQL Server 2005 Notification Services on top of SQL Server 2008 R2 (Part 5)
- BizTalk 2010 Installation and Configuration – Install and Configure Windows SharePoint Services (Part 6)
- BizTalk 2010 Installation and Configuration – Install and Configure SharePoint Foundation 2010 (Part 6.1)
- BizTalk 2010 Installation and Configuration – Disable the Shared Memory Protocol (Part 7)
- BizTalk 2010 Installation and Configuration – Installing and Configuring BizTalk Server (Part 8 )
- BizTalk 2010 Installation and Configuration – Installing and configuring local SMTP for Reporting Server (Part 9)
- BizTalk 2010 Installation and Configuration – Installing BizTalk Adapter Pack 2010 and BizTalk AppFabric Connect feature (Part 10)
- BizTalk 2010 Installation and Configuration – Configure BizTalk Server SQL Jobs (Part 11)
- BizTalk 2010 Installation and Configuration – Enable TCP/IP, Named Pipes protocols and DTC on the Local Host Server (Part 12)
- BizTalk 2010 Installation and Configuration – Configure the Application Event Log (Part 13)
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.
Thanks.
Hi,
The Shared Memory should be disabled.
To solve this problem, try check the following solutions:
– http://connect.microsoft.com/SQLServer/feedback/details/330614/sql-server-could-not-spawn-fruncm-thread
– http://sqlserver-qa.net/blogs/tools/archive/2007/09/25/sql-server-errors-could-not-spawn-fruncm-thread-and-tdssniclient-initialization-failed-with-error-0xd-status-code-0x36.aspx
– http://www.dedicatedsqlserver.com/HowTo/MSSQLSERVER_Fail_To_Start.aspx
Another thing, “TCP/IP” protocol should be enabled
Is there any way to disable shared memory from command line or registry
You can for example configure all the SQL Server Network Protocols with PowerShell. See my last post http://sandroaspbiztalkblog.wordpress.com/2013/04/04/how-to-configure-sql-server-network-protocols-in-the-sql-server-that-houses-biztalk-server-databases-with-powershell/