Article ID: 2832198 - View products that this article applies to.
Assume that you install Microsoft Exchange 2010 Service Pack 3 (SP3) in an Exchange Server environment. There are many Outlook Anywhere (RPC over HTTP) clients in the environment. When the Outlook Anywhere clients try to connect to the Exchange server, the Outlook Anywhere clients are not connected. Additionally, the Outlook Anywhere clients receive the following error message:
503 Service Unavailable
This issue occurs because the limit of RPC over HTTP requests that ASP.NET can process is reached.
The RPC over HTTP requests in Exchange Server 2010 SP3 rely on the ASP.NET runtime to process the requests. However, the default limit of ASP.NET requests is 25,000.
Note In versions of Exchange Server earlier than Exchange Server 2010 SP3, RPC over HTTP requests do not rely on the ASP.NET runtime, and they are not affected by the request limit.
To resolve this issue, increase the limit of ASP.NET requests to the recommended value of 65535. To increase the limit of ASP.NET requests, follow these steps:
You can use the following counters to monitor the number of ASP.NET requests and RPC over HTTP connections:
2013-03-21 23:06:14 10.0.0.1 RPC_OUT_DATA /rpc/rpcproxy.dll cas.contoso.com:6001 443 CONTOSO\user 10.0.0.10 MSRPC 503 3 0 15
2013-03-21 23:06:15 10.0.0.1 RPC_IN_DATA /rpc/rpcproxy.dll cas.contoso.com:6001 443 CONTOSO\user 10.0.0.10 MSRPC 503 3 0 46
Article ID: 2832198 - Last Review: May 28, 2013 - Revision: 6.0