FIX: A memory leak in SQLWEP causes the host process Wmiprvse.exe to crash in SQL Server

Si applica a: SQL Server 2012 DeveloperSQL Server 2012 EnterpriseSQL Server 2012 Enterprise Core

Symptoms


Assume that you use Windows Management Instrumentation (WMI) to monitor events in Microsoft SQL Server. In this situation, a memory leak occurs in SQLWEP. This causes the Wmiprvse.exe process to crash with a 'WBEM_E_OUT_OF_MEMORY' error. Additionally, error messages that resemble the following are logged in the SQL Server error log:

Error: 17003 - Closed event notification conversation endpoint with handle '{7BC24B36-B24C-E611-944D-0050569F4BF2}', due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8470</Code><Description>Remote service has been dropped.</Description></Error>'.

Error: 17001 - Failure to send an event notification instance of type 'AUDIT_DATABASE_OBJECT_MANAGEMENT_EVENT' on conversation handle '{7EC24B36-B24C-E611-944D-0050569F4BF2}'. Error Code = '8429'.

Error: 17005 - Event notification 'SQLWEP_2C6B2B50_50D2_4615_BEDF_A1E2092223C7' in database 'master' dropped due to send time service broker errors.

Resolution


This issue is fixed in the following cumulative updates for SQL Server:

       Cumulative Update 6 for SQL Server 2016 RTM

       Cumulative Update 3 for SQL Server 2016 SP1

       Cumulative Update 5 for SQL Server 2014 SP2

       Cumulative Update 12 for SQL Server 2014 SP1

       Cumulative Update 8 for SQL Server 2012 SP3

 

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology that Microsoft uses to describe software updates.