Posts Tagged ‘SCOM’

OpsMgr: Prevent warning event 21405

Written by Ingmar Verheij on March 16th, 2012. Posted in Operations Manager

A System Center Operation Manager (SCOM or OpsMgr) management pack might cause warning event with ID 21405. This event is raised when a script is run without returning any data.


Log Name:      Operations Manager
Source:        Health Service Modules
Date:          16-3-2012 16:14:26
Event ID:      21405
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
The process started at 16:14:26 failed to create System.PropertyBagData, no errors detected in the output.  The process exited with 0

A script is run to discover objects or to query data (to collect data – a rule – or to monitor and object – a monitor) and should return this data to the MOM.ScriptAPI object so it can be processed. If a script is run without returning data OpsMgr suspects an issue. A script might not return data because of antivirus, DEP or by design. If you design a management pack, continue reading.

No data collected from HP EVA

Written by Ingmar Verheij on July 25th, 2011. Posted in Operations Manager

16 MegaBytes Hard DiskRecently I wrote a management pack to retrieve capacity data from a HP Enterprise Virtual Array (EVA) in System Center Operations Manager (SCOM). Recently I found out that no data is collected.

Execution of the Python script resulted in the following error:

c:\Python26\python.exe "C:\Python26\Temp\" -s bsma001.xxxx.local --port 5988 -u SVC_SCOM_AA -p xxxxxxxx -f "C:\Python26\Temp" -c HPEVA_StorageSystem,HPEVA_StoragePool

Connection string: https://bsma001.xxxx.local:5988
Traceback (most recent call last):
  File "C:\Python26\Temp\", line 90, in 
    instanceNames = conn.EnumerateInstanceNames( className)
  File "c:\Python26\lib\site-packages\pywbem\", line 382, in EnumerateInstanceNames
  File "c:\Python26\lib\site-packages\pywbem\", line 173, in imethodcall 
    raise CIMError(0, str(arg))
pywbem.cim_operations.CIMError: (0, 'Socket error: [Errno 10061] No connection could be made because the target machine actively refused it')

Failed heartbeat unnoticed in Distributed Application

Written by Ingmar Verheij on July 12th, 2011. Posted in Monitoring

Server down

System Center Operations Manager (SCOM) monitors the health of systems with an agent. One of the most basic checks that is executed is a health check of the agent itself. One of the checks is a heartbeat between the agent and the RMS (Root Management Server). If the heartbeat is lost for three times (configurable), the agent is considered unavailable.Health Service Heartbeat Failure

An alert is generated and (if configured) a notification is send to inform the administrator that there is a problem.

But if a Distributed Application is configured to monitor a chain of components, this failure remains unnoticed.

Node state 'Healthy'

Nodes that are unmonitored are grey and appear to be ‘Healthy’, which is strange for a node who’s heartbeat haven’t reported for quite some time.

SCOM : Configure notification for distributed applications

Written by Ingmar Verheij on May 24th, 2011. Posted in Operations Manager

Events generated by System Center Operations Manager (SCOM), like alerts and warnings, usually indicate (upcoming) problems. Notifiying you’re system administrators enables you to troubleshoot te problem as quickly as possible.

For a customer I’ve configured multiple distributed applications. Each distributed application defines a critical application that needs to be monitored. All distributed applications are displayed on a monitor showing the state of the distributed application.


When an event is triggered, for instance because the service is down, a notification needs to be sent. Not only to the system adminstrators, who administer the infrastructure, but also to the technical and functional application operator.

Active Directory groups are used to make the membership of the managable, since role based access control (RBAC) is used.


Maintenance mode report in SCOM (fixed)

Written by Ingmar Verheij on May 18th, 2011. Posted in Operations Manager

Object, like computers, in System Center Operations Manager (SCOM) can be placed in a maintenance mode. While the object is in maintenance mode no alerts will be generated, as expected.

I wanted to see which objects have been placed in maintenance mode, unfortunately there is no default report supplied by Microsoft.

Fortunately Alain Côte wrote a report, along with a stored procedure, which enables me the insights requested. The management pack, containing the report and stored procedure, can be downloaded here: Maintenance Mode History Report Management Pack

There is one instruction missing in the documentation, additional permissions are required to run the stored procedure required by the report. Without the permissions the following error is displayed:

Query execution failed for data set 'OperationsManagerDW'