I've been seeing a bunch of SCOM alerts over the past few weeks coming from my Server 2008 R2 database servers. The workflows are all SQL. The one's I'm seeing over and over are for these workflows
Microsoft.SQLServer.2008.ReportingServicesDiscoveryRule.Server
Microsoft.SQLServer.2008.AnalysisServicesDiscoveryRule.Server
Microsoft.SQLServer.2008.DBEngineDiscoveryRule.Server
Microsoft.SQLServer.2012.AnalysisServicesDiscoveryRule.Server
The alerts are all basically the same and look like this
Alert: Operations Manager failed to start a process
Source: SQLSRV.domain.com
Path: SQLSRV.domain.com
Last modified by: System
Last modified time: 11/21/2013 3:30:38 PM Alert description: The process started at 3:29:41 PM 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 "DiscoverSQL2008ASDiscovery.vbs" {8471C573-7C7E-1174-E3E0-0912FB4661A2} {EE10DDE0-2A93-8C71-A31E-3DDD783BB728} SQLSRV.domain.com SQLSRV.domain.com SQLSRV
Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 22776\8800\
I've changed the Timeout on the Discovery to 600 from 300 but that appears to do nothing. Anyone struggling with this?
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2008.AnalysisServicesDiscoveryRule.Server
Instance name: SQLSRV.domain.com
Instance ID: {EE10DDE0-2A93-8C71-A31E-3DDD783BB728}
Management group: SCOM2012
Orange County District Attorney