Search This Blog

Friday, February 3, 2012

WMI / Workflow errors in SCOM

Came across a different batch of workflow errors that required the same solution as the ones previously posted. If you encounter errors like this in SCOM, time to break out scriptomatic and toubleshoot your WMI connections to the affected servers.

*************************************************************************************

Data was found in the output, but has been dropped because the Event Policy for the process started at 10:56:09 AM has detected errors.
The 'StdErr' policy expression:
\a+
matched the following output:
Error -2147217407:
Unable to open WMI Namespace 'winmgmts:\\servername\root\cimv2'. Check to see if the WMI service is enabled and running, and ensure this WMI namespace exists.

*************************************************************************************

Data was found in the output, but has been dropped because the Event Policy for the process started at 2:35:17 PM has detected errors.
The 'StdErr' policy expression:
\a+
matched the following output:
Error -2147217357: Shutting down
The class name 'Win32_Printer' could not be found. Please check to see if this is a valid WMI class name.

*************************************************************************************

No comments:

Post a Comment