Symptoms
When you perform a database recovery in Microsoft Exchange Server 2013, and you try to replay more than 1,000 transaction log files, the Microsoft Exchange Replication service terminates unexpectedly. When this problem occurs, the event ID 4399 and event ID 4999 are logged in the Application log as follows:Log Name: ApplicationSource: MSExchangeRepl Event ID: 4399 Task Category: Service Level: Error Keywords: Classic User: N/A Description: The Microsoft Exchange Replication service is terminating without collecting a Watson dump.Error The Microsoft Exchange Replication service is using too much memory (2279.62109375 MiB) and will beterminated without collecting a Watson dump. This exceeds the maximum expected value of 2048 MiB. To takea dump along with the Watson report, set registry key 'SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters\EnableWatsonDumpOnTooMuchMemory' to 1. Default can be overridden by setting registry keySOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters\MaximumProcessPrivateMemoryMB.Log Name: ApplicationSource: MSExchange CommonEvent ID: 4999 Task Category: GeneralLevel: Error Keywords: ClassicUser: N/A Description: Watson report about to be sent for process id: 2524, with parameters: E12, c-RTL-AMD64,15.00.0620.029, msexchangerepl, unknown, unknown, M.E.C.Replay.ReplayServiceTooMuchMemoryNoDumpException,0, unknown. ErrorReportingEnabled: True
Cause
This problem may occur because the replication service has a default limit of 2 gigabytes (GB) of memory. When this limit is reached, the process terminates.
Workaround
To work around this problem, add the following registry subkey, and then add the specified values to the new subkey:
SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters\
dword: MaximumProcessPrivateMemoryMBValue: 8192Base: Decimaldword: MemoryLimitBaseInMBValue: 4096Base: decimal
Status
This problem is scheduled be resolved in a future cumulative update for Exchange 2013.
