Exchange 2010 Correlation Engine Not Generating Alerts

Published Mar 12 2019 05:13 PM 1,305 Views
Senior Member

First published on TECHNET on Apr 15, 2015

While helping a customer migrate from SCOM 2007 to SCOM 2012 R2, we noticed a large reduction in Alerts for Exchange 2010.  After investigating further, we noticed that we were not getting any Alerts that come from the Exchange 2010 Correlation Engine.

 

After verifying with my customer that the Exchange 2010 Monitors were generating state changes, but no alerts were coming in, we reviewed the event log for the Correlation Engine (it logs to the Application Event log on the server it is installed on) and saw event 717 being logged every 5 minutes (more details below).

 

After doing some research, I found the following information which resolved the problem (provided by Microsoft Escalation Engineer Manoj Parvathaneni ).

 

Quick Summary:
We had to install the Correlation Engine on a server without any SCOM 2012 server components installed, and include some SCOM 2007 dlls in the Correlation Engine installation directory.

 

Symptoms

 

When the Exchange Correlation Engine is installed on a System Center 2012 Operations Manager Management Server, the Automatic Alert Resolution feature in the Exchange Correlation Engine ceases to function and the following event is logged in the Application event log on the Management Server:

 

Log Name: Application
Source: MSExchangeMonitoringCorrelation
Event ID: 717
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Description:
Connection with the Operations Manager Root Management Server failed.

 

Error: System.InvalidCastException: [A]System.Collections.Generic.List`1[Microsoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo] cannot be cast to [B]System.Collections.Generic.List`1[Microsoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo]. Type A originates from 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' in the context 'LoadNeither' at location 'C:\Windows\assembly\GAC_64\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll'. Type B originates from 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' in the context 'LoadNeither' at location 'C:\Windows\assembly\GAC_64\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll'.
at Microsoft.EnterpriseManagement.Utilities.GetDeserializeObject[T](Byte[] serializedObject)
at Microsoft.EnterpriseManagement.DataAbstractionLayer.InstanceSpaceOperations.UpdateAlerts(Byte[] alerts, String comments, Nullable`1 modifyingConnectorId)
at Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateAlertsInternal[T](IList`1 alerts, String comments, Nullable`1 modifyingConnectorId, ManagementGroup managementGroup)
at Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateInternal(String comments, Nullable`1 modifyingConnectorId)
at Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.Update(String comments)
at Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlert(Entity entity, MonitoringAlert monAlert)
at Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlerts(Entity entity, String alertCriteriaString)
at Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateWithinEntity(Node entity)
at Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateBatchTask(Object batchData)

 

Number of occurrence: 3

 

You'll also notice the following error in the Exchange Correlation Engine logs:

 

2013-11-18T08:16:15.673Z,4,Information,"CorrelateBatchTask: caught exception [System.InvalidCastException: [A]System.Collections.Generic.List`1[Microsoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo] cannot be cast to [B]System.Collections.Generic.List`1[Microsoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo]. Type A originates from 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' in the context 'LoadNeither' at location 'C:\Windows\assembly\GAC_64\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll'. Type B originates from 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' in the context 'LoadNeither' at location 'C:\Windows\assembly\GAC_64\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll'.    at Microsoft.EnterpriseManagement.Utilities.GetDeserializeObject[T](Byte[] serializedObject)    at Microsoft.EnterpriseManagement.DataAbstractionLayer.InstanceSpaceOperations.UpdateAlerts(Byte[] alerts, String comments, Nullable`1 modifyingConnectorId)    at Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateAlertsInternal[T](IList`1 alerts, String comments, Nullable`1 modifyingConnectorId, ManagementGroup managementGroup)    at Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateInternal(String comments, Nullable`1 modifyingConnectorId)    at Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.Update(String comments)    at Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlert(Entity entity, MonitoringAlert monAlert)    at Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlerts(Entity entity, String alertCriteriaString)    at Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateWithinEntity(Node entity)    at Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateBatchTask(Object batchData)].

 

