Query: APM:: SQL Server 2005 Monitor

Hi,

I am trying to attach the SQL 2005 Monitor in order to monitor the orion sql server.

When testing against the node i receive the following:

Component Name | Component Test Results

Buffer cache-hit ratio | Testing on node xxx.xxx.xxx.xxx: failed with 'Undefined' status. Invalid Class

SQL Page Reads per Second | Testing on node xxx.xxx.xxx.xxx: failed with 'Undefined' status. Invalid Class

SQL Page Writes per Second | Testing on node xxx.xxx.xxx.xxx: failed with 'Undefined' status. Invalid Class

Latch waits | Testing on node xxx.xxx.xxx.xxx: failed with 'Undefined' status. Invalid Class

Full scans | Testing on node xxx.xxx.xxx.xxx: failed with 'Undefined' status. Invalid Class

SQL Server Process - WMI | Testing on node xxx.xxx.xxx.xxx: finished successfully with 'Available' status

SQL Server Browser - WMI | Testing on node xxx.xxx.xxx.xxx: failed with 'NotAvailable' status

SQL Server Port | Testing on node xxx.xxx.xxx.xxx: finished successfully with 'Available' status

Find more posts tagged with

apm

sql_server_2005

Accepted answers

All comments

Hi,

Try the commands described in the following post on your SQL Server:

HTH,

Yann

Hi

Same problem as described above

I am trying to attach the SQL 2005 Monitor in order to monitor the orion sql server.

Any help please. Thanks

Hi,

If you are getting the Invalid Class error, this means that when APM polls through WMI the CIMV2 NameSpace, it fails finding the needed Class.

This issue simply means that the WMI Service on the remote host did not manage to populate the required WMI Class in the Namespace, thus they are not available.

I suggest you to run WMI Explorer to check if you can query the needed WMI Class in your namespace.

Did you encounter any errors performing the actions described the link posted above?

Thanks,

Yann

I am having the same exact problem. We did everything on the WMI troubleshooting guide, but the problem still exists.

Has anyone found an answer to this? I am having this issue on one of the Exchange 2003 servers. Whats odd is all monitors are working fine against other Exchange servers. Its a cluster with 3 nodes. Others are two node clusters.

Quick Links