• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1608
  • Last Modified:

Disabling Shared Memory - SQL Native Client Configuration

We have 5 front end Windows Server 2003 servers connecting to a Dell R900 server with 24 cores. All machines are 64 bit operating systems.   We have started seeing this error:

---> System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

I have read many articles saying that we should disable Shared Memory in the SQL Native Client Configuration, and set the order of the TCP/IP client protocol to 1.

By disabling Shared Memory - what effect will this setting have on our current web applications?  If we are connecting to SQL Server using the SQL machine name, will we be affected?  I want to make sure our applications do not break.  

Isn't Shared Memory only used if a connection to SQL is made locally?
JWeb Admin
JWeb Admin
1 Solution
AFAIK, shared memory protocol (if enabled) is used when connecting locally using (local) or . as the servername prefix
(e.g. (local) or (local)\namedinstance ) and should provide the fastest connection to the backend. This is done bypassing the network stack and using an in-memory pipe for direct communication.

If you are connecting from a webserver, there is no way shared memory protocol can be used, so disabling shared memory is unlikely to change anything in terms of remote connections.

Have a look at the link below to see if that helps in terms of resolving the error -

JWeb AdminAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now