Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
A memory leak occurs in the Microsoft.Exchange.Monitoring.exe process when you run the "Test-OwaConnectivity" cmdlet or the "Test-ActiveSyncConnectivity" cmdlet in the EMS on an Exchange Server 2010 server
Article ID: 2445121 - View products that this article applies to.
You run the Test-OwaConnectivity cmdlet or the Test-ActiveSyncConnectivity cmdlet in the Exchange Management Shell (EMS) on a Microsoft Exchange Server 2010 server. The connection times out. In this situation, a memory leak occurs in the Microsoft.Exchange.Monitoring.exe process. Additionally, the Exchange Server 2010 server experiences multiple issues, such as a slow response.
Note The Virtual Bytes counter of the Microsoft.Exchange.Monitoring.exe process increases to 1 GB or bigger in Performance Monitor.
This issue occurs because an asynchronous HTTP Request is called by the httpWebRequest.BeginGetResponse() method in the Test-OwaConnectivity cmdlet and in the Test-ActiveSyncConnectivity cmdlet. However, if the connections time out, the httpWebRequest.EndGetResponse() method does not call to release memory.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2529939/ )Description of Update Rollup 3 for Exchange Server 2010 Service Pack 1
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Test-ActiveSyncConnectivity cmdlet, visit the following Microsoft website:
General information about Test-ActiveSyncConnectivity cmdletFor more information about the HttpWebRequest methods, visit the following Microsoft website:
General information about the HttpWebRequest methods
Article ID: 2445121 - Last Review: October 26, 2012 - Revision: 3.0