Microsoft KB Archive/938911

= FIX: Event ID: 21421 occurs when you use the Microsoft Operations Manager 2005 agent to monitor a clustered instance of SQL Server 2005 in a clustered environment =

Article ID: 938911

Article Last Modified on 9/18/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems

-



Bug #: 50001253 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.



SYMPTOMS
Consider the following scenario. In a clustered environment, you install an instance of SQL Server 2005 on a node. You install an instance of SQL Server 2005 Reporting Services on the same node. The virtual server name of the cluster is the same as the name of the instance of SQL Server 2005 Reporting Services. Additionally, you install the Microsoft Operations Manager (MOM) 2005 agent on the same node.

In this scenario, when you configure the MOM 2005 agent to monitor the clustered instance of SQL Server 2005, an event that resembles the following is logged in the Application log every 15 seconds: Event Type: Warning

Event Source: Microsoft Operations Manager

Event Category: MOM Agent

Event ID: 21421

Date:

Time:

User: N/A

Computer:

Description:

The description for Event ID ( 21421 ) in Source ( Microsoft Operations Manager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: script: SQL Server 2005 Block Analysis, 240, GRPMOM.

Additionally, two events that resemble the following may be logged in the Application log:

Event 1

Event Type: Error

Event Source: Application Error

Event Category: (100)

Event ID: 1000

Date:

Time:

User: N/A

Computer:

Description:

Faulting application wmiprvse.exe, version 5.2.3790.1830, faulting module svrenumapi.dll, version 2005.90.3042.0, fault address 0x00054174.

Event 2

Event Type: Error

Event Source: WinMgmt

Event Category: None

Event ID: 10

Date:

Time:

User: N/A

Computer:

Description:

Event filter with query &quot;select * from __InstanceModificationEvent within 10 where TargetInstance isa 'SqlService'&quot; could not be (re)activated in namespace &quot;//./root/Microsoft/SqlServer/ComputerManagement&quot; because of error 0x8004106c. Events may not be delivered through this filter until the problem is corrected.



RESOLUTION
The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2

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 2005 fix release. Microsoft recommends 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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; 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:

936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available