In addition, the Exchange Correlation Engine will not report any new Alerts or report the alerts to SCOM 2012 inconsistently.

 

Resolution

 

The exception above can be resolved by using one of the following methods:

 

Method 1: Install Exchange Correlation Engine on a dedicated system without the SCOM 2012 Management Server component



    1. Install Exchange Correlation engine on this machine.

 

    1. Stop the Microsoft Exchange Monitoring Correlation service.

 

    1. Copy SCOM 2007 R2 SDK binaries into the CE install directory (Program Files\Microsoft\Exchange Server\v14\Bin).
      • Microsoft.EnterpriseManagement.OperationsManager.Common.dll
      • Microsoft.EnterpriseManagement.OperationsManager.dll
      • MomBidLdr.dll



**UPDATE: Files attached to this blog

 

Where can you find the above binary files?



    • The SCOM 2007 R2 SDK Binaries Microsoft.EnterpriseManagement.OperationsManager.Common.dll and Microsoft.EnterpriseManagement.OperationsManager.dll can be found on a system that has SCOM 2007 R2 Console in the following directory Program Files\System Center Operations Manager 2007\SDK Binaries.

 

    • The MOmBidLdr.dll can be found can be found on a system that has SCOM 2007 R2 Console in the following directory Program Files\System Center Operations Manager 2007



Method 2: Disable the Automatic Alert Resolution Feature in the Correlation Engine

 

By following this approach the customer will lose the ability to resolve the alerts automatically via the Exchange Correlation Engine.

 

To disable Automatic Alert Resolution, perform the following steps:



    1. Log on to the server that's hosting the Microsoft Exchange Monitoring Correlation Engine service.

 

    1. Locate the Correlation Engine configuration file named Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config. By default, the file is located in C:\Program Files\Microsoft\Exchange Server\V14\Bin\, where C:\ is the Exchange installation directory.

 

    1. Open Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config in a text editor such as Notepad

 

    1. Locate the following line in the configuration file:
      <add key="AutoResolveAlerts" value="true" />

 

    1. Change <add key="AutoResolveAlerts" value="true" /> to <add key="AutoResolveAlerts" value="false" />

 

    1. Restart the Microsoft Exchange Monitoring Correlation Engine service.



More Information

 

Exchange Correlation Engine:
The Correlation Engine(CE) is a stand-alone Windows service that uses the Operations Manager SDK interface to first retrieve the health model (or instance space) and then process state change events. By maintaining the health model in memory, and processing state change events, the Correlation Engine is able to determine when to raise an alert based on the state of the system. The Correlation Engine solely relies on the Operations Manager SDK. It does not use the agent to perform any of the correlation and other aspects of its operations. For further details, you can also reference the Exchange 2010 Management Pack guide .

 

Automatic Alert Resolution feature in Exchange Correlation Engine:
The Automatic Alert Resolution feature automatically closes related alerts when the Exchange 2010 Management Pack determines that the underlying issue is no longer a problem. This feature is provided by the Correlation Engine, and is enabled by default. Using Automatic Alert Resolution can cause multiple alerts to be logged if the same alert is logged again for another instance of the problem before the associated ticket has been resolved by support teams.

 

You may also want to disable this feature under the following or other conditions:



    • If you're using ticketing or another support system that wouldn't work correctly if alerts are automatically resolved.



If you're using a connector with Operations Manager 2007. A connector is a custom service or program that allows Operations Manager to communicate with external systems. For example, you may want to disable this feature if you're using a connector that allows an external application to track Exchange 2010 Management Pack alerts.

 

SCOM2007FilesForEXCHCorrelationEngine.zip

