FIX: Error message when you try to create a WMI event alert by using the sp_add_alert stored procedure in SQL Server 2008: "The @wmi_query could not be executed in the @wmi_namespace provided"

Article translations Article translations
Article ID: 960573 - View products that this article applies to.
Bug: #50004003 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Expand all | Collapse all

SYMPTOMS

When you try to create a Windows Management Instrumentation (WMI) event alert by using the sp_add_alert stored procedure on a named cluster instance of Microsoft SQL Server 2008, you receive the following error message:
Msg 22022, Level 16, State 1, Line 0
SQLServerAgent Error: WMI error: 0x80041013.
Msg 14511, Level 16, State 1, Procedure sp_verify_alert, Line 300
The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists in the namespace and that the query has the correct syntax.
Note This problem does not occur if the cluster's SQL network name has exactly 15 characters.

The SQL network name is also known as the virtual SQL Server name.

CAUSE

This problem occurs because the WMI event provider cannot connect to the SQL Server database engine.

RESOLUTION

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
960484 Cumulative update package 3 for SQL Server 2008
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

WORKAROUND

To work around this problem, install a default cluster instance instead of a named cluster instance. Or, give the cluster a SQL network name that has exactly 15 characters.

Before you try to change the virtual SQL Server name, make sure that you have read the following items:
  • SQL Server does not support renaming servers that are involved in replication unless you use log shipping together with replication. The secondary server in log shipping can be renamed if the primary server is permanently lost. For more information, visit the following Microsoft Developer Network (MSDN) Web site:
    http://msdn.microsoft.com/en-us/library/ms151224.aspx
  • When you rename a virtual server that is configured to use database mirroring, you must turn off database mirroring before the renaming operation, and then you must re-establish database mirroring by using the new virtual server name. Metadata for database mirroring is not updated automatically to reflect the new virtual server name.
For more information about how to rename a virtual instance of SQL Server, visit the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/ms178083.aspx

STATUS

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

MORE INFORMATION

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
960484 Cumulative update package 3 for SQL Server 2008
The error message that is mentioned in the "Symptoms" section is a generic WMI error message. This error message may also occur under various other conditions that are not described in this article. In those cases, the resolutions that are described in this article do not apply. For more information about one case that is documented, visit the following Microsoft Web site:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=351556

REFERENCES

For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 960573 - Last Review: May 8, 2009 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 Web
Keywords: 
kbexpertiseadvanced kbfix kbsurveynew kbqfe KB960573

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com