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.

Install Centrix Workspace Discover on a non-English OS

Written by Ingmar Verheij on January 13th, 2012. Posted in Inventory

I was looking for a free application to discover which applications where used in a environment. This is very useful when planning a major change in an environment (physical to virtual, or SBC to VDI, etc). But even more important when you’re scaling an environment with a loadtest, where the simulated load should match the real load. Neil Spellings was so kind to point me at the Centrix Workspace Discovery software.

During installation on a Dutch (Windows 7 x64) operating system I ran into problems. These are easy to fix (see below) but I recommend you to install it on a English OS (as with all server components).

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:

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.

Monitor “HP Proliant Server health on “Citrix XenServer” with Nagios

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

Nagios Powered

Nagios is a powerful monitoring system that enables organizations to identify and resolve IT infrastructure problems before they affect critical business processes.

After experiencing problems with a HP Proliant DL380G6 that unexpectedly restarts, caused by a Automated Server Recovery (ASR), monitoring the status of the Citrix XenServers running on HP Proliant Servers is required in Nagios.

Nagios is a flexible solution that can be expanded with plugins. Plugins can be found at Nagios Exchange, this is where I found the check check_hpasm plugin (direct link). Unfortunately this plugin does not check the ASR status.

In this article I will describe how I’ve configured Groundwork (using Nagios) to monitor the health of HP Proliant Servers and expanded the check_hpasm plugin to check for ASR health.