%3CLINGO-SUB%20id%3D%22lingo-sub-365787%22%20slang%3D%22en-US%22%3EExchange%202010%20Correlation%20Engine%20Not%20Generating%20Alerts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-365787%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E%20First%20published%20on%20TECHNET%20on%20Apr%2015%2C%202015%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWhile%20helping%20a%20customer%20migrate%20from%20SCOM%202007%20to%20SCOM%202012%20R2%2C%20we%20noticed%20a%20large%20reduction%20in%20Alerts%20for%20Exchange%202010.%26nbsp%3B%20After%20investigating%20further%2C%20we%20noticed%20that%20we%20were%20not%20getting%20any%20Alerts%20that%20come%20from%20the%20Exchange%202010%20Correlation%20Engine.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20verifying%20with%20my%20customer%20that%20the%20Exchange%202010%20Monitors%20were%20generating%20state%20changes%2C%20but%20no%20alerts%20were%20coming%20in%2C%20we%20reviewed%20the%20event%20log%20for%20the%20Correlation%20Engine%20(it%20logs%20to%20the%20Application%20Event%20log%20on%20the%20server%20it%20is%20installed%20on)%20and%20saw%20event%20717%20being%20logged%20every%205%20minutes%20(more%20details%20below).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20doing%20some%20research%2C%20I%20found%20the%20following%20information%20which%20resolved%20the%20problem%20(provided%20by%20Microsoft%20Escalation%20Engineer%20%3CSTRONG%3E%20Manoj%20Parvathaneni%20%3C%2FSTRONG%3E%20).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EQuick%20Summary%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3EWe%20had%20to%20install%20the%20Correlation%20Engine%20on%20a%20server%20without%20any%20SCOM%202012%20server%20components%20installed%2C%20and%20include%20some%20SCOM%202007%20dlls%20in%20the%20Correlation%20Engine%20installation%20directory.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%20Symptoms%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20the%20Exchange%20Correlation%20Engine%20is%20installed%20on%20a%20System%20Center%202012%20Operations%20Manager%20Management%20Server%2C%20the%20Automatic%20Alert%20Resolution%20feature%20in%20the%20Exchange%20Correlation%20Engine%20ceases%20to%20function%20and%20the%20following%20event%20is%20logged%20in%20the%20Application%20event%20log%20on%20the%20Management%20Server%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3E%20Log%20Name%3A%20Application%20%3CBR%20%2F%3ESource%3A%20MSExchangeMonitoringCorrelation%20%3CBR%20%2F%3EEvent%20ID%3A%20717%20%3CBR%20%2F%3ETask%20Category%3A%20General%20%3CBR%20%2F%3ELevel%3A%20Warning%20%3CBR%20%2F%3EKeywords%3A%20Classic%20%3CBR%20%2F%3EUser%3A%20N%2FA%20%3CBR%20%2F%3EDescription%3A%20%3CBR%20%2F%3EConnection%20with%20the%20Operations%20Manager%20Root%20Management%20Server%20failed.%20%3C%2FI%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3E%20Error%3A%20System.InvalidCastException%3A%20%5BA%5DSystem.Collections.Generic.List%601%5BMicrosoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo%5D%20cannot%20be%20cast%20to%20%5BB%5DSystem.Collections.Generic.List%601%5BMicrosoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo%5D.%20Type%20A%20originates%20from%20'mscorlib%2C%20Version%3D2.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db77a5c561934e089'%20in%20the%20context%20'LoadNeither'%20at%20location%20'C%3A%5CWindows%5Cassembly%5CGAC_64%5Cmscorlib%5C2.0.0.0__b77a5c561934e089%5Cmscorlib.dll'.%20Type%20B%20originates%20from%20'mscorlib%2C%20Version%3D2.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db77a5c561934e089'%20in%20the%20context%20'LoadNeither'%20at%20location%20'C%3A%5CWindows%5Cassembly%5CGAC_64%5Cmscorlib%5C2.0.0.0__b77a5c561934e089%5Cmscorlib.dll'.%20%3CBR%20%2F%3Eat%20Microsoft.EnterpriseManagement.Utilities.GetDeserializeObject%5BT%5D(Byte%5B%5D%20serializedObject)%20%3CBR%20%2F%3Eat%20Microsoft.EnterpriseManagement.DataAbstractionLayer.InstanceSpaceOperations.UpdateAlerts(Byte%5B%5D%20alerts%2C%20String%20comments%2C%20Nullable%601%20modifyingConnectorId)%20%3CBR%20%2F%3Eat%20Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateAlertsInternal%5BT%5D(IList%601%20alerts%2C%20String%20comments%2C%20Nullable%601%20modifyingConnectorId%2C%20ManagementGroup%20managementGroup)%20%3CBR%20%2F%3Eat%20Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateInternal(String%20comments%2C%20Nullable%601%20modifyingConnectorId)%20%3CBR%20%2F%3Eat%20Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.Update(String%20comments)%20%3CBR%20%2F%3Eat%20Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlert(Entity%20entity%2C%20MonitoringAlert%20monAlert)%20%3CBR%20%2F%3Eat%20Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlerts(Entity%20entity%2C%20String%20alertCriteriaString)%20%3CBR%20%2F%3Eat%20Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateWithinEntity(Node%20entity)%20%3CBR%20%2F%3Eat%20Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateBatchTask(Object%20batchData)%20%3C%2FI%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3E%20Number%20of%20occurrence%3A%203%20%3C%2FI%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou'll%20also%20notice%20the%20following%20error%20in%20the%20Exchange%20Correlation%20Engine%20logs%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3E%202013-11-18T08%3A16%3A15.673Z%2C4%2CInformation%2C%22CorrelateBatchTask%3A%20caught%20exception%20%5BSystem.InvalidCastException%3A%20%5BA%5DSystem.Collections.Generic.List%601%5BMicrosoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo%5D%20cannot%20be%20cast%20to%20%5BB%5DSystem.Collections.Generic.List%601%5BMicrosoft.EnterpriseManagement.Monitoring.MonitoringAlertUpdateStatusIndigo%5D.%20Type%20A%20originates%20from%20'mscorlib%2C%20Version%3D2.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db77a5c561934e089'%20in%20the%20context%20'LoadNeither'%20at%20location%20'C%3A%5CWindows%5Cassembly%5CGAC_64%5Cmscorlib%5C2.0.0.0__b77a5c561934e089%5Cmscorlib.dll'.%20Type%20B%20originates%20from%20'mscorlib%2C%20Version%3D2.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db77a5c561934e089'%20in%20the%20context%20'LoadNeither'%20at%20location%20'C%3A%5CWindows%5Cassembly%5CGAC_64%5Cmscorlib%5C2.0.0.0__b77a5c561934e089%5Cmscorlib.dll'.%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.EnterpriseManagement.Utilities.GetDeserializeObject%5BT%5D(Byte%5B%5D%20serializedObject)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.EnterpriseManagement.DataAbstractionLayer.InstanceSpaceOperations.UpdateAlerts(Byte%5B%5D%20alerts%2C%20String%20comments%2C%20Nullable%601%20modifyingConnectorId)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateAlertsInternal%5BT%5D(IList%601%20alerts%2C%20String%20comments%2C%20Nullable%601%20modifyingConnectorId%2C%20ManagementGroup%20managementGroup)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.UpdateInternal(String%20comments%2C%20Nullable%601%20modifyingConnectorId)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.EnterpriseManagement.Monitoring.MonitoringAlert.Update(String%20comments)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlert(Entity%20entity%2C%20MonitoringAlert%20monAlert)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Monitoring.CorrelationEngine.MomSdkProxy.ResolveEntityAlerts(Entity%20entity%2C%20String%20alertCriteriaString)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateWithinEntity(Node%20entity)%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Monitoring.CorrelationEngine.CorrelationEngine.CorrelateBatchTask(Object%20batchData)%5D.%20%3C%2FI%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20addition%2C%20the%20Exchange%20Correlation%20Engine%20will%20not%20report%20any%20new%20Alerts%20or%20report%20the%20alerts%20to%20SCOM%202012%20inconsistently.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%20Resolution%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20exception%20above%20can%20be%20resolved%20by%20using%20one%20of%20the%20following%20methods%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMethod%201%3A%20%3C%2FSTRONG%3E%20%3CSTRONG%3E%20Install%20Exchange%20Correlation%20Engine%20on%20a%20dedicated%20system%20without%20the%20SCOM%202012%20Management%20Server%20component%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EInstall%20Exchange%20Correlation%20engine%20on%20this%20machine.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EStop%20the%20Microsoft%20Exchange%20Monitoring%20Correlation%20service.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ECopy%20SCOM%202007%20R2%20SDK%20binaries%20into%20the%20CE%20install%20directory%20(Program%20Files%5CMicrosoft%5CExchange%20Server%5Cv14%5CBin).%20%3CBR%20%2F%3E%E2%80%A2%20Microsoft.EnterpriseManagement.OperationsManager.Common.dll%20%3CBR%20%2F%3E%E2%80%A2%20Microsoft.EnterpriseManagement.OperationsManager.dll%20%3CBR%20%2F%3E%E2%80%A2%20MomBidLdr.dll%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E**UPDATE%3A%20Files%20attached%20to%20this%20blog%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%20Where%20can%20you%20find%20the%20above%20binary%20files%3F%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EThe%20SCOM%202007%20R2%20SDK%20Binaries%20Microsoft.EnterpriseManagement.OperationsManager.Common.dll%20and%20Microsoft.EnterpriseManagement.OperationsManager.dll%20can%20be%20found%20on%20a%20system%20that%20has%20SCOM%202007%20R2%20Console%20in%20the%20following%20directory%20Program%20Files%5CSystem%20Center%20Operations%20Manager%202007%5CSDK%20Binaries.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EThe%20MOmBidLdr.dll%20can%20be%20found%20can%20be%20found%20on%20a%20system%20that%20has%20SCOM%202007%20R2%20Console%20in%20the%20following%20directory%20Program%20Files%5CSystem%20Center%20Operations%20Manager%202007%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMethod%202%3A%20%3C%2FSTRONG%3E%20%3CSTRONG%3E%20Disable%20the%20Automatic%20Alert%20Resolution%20Feature%20in%20the%20Correlation%20Engine%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBy%20following%20this%20approach%20the%20customer%20will%20lose%20the%20ability%20to%20resolve%20the%20alerts%20automatically%20via%20the%20Exchange%20Correlation%20Engine.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20disable%20Automatic%20Alert%20Resolution%2C%20perform%20the%20following%20steps%3A%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ELog%20on%20to%20the%20server%20that's%20hosting%20the%20Microsoft%20Exchange%20Monitoring%20Correlation%20Engine%20service.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ELocate%20the%20Correlation%20Engine%20configuration%20file%20named%20Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config.%20By%20default%2C%20the%20file%20is%20located%20in%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV14%5CBin%5C%2C%20where%20C%3A%5C%20is%20the%20Exchange%20installation%20directory.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOpen%20Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config%20in%20a%20text%20editor%20such%20as%20Notepad%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ELocate%20the%20following%20line%20in%20the%20configuration%20file%3A%20%3CBR%20%2F%3E%3CADD%20key%3D%22%26quot%3BAutoResolveAlerts%26quot%3B%22%20value%3D%22%26quot%3Btrue%26quot%3B%22%3E%3C%2FADD%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EChange%20%3CADD%20key%3D%22%26quot%3BAutoResolveAlerts%26quot%3B%22%20value%3D%22%26quot%3Btrue%26quot%3B%22%3E%3C%2FADD%3E%20to%20%3CADD%20key%3D%22%26quot%3BAutoResolveAlerts%26quot%3B%22%20value%3D%22%26quot%3Bfalse%26quot%3B%22%3E%3C%2FADD%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ERestart%20the%20Microsoft%20Exchange%20Monitoring%20Correlation%20Engine%20service.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%20More%20Information%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EExchange%20Correlation%20Engine%3A%20%3CBR%20%2F%3E%3C%2FSTRONG%3E%20The%20Correlation%20Engine(CE)%20is%20a%20stand-alone%20Windows%20service%20that%20uses%20the%20Operations%20Manager%20SDK%20interface%20to%20first%20retrieve%20the%20health%20model%20(or%20instance%20space)%20and%20then%20process%20state%20change%20events.%20By%20maintaining%20the%20health%20model%20in%20memory%2C%20and%20processing%20state%20change%20events%2C%20the%20Correlation%20Engine%20is%20able%20to%20determine%20when%20to%20raise%20an%20alert%20based%20on%20the%20state%20of%20the%20system.%20The%20Correlation%20Engine%20solely%20relies%20on%20the%20Operations%20Manager%20SDK.%20It%20does%20not%20use%20the%20agent%20to%20perform%20any%20of%20the%20correlation%20and%20other%20aspects%20of%20its%20operations.%20For%20further%20details%2C%20you%20can%20also%20reference%20the%20%3CSTRONG%3E%20Exchange%202010%20Management%20Pack%20guide%20%3C%2FSTRONG%3E%20.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAutomatic%20Alert%20Resolution%20feature%20in%20Exchange%20Correlation%20Engine%3A%20%3CBR%20%2F%3E%3C%2FSTRONG%3E%20The%20Automatic%20Alert%20Resolution%20feature%20automatically%20closes%20related%20alerts%20when%20the%20Exchange%202010%20Management%20Pack%20determines%20that%20the%20underlying%20issue%20is%20no%20longer%20a%20problem.%20This%20feature%20is%20provided%20by%20the%20Correlation%20Engine%2C%20and%20is%20enabled%20by%20default.%20Using%20Automatic%20Alert%20Resolution%20can%20cause%20multiple%20alerts%20to%20be%20logged%20if%20the%20same%20alert%20is%20logged%20again%20for%20another%20instance%20of%20the%20problem%20before%20the%20associated%20ticket%20has%20been%20resolved%20by%20support%20teams.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20may%20also%20want%20to%20disable%20this%20feature%20under%20the%20following%20or%20other%20conditions%3A%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you're%20using%20ticketing%20or%20another%20support%20system%20that%20wouldn't%20work%20correctly%20if%20alerts%20are%20automatically%20resolved.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EIf%20you're%20using%20a%20connector%20with%20Operations%20Manager%202007.%20A%20connector%20is%20a%20custom%20service%20or%20program%20that%20allows%20Operations%20Manager%20to%20communicate%20with%20external%20systems.%20For%20example%2C%20you%20may%20want%20to%20disable%20this%20feature%20if%20you're%20using%20a%20connector%20that%20allows%20an%20external%20application%20to%20track%20Exchange%202010%20Management%20Pack%20alerts.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmsdnshared.blob.core.windows.net%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2Ftelligent.evolution.components.attachments%2F01%2F6699%2F00%2F00%2F03%2F64%2F81%2F09%2FSCOM2007FilesForEXCHCorrelationEngine.zip%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%20SCOM2007FilesForEXCHCorrelationEngine.zip%20%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-365787%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20TECHNET%20on%20Apr%2015%2C%202015%20While%20helping%20a%20customer%20migrate%20from%20SCOM%202007%20to%20SCOM%202012%20R2%2C%20we%20noticed%20a%20large%20reduction%20in%20Alerts%20for%20Exchange%202010.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-365787%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EJimmyHarper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Feb 20 2020 11:28 AM
Updated by: