Article ID: 2622195 - View products that this article applies to.
A System Center Operations Manager 2007 (OpsMgr 2007) management server repeatedly logs events that are similar to the following:
Event Type: Information
The agent names in the 21042 event descriptions are servers that run Microsoft Failover Clustering or Microsoft Cluster Service.
If you capture verbose trace logs on the management server, the native trace log (TracingGuidsNative.log) contains messages that are similar to the following:
   [09/22/2011-14:44:13.325] [MOMConnector]  [Verbose]  [CConnectorSolutionImpl::onIncomingRead] [ConnectorSolutionImpl_cpp2186]Processing message of datatype 6:0, destination <FQDN of cluster node>
   [09/22/2011-14:44:13.325] [MOMConnector]  [Error]  [CConnectorSolutionImpl::validateDataItemRouting] [ConnectorSolutionImpl_cpp5148]Received a DATATYPE_CONTRIBUTOR_STATE_REQUEST from <Health Service ID>
   [09/22/2011-14:44:13.325] [MOMConnector]  [Verbose]  [CConnectorSolutionImpl::validateDataItemRouting] [ConnectorSolutionImpl_cpp5151]<Jobs><Job ID="6C8BEDC9-5332-7143-D192-84C218878A5A" BatchID="2027CBF5-B248-4A0E-8F9A-32A0F2C56E41" TaskID="4BE723CD-BA53-F7FB-6A4A-4A5F062E77EF" TargetInstanceID="<Health Service ID>" JobCategory="0" ><Overrides><Override><Path>MonitorId</Path><Value>A6C69968-61AA-A6B9-DB6E-83A0DA6110EA</Value></Override></Overrides></Job></Jobs>
   [09/22/2011-14:44:13.325] [MOMConnector]  [Error]  [CConnectorSolutionImpl::onIncomingRead] [ConnectorSolutionImpl_cpp2210]Bad routing for a data item detected
   [09/22/2011-14:44:13.340] [Common]  [Verbose]  [Common::EventLogUtil::LogEvent] [EventLogUtil_cpp321]Logging informational event 21042 with args "5", "<MG Name>","<FQDN of a different node on the same cluster>", "NULL", "NULL", "NULL", "NULL", "NULL", "NULL"
In the above trace log messages, the FQDN in the first trace message and the FQDN in the last trace log message are different physical nodes in the same failover cluster.
This is a known issue in OpsMgr 2007 that occurs when an agent that is part of a cluster runs a dependency monitor. In some cases, unit monitors that contribute to the dependency monitor state may run on a different node in the cluster. This results in an agent sending state data to another agent via the management server. When this occurs, the management server discards the state data and logs a 21042.
If the agent names in the 21042 events are cluster nodes, you can safely ignore these messages.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2622195 - Last Review: October 3, 2011 - Revision: 2.0