Winsock Layered Service Providers (LSP) may result in network or server stability problems for SQL Server

Applies to: Microsoft SQL Server 2005 Developer EditionMicrosoft SQL Server 2005 Enterprise EditionMicrosoft SQL Server 2005 Enterprise X64 Edition More

Symptoms


You notice abrupt hang or termination of all network communications between SQL Server and the client applications. This can cause SQL Server to become unresponsive and cause service failures. You might receive exceptions whose call stacks involve manipulating data structures that are maintained or used by the modules loaded into the SQL Server address space. These problems are typically followed by error messages generated by the SQL Server scheduler, such as errors 17883 and 17882.

Cause


A Winsock LSP DLL can be loaded into the SQL Server processes and can intercept and monitor network communications (including TDS packets) at the Winsock level between the client applications and SQL Server. This occurs when Network Monitoring Agents are installed on a computer that is running SQL Server and this computer is chosen for monitoring network use for monitoring performance counters by a Managed Service Provider.

Resolution


Execute the following command from a command prompt to find out the list of all Winsock LSPs that are installed on the computer that is running SQL Server:
Netsh winsock show catalog
Execute the following query to find out which of these installed LSPs are loaded into the SQL Server process:
SELECT [name],[company],[file_version],[product_version]
FROM sys.dm_os_loaded_modules
WHERE company NOT LIKE 'Microsoft%' OR company is NULL

If you have a business requirement to use these providers, ensure that you have the latest updates installed for these providers. If possible avoid monitoring SQL Server related traffic and avoid loading these modules into the SQL Server process. Alternately you could exclude this server from the monitoring process.


More Information


Winsock architecture
Transport Service Providers


For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:

Rule softwareRule titleRule descriptionProduct versions against which the rule is evaluated 
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)







Winsock LSP loaded into SQL









The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect situations where one or more Winsock Layered Service Providers (LSPs) are installed on the computer that is running SQL Server and that their corresponding libraries are loaded into the SQL Server process. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2. 


If you run the BPA tool and encounter a Warning with the title of Database Engine - Winsock LSP loaded into SQL, then you need to review the information provided in this article and configure the providers in such a way to avoid monitoring SQL Server related traffic or remove them from the SQL Server.
SQL Server 2008
SQL Server 2008 R2









SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)





Winsock LSP loaded into SQL






The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect situations where one or more Winsock Layered Service Providers (LSPs) are installed on the computer that is running SQL Server and that their corresponding libraries are loaded into the SQL Server process.
If you run the BPA tool and encounter a Warning with the title of Database Engine - Winsock LSP loaded into SQL, then you need to review the information provided in this article and configure the providers in such a way to avoid monitoring SQL Server related traffic or remove them from the SQL Server.
SQL Server 2012