When a witness server of a Microsoft Exchange database availability group (DAG) is under a heavy workload, the Microsoft Exchange Replication service crashes on Exchange Server 2010 DAG members. Additionally, following error messages are logged on Exchange Server 2010 DAG members:
Note If you run the following cmdlet against the witness server from the DAG members, the WMI query fails:
Log Name: Application
Source: MSExchange Common
Date: Date
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
Watson report about to be sent for process id: Process ID, with parameters: E12, Build Type, Version, msexchangerepl, M.E.Cluster.Replay, M.E.C.A.AmHelper.GetBootTimeWithWmi, S.Management.ManagementException, XXXX, Version.
ErrorReportingEnabled: True
Log Name: Application
Source: MSExchangeRepl
Date: Date
Event ID: 2060
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
The Microsoft Exchange Replication service encountered a transient error while attempting to start a replication instance for mailbox database\mailbox server. The copy will be set to failed. Error: The NetworkManager has not yet been initialized. Check the event logs to determine the cause.
Source: MSExchange Common
Date: Date
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
Watson report about to be sent for process id: Process ID, with parameters: E12, Build Type, Version, msexchangerepl, M.E.Cluster.Replay, M.E.C.A.AmHelper.GetBootTimeWithWmi, S.Management.ManagementException, XXXX, Version.
ErrorReportingEnabled: True
Log Name: Application
Source: MSExchangeRepl
Date: Date
Event ID: 2060
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
The Microsoft Exchange Replication service encountered a transient error while attempting to start a replication instance for mailbox database\mailbox server. The copy will be set to failed. Error: The NetworkManager has not yet been initialized. Check the event logs to determine the cause.
(Get-WmiObject -Class Win32_OperatingSystem -ComputerName Witnessservername).LastBootUpTime