IT Core Blog

Never stop questioning. Curiosity has its own reason for existing…

How Stop monitoring SQL Express and Windows Internal Database

leave a comment »

Once again Kevin Holman did an excellent job explaining How Stop monitoring SQL Express and Windows Internal Database

What you will find – is that these editions are creating noise alerts… because of missing services, or service pack compliance.  Instead of tuning each rule/monitor and disabling for these machines – what I need to do is just say “don’t discover SQL Express or Windows Internal DB”.

Here are examples of the alerts you might see for these:

Service Check Probe Module Failed Execution
Error getting state of service
Error: 0x8007007b
Details: The filename, directory name, or volume label syntax is incorrect.
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor
Instance name: MICROSOFT##SSEE
Instance ID: {95468BCA-A30C-1EC5-027B-92BAF388AB69}
Management group: PROD1

Service Check Data Source Module Failed Execution
Error getting state of service
Error: 0x8007007b
Details: The filename, directory name, or volume label syntax is incorrect.
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2005.DBEngine.FullTextSearchServiceMonitor
Instance name: SQLEXPRESS
Instance ID: {6E9B2468-DF8A-B7F3-6283-D26F26B11D38}
Management group: PROD1

Script or Executable Failed to Run
The process started at 10:38:59 AM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0
Command executed: “C:\Windows\system32\cscript.exe” /nologo “DiscoverSQL2005DB.vbs” {E3EDD883-4224-657C-BD61-556FD10E7A38} {95468BCA-A30C-1EC5-027B-92BAF388AB69} omterm.opsmgr.net omterm.opsmgr.net omterm\MICROSOFT##SSEE MICROSOFT##SSEE “Exclude:”
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 9\3192\
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2005.DatabaseDiscoveryRule
Instance name: MICROSOFT##SSEE
Instance ID: {95468BCA-A30C-1EC5-027B-92BAF388AB69}
Management group: PROD1

Advertisements

Written by IT Core

February 13, 2010 at 10:33 PM

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: