OpsMgr Config Service could not retrieve a consistent state from the OpsMgr database due to too frequent database changes. ...

System Center Operations Manager 2007

OpsMgr Config Service could not retrieve a consistent state from the OpsMgr database due to too frequent database changes.  This could be due to a normal and temporary increase of discovery data; however check the most recent changes to determine if this increase is unexpected.

 Most recent monitoring object change:
 Instance = %1
 Class = %2
 Modified time = %3

 Most recent monitoring relationship change:
 Relationship instance = %4
 Source instance = %5
 Target instance = %6
 RelationshipClass = %7
 Modified time = %8

Operations Manager will discover the devices that you specify and all devices that are connected to the devices that you ... OperationsManager container doesnt exist in domain %5 or the Run As Account associated with the AD based agent assignment ... 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. ...