The F5 Monitoring Service Data Source Singleton Error

F5 Monitoring service on Management Server now refuses to stay started.

 

 

I've reset the Log On credentials for the F5 Monitoring service to use the designated domain service account and re-entered the password and restarted the service but within 30 seconds the service stops unexpectedly.

 

 

This happens regardless of whether the designated service account is used or the user credentials of a Windows Administrator colleague so I don't belive it is due to an incorrect password being entered when I specify the designated F5 Service Account credentials.

 

 

Julian, can you clarify whether the F5 Monitoring Service needs to be started before the System Center Management service on the Management Server in order to properly bind to the Heathlservice on the Management Server?

 

 

Regards,

 

 

Michael