Operations Manager stops monitoring agents, EventID 29106
We hade problems with that new agents never get monitored and the existing agents didn’t get updates. The problem wasn’t´t noticed until we added a new agent to the Operations Manager. The agent never changed stat from “Not Monitored”. to being monitored. When we started to investigate we also noticed that existing agents hade not received updates for a few weeks. We found the following events on the management servers Operating Manger Event Log.
EventID 21402
and
EventID 29106
The request to synchronize state for OpsMgr Health Service identified by "840b63fc-4e79-feae-5754-2c5f58e3935e" failed due to the following exception "Microsoft.EnterpriseManagement.Common.DataAccessLayerException: Invalid column name ServerName_4B913AE3_F8FE_5802_C2B6_2CE90D099180 for query MTV_SelectProperty_9177efd8-6014-097c-0b38-b6358bafe2f7.
at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryDefinition.GetColumnDefinitionBySourceColumnName(String sourceColumnName, Int32 resultSetIndex)
at Microsoft.Mom.ConfigService.OpsMgrDataAccess.ConfigurationDataAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Execute(Managers managers)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)".
To find out the name of the management pack with 9177efd8-6014-097c-0b38-b6358bafe2f7.
You need to do a Query against the OperatinsManaganer database.
SELECT mp.ManagementPackId, mp.MPName,
mp.MPFriendlyName, mt.TypeName, mt.ManagedTypeTableName
FROM ManagementPack mp
LEFT JOIN ManagedType mt on mt.ManagementPackId = mp.ManagementPackId
WHERE mt.ManagedTypeId = ’9177efd8-6014-097c-0b38-b6358bafe2f7′
Running that query I got the following back:
B38768F3-8683-5B1D-0BE6-9F17BA9F0BB8 BridgeWays.Tomcat.ApplicationServer.Library BridgeWays Library for Apache Tomcat BridgeWays.Tomcat.ApplicationServer.License MT_License_0
We then tried removing the BridgeWays.Tomcat.ApplicationServer.Library management pack and the mp´s that where depending on it. And after after 5-30 minutes all the server that where not monitored turned green and healthy.
I found the solution in this blog post Kwan’s System Center Experience: OMG !!! I can’t monitor new servers in OpsMgr
