Share via

Issue of the week 10/9/09 - StatisticsManagerServer event id 100

  • Article

Issue:

Constant StatisticsManagerServer event id 100 on the passive node of a 2003 cluster (maybe on a SCC cluster in 2008 as well)

 

Cause:

Antigen Statistics Service needs to access the statistics.xml located in the %data% folder of the Antigen install.

On a passive node this xml file is located on the shared drive that is controlled by the active node. This causes a failure to start for the service.

The service is starting because something is making a call to it.

In most cases there is monitoring software that loads up our Scan counters for performance monitor.

Other issues could stem from FSSMC collecting scan data from the passive node.

 

Workaround:

Monitoring software. This is expected behavior and the process loading these counters need to be configured to not monitor Antigen on passive nodes.

 

FSSMC: If you are using FSSMC to monitor the passive node you can try re-deploying the agent to the passive node.