OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.
OperationsManager container doesnt exist in domain %5 or the Run As Account associated with the AD based agent assignment ...
OpsMgr Config Service configuration state has become invalid. This maybe a temporary issue that may be recovered from automatically. ...
OpsMgr Config Service could not retrieve a consistent state from the OpsMgr database due to too frequent database changes. ...
OpsMgr Config Service failed to adjust the privileges at start up. It is not recommended to run the service with unnecesarry ...
OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening ...
OpsMgr Config Service has lost connectivity to the OpsMgr database, therefore it can not get any updates from the database. ...
OpsMgr has received configuration for management group %1 from the Configuration Service, but failed to process the configuration. ...
OpsMgr has received configuration for management group %1 from the Configuration Service, but failed to process the configuration. ...
OpsMgr has received confirmation for management group %1 from the Configuration Service that our existing configuration is ...