Topic Last Modified: 2009-04-29
This topic provides information about how to troubleshoot a message from Microsoft Operations Manager (MOM) that says that a log file cannot be replayed and that the passive node must be reseeded.
In this scenario, the MOM message resembles the following:
|
Log file LogFileName.log in Server_Location could not be replayed. Re-seeding the passive node is now required |
Additionally, the Application log that is located on the server that is identified in the message may include the following event messages:
Event ID 419
|
Event Type: Error Event Source:ESE Event Category: Logging/Recovery Event ID: 419 Description: Microsoft.Exchange.Cluster.ReplayService (6608) Recovery E07: Unable to read page Number of database Path_Of_Database. Error -1018. |
Event ID 454
|
Event Type: Error Event Source:ESE Event Category: Logging/Recovery Event ID: 454 Description: Microsoft.Exchange.Cluster.ReplayService (6608) Recovery E07: Database recovery/restore failed with unexpected error -1018. |
Event ID 2095
|
Event Type: Error Event Source:MSExchangeRepl Event Category: Service Event ID: 2095 Description: Log file Log_Name.log in Computer_Name could not be replayed. Re-seeding the passive node is now required. Use the Update-StorageGroupCopy cmdlet in the Exchange Management Shell to perform a re-seed operation. |
When this occurs, view the log file on the relevant server to determine whether the database is healthy. If the log file on the server reports that a recent log was the last to be replayed, and the copy is healthy, you do not have to reseed the passive node. If the log file reports that the database is corrupted, reseed the passive node.
For more information about how to reseed the passive node, see the following topics: