The F5 Monitoring Service Data Source Singleton Error

Hi flipa,

 

 

I'd probably do the same, trying to flush the cached health-state of the entire SCOM health model. You mentioned that the "System Center Management (SCOM) service" is configured on both Management Servers with the same account. Are you referring to the SCOM Health Service here (System Center Management service)? Is the SCOM Health Service configured to run with a different account than 'LocalSystem'? If that's the case, I would definitely change the account to LocalSystem (on both Management Servers). Is there a specific reason why you would run the Health Service with a different account than the default (and preferred) LocalSystem account?

 

 

If you'd like to also clean the cached health state of the SCOM Health Service, probably the least disruptive (and safest) way would be to the following:

 

 

- stop the System Center services (SDK, Health, Config),

 

- clear the Health Service state (deleting the files in the \System Center Operations Manager 2007\Health Service State\Health Service Store folder)

 

- clear the Management Pack cache (deleting the files in the \System Center Operations Manager 2007\Health Service State\Management Packs folder)

 

- clear the Health Service connector configuration cache (deleting the OpsMgrConnector.Config.xml file in \System Center Operations Manager 2007\Health Service State\Connector Configuration Cache\)

 

- clear the SDK Service state (deleting the MomAuth.xml file in \System Center Operations Manager 2007\SDK Service State).

 

 

I usually try to stay away from this radical procedure, but in cases like yours it's probably worth pursuing in order to start a clean slate. (All of the files deleted will be reconstructed based on the OperationsManager database, upon restarting the SCOM services).

 

 

Julian