SCOM Problem

April 1, 2008 at 12:17 pm (SCOM) (, , , , )

I’m stuck. I posted this last week on the Microsoft SCOM newsgroup, but I’m not getting any responses. On the off chance that the 5 people a day who read this site might know the answer, here’s the question as posted:

I’m sure this is something fundamental and simple, but I’m honestly
stuck.
I’m attempting to capture a new Performance Counter, Plan Cache, Cache
Hit Ratio, Object Plans & SQL Plans. When I lay it out to create it, I
get the attached error. I’m assuming based on the “Unknown alias” and
the fact that I’m in a custom management pack, something is amiss with
the Management Pack. What? Any help at all would be appreciated.

Date: 3/28/2008 11:29:55 AM
Application: System Center Operations Manager 2007
Application Version: 6.0.6246.0
Severity: Error
Message:

: Processing the template failed. See inner exception for details.
Verification failed with [1] errors:
——————————————————-
Error 1:
: Verification failed for rule:
MomUIGeneratedRulea4c32409c6a04ff786d9570af7d90d5f

Failed to verify referenced module : ID=DSInvalid configuration
specified for Module [DS]Cannot resolve identifier [SQL!
Microsoft.SQLServer.DBEngine] in the context of ManagementPack
[FMG.SQL.Management.Pack]. Unknown alias [SQL]
——————————————————-
Verification failed for rule:
MomUIGeneratedRulea4c32409c6a04ff786d9570af7d90d5f
Failed to verify referenced module : ID=DSInvalid configuration
specified for Module [DS]Cannot resolve identifier [SQL!
Microsoft.SQLServer.DBEngine] in the context of ManagementPack
[FMG.SQL.Management.Pack]. Unknown alias [SQL]
: Verification failed with [1] errors:
——————————————————-
Error 1:
: Verification failed for rule:
MomUIGeneratedRulea4c32409c6a04ff786d9570af7d90d5f

Failed to verify referenced module : ID=DSInvalid configuration
specified for Module [DS]Cannot resolve identifier [SQL!
Microsoft.SQLServer.DBEngine] in the context of ManagementPack
[FMG.SQL.Management.Pack]. Unknown alias [SQL]
——————————————————-

Verification failed for rule:
MomUIGeneratedRulea4c32409c6a04ff786d9570af7d90d5f
Failed to verify referenced module : ID=DSInvalid configuration
specified for Module [DS]Cannot resolve identifier [SQL!
Microsoft.SQLServer.DBEngine] in the context of ManagementPack
[FMG.SQL.Management.Pack]. Unknown alias [SQL]
: Verification failed for rule:
MomUIGeneratedRulea4c32409c6a04ff786d9570af7d90d5f

Failed to verify referenced module : ID=DSInvalid configuration
specified for Module [DS]Cannot resolve identifier [SQL!
Microsoft.SQLServer.DBEngine] in the context of ManagementPack
[FMG.SQL.Management.Pack]. Unknown alias [SQL]
: Failed to verify referenced module : ID=DS
Invalid configuration specified for Module [DS]Cannot resolve
identifier [SQL!Microsoft.SQLServer.DBEngine] in the context of
ManagementPack [FMG.SQL.Management.Pack]. Unknown alias [SQL]
: Invalid configuration specified for Module [DS]
Cannot resolve identifier [SQL!Microsoft.SQLServer.DBEngine] in the
context of ManagementPack [FMG.SQL.Management.Pack]. Unknown alias
[SQL]
: Cannot resolve identifier [SQL!Microsoft.SQLServer.DBEngine] in the
context of ManagementPack [FMG.SQL.Management.Pack]. Unknown alias
[SQL]

Permalink 7 Comments

SCOM As a Code Source

March 25, 2008 at 2:28 pm (SCOM) (, , , , )

A friend has had an article posted over on SQL Server Central that’s worth a read. Scott Abrants outlines the type of code that SCOM uses for SQL Server auditing and how you can leverage that outside of SCOM for other work you may be doing. As noted in the comments, it’s also worth taking a look at how Microsoft set up it’s rules and monitors as a method for setting up your own.

Permalink Leave a Comment