The Microsoft Exchange Replication Service is either stopping or stopping a replication instance
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:
From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.
From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.
To learn more about this alert, if you are using System Center Operations Manager 2007, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the events that have been logged that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
2007;2009;2011 |
Event Source |
MSExchangeRepl |
Alert Type |
Warning |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Mailbox/Continuous Replication |
MOM Rule Name |
The Microsoft Exchange Replication Service is either stopping or stopping a replication instance. |
Explanation
The alert indicates that the Microsoft Exchange Replication (MSExchangeRepl) Service is either stopping or stopping a replication instance to a storage group because of a number of reasons: the computer shut down, or the administrator disabled replication to a storage group, or the administrator manually stopped the replication service, or because configuration for replication has changed.
Note
The replication service provides replication functionality that is used by local continuous replication (LCR) and cluster continuous replication (CCR).
As soon as the replication service stops, logs will not be copied and replayed to the passive copy. This could lead to an accumulation of logs on the active node. When the replication service starts again, log copying and replay will resume on the passive copy.
The causes related to this alert are listed below depending on the particular event that caused the alert. The events that can trigger this alert are MSExchangeRepl 2002, MSExchangeRepl 2007, and MSExchangeRepl 2011. For detailed information about each of thes events, visit the Events and Errors Message Center.
User Action
To resolve this alert, do one or more of the following depending on the event or events that caused the issue:
If the alert is caused by MSExchangeRepl 2002, the Microsoft Exchange Replication Service may start automatically. If the service does not start automatically, check the Services snap-in to make sure that the Microsoft Exchange Replication service is configured to restart automatically.
If the alert is caused by MSExchageRepl 2007, consider the following:
If the replication instance stopped because of a configuration change, no user action is needed.
If the replication instance stopped because an administrator disabled LCR, enable LCR. For detailed steps, see How to Enable Local Continuous Replication for an Existing Storage Group.
You can determine whether replication has failed by running the Get-StorageGroupCopyStatus cmdlet. For more information about Get-StorageGroupCopyStatus, see Get-StorageGroupCopyStatus. If the status summary returned by this cmdlet shows that replication failed, look for one of the following events in the Application log under the MSExchangeRepl source for more information: MSExchangeRepl events from 2056 through 2082; MSExchangeRepl events from 2095 through 2098; and MSExchangeRepl event ids 2101 and 2106.
If the alert is caused by MSExchangeRepl 2009, no user action is needed. This event notifies the administrator that the new active node has finished preparing its copy of the database.
If the alert is caused by MSExchangeRepl 2011, follow one or more of these steps:
If the replication instance stopped because of a configuration change, no user action is needed.
Look in the Application log to see whether a CMS move or failover occurred. If an unscheduled failover occurred, you must investigate the cause of the failover by reviewing the Application log.
You can determine whether replication failed by running the Get-StorageGroupCopyStatus cmdlet. For more information about Get-StorageGroupCopyStatus, see Get-StorageGroupCopyStatus. If the status summary returned by this task shows that replication failed, look for one of the following events in the Application log under the MSExchangeRepl source for more information: MSExchangeRepl events from 2056 through 2082; MSExchangeRepl events from 2095 through 2098; and MSExchangeRepl event ids 2101 and 2106.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.