0 Replies Latest reply: Nov 20, 2013 1:13 PM by SAULBADGUY RSS

SCOM 2012 - Workflow Initialization: Failed to start a workflow that runs a process or script

SAULBADGUY
Currently Being Moderated

Hello all - we recently installed the OnCommand Plug-In for SCOM, and things seem to be working properly (for the most part) but I constantly get warnings like this. Does anyone have an idea of what may be causing this?

 

The Event Policy for the process started at 2:50:00 PM has detected errors in the output. The 'StdErr' policy expression:
\a+
matched the following output:
C:\Program Files\System Center 2012\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 4\178119\InvokeMonitoringMethod.vbs(60, 19) mscorlib: An item with the same key has already been added.

 

Command executed: "C:\Windows\system32\cscript.exe" /nologo "InvokeMonitoringMethod.vbs" *root management server FQDN* LogControllerConnectionProtocol
Working Directory: C:\Program Files\System Center 2012\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 4\178119\

 


One or more workflows were affected by this.

 


Workflow name: DataONTAP.Monitoring.Rule.Controller.Connection

 

Instance name:*root management server*

More Like This

  • Retrieving data ...