Memory leak or memory corruption occurs in Exchange Server 2010

Symptoms

When some RPC requests return ecMaxThreadsPerMdbExceeded or ecMaxThreadsPerSCTExceeded errors in a Microsoft Exchange Server 2010 environment, a memory leak or memory corruption occurs on Exchange Client Access servers or Hub Transport servers. Additionally, Microsoft Outlook cannot connect to Exchange servers, and some events that resemble the following are logged in the event log:
ID:       4999
Level:    Error
Source: MSExchange Common
Machine: Machine 
Message:  Watson report about to be sent for process id: ProcessID, with parameters: E12N, Build Type, Application Version, edgetransport.exe, EXCHMEM.dll, Call Stack Hash, c0000005, Call Stack Hash, Assembly Version.

ID:       10003
Level:    Error
Source: MSExchangeTransport
Machine:  Machine
Message:  The transport process failed during message processing with the following call stack: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

ID:       4999
Level:    Error
Source: MSExchange Common
Machine: Machine
Message:  Watson report about to be sent for process id: ProcessID, with parameters: E12N, Build Type, Application Version, Microsoft.Exchange.RpcClientAccess.Service.exe, EXCHMEM.dll, Call Stack Hash, c0000005, Call Stack HashAssembly Version.

Cause

This issue occurs because the allocated memory is not freed before retrying the failed RPC requests.

Resolution

To resolve this issue, install the following update rollup:
2917508 Description of Update Rollup 5 for Exchange Server 2010 Service Pack 3

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 2919513 - Last Review: 25 Feb 2014 - Revision: 1

Feedback