Return
-
Title
Invalid class Win32_PerfRawData_MSSQLMSSQLSERVER_MSSQLMSSQLSERVERTransaction in SQL Server agent logs -
Description
An error similar to the following is found in the SQL Server agent log
ERROR [DBSS-HOSTNAME-MSSQLSERVER-lowPriorityPool-1-[DBSS_TempDB][2020/06/11 07:07:29]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DBSSOSTempdbVersionStoreProcessor processor of DBSS_TempDB collection.java.lang.RuntimeException: Failed to execute collection [DBSS_TempDB], reason=com.quest.qsi.fason.framework.connections.common.exceptions.FrameworkQueryException: The query 'select VersionGenerationrateKBPers ,VersionCleanuprateKBPers ,LongestTransactionRunningTime ,UpdateSnapshotTransactions ,NonSnapshotVersionTransactionsfrom Win32_PerfRawData_MSSQLMSSQLSERVER_MSSQLMSSQLSERVERTransactions' has failed (0x80041010)- Profile:FglAM Connection Profile {Host = HOSTNAME, Agent = DBSS-HOSTNAME-MSSQLSERVER} Query: "select VersionGenerationrateKBPers , VersionCleanuprateKBPers , LongestTransactionRunningTime , UpdateSnapshotTransactions , NonSnapshotVersionTransactions from Win32_PerfRawData_MSSQLMSSQLSERVER_MSSQLMSSQLSERVERTransactions"
...Caused by: com.jacob.com.ComFailException: Invoke of: CountSource: SWbemObjectSetDescription: Invalid class -
Cause
MSSQLSERVER was used as the default SQL Server name rather than DEFAULT INSTANCE
-
Resolution
WORKAROUND
- Run SELECT @@servername in the monitored host.
- Navigate to Administration | Agents | Agent Status
- Select the SQL Server agent
- Click the Edit Properties
- Click the link to Modify the Private Properties for the Agent
- Please check the value of SQL Server Instance field in the Agent Status Properties. It should either match the Instance name after the "\" in Step #1 or be DEFAULT_INSTANCE.
- Save the changes
- Deactivate and activate the SQL Server agent
STATUS
Enhancement ID FGSS-I-72 has been logged to allow MSSQLSERVER be used as an alternative for the DEFAULT_INSTANCE name in the SQL Server agent.
-
Defect ID
FGSS-I-72