Article ID: 2033238 - View products that this article applies to.
When certain modules are loaded into the Microsoft SQL Server process address space (Sqlservr.exe), you may encounter the following symptoms:
These issues occur because applications or other software that are installed on a server that is running SQL Server can load certain modules into the SQL Server process (Sqlservr.exe). This maybe done to achieve a specific business logic requirement, an enhanced functionality, or intrusion monitoring. These modules might perform unsupported activities that include detouring important Win32 APIs and SQL Server routines, and calling risky APIs. Additionally, some intrinsic problems within these modules may cause corruption of various memory structures that are necessary for the SQL Server process to function correctly.
Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
To work around this problem, follow these steps:
Microsoft Customer Support and Services (CSS) team has identified the following modules that can cause the symptoms that are mentioned in the "Symptoms" section. This list will be updated as new issues are found. This list is provided to help you identify the process that is mentioned in the "Resolution" section. This process typically involves the collection of an iterative set of diagnostic and tracing data for the duration of the problem.
The following modules can cause performance and stability issues when they are loaded into the SQL Server process:
The following table provides more information about the products or tools that automatically check for this condition in your instance of SQL Server and in the versions of SQL Server against which the rule is evaluated.
Collapse this tableExpand this table
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.
Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.
For more information about the SQL Server support policy, click the following article numbers to go to the article in the Microsoft Knowledge Base:
The use of third-party detours or similar techniques is not supported in SQL ServerFor more information about the SQL Server process, click the following article numbers to go to the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/906205/ )How to run a DLL-based COM object outside the SQL Server process
(http://support.microsoft.com/kb/243428/ )How to move extended stored procedures out of process
Article ID: 2033238 - Last Review: February 6, 2014 - Revision: 8.0
Contact us for more help
Connect with Answer Desk for expert help.