|
|
 
0 |
Many people on forums claims that Import/Download Management Pack – new functionality introduced in Operations Manager 2007 R2 -- is not good solution. Main reason for that statements: I allow to import MP without reading piece of documentation. But there are others.
One of example I observe few days ago.
I had few problems with my production OpsMgr environment. It is quite small: all roles in one server, with few agents (bellow 100), with few OpsMgr Gateways (with separate domains, not trusted) and 5 independent machines connected do RMS by certificate.
I meet other issue related with that functionality. When I upgrade Windows Base OS MPs (to version 6.0.6667) I do it using Download MP. If I’m correct remember it finish with success.
But few weeks after that I recognize similar behavior like here: http://www.systemcentercentral.com/tabid/60/indexId/46870/tag/Forums/Default.aspx#vindex48005 :( It look that Agents cannot communicate with RMS.
Event Type: Warning
Event Source: OpsMgr Config Service
Event Category: None
Event ID: 29106
Date: 11/12/2009
Time: 7:35:38 PM
User: N/A
Computer: OPSMGR
Description:
The request to synchronize state for OpsMgr Health Service identified by "9feb20e0-38dc-4e08-8b2a-5eec57a6de66" failed due to the following exception "Microsoft.EnterpriseManagement.Common.DataAccessLayerException: Invalid column name SizeNumeric_486ADDDB_2EB8_819A_FA24_8F6AB3E29543 for query MTV_SelectProperty_0b95ad7d-e73b-80cf-56cb-05d537682d2c.
at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryDefinition.GetColumnDefinitionBySourceColumnName(String sourceColumnName, Int32 resultSetIndex)
at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryDefinition.GetColumnDefinitionBySourceColumnName(String sourceColumnName)
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)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Of course after “reinstall” – practically, for Windows 2003 MP, install first time – problem disappeared.
Awful, really?