[Edit: I did figure out a little more of the issue. I have figured out that what is causing this is the IIS Application Poll that The Exchange 2013 installer creates by default when installing called "MSExchangeRpcProxyAppPool". The server is recycling the RPC Application Pool every 20 - 30 minutes or so. I have recycling completely turned off  on this pool yet it still restarts which leads me to believe it may be a code problem since it only should recycle if the poll crashes. Short of a bug in the code somewhere, I for the life of me can not find why the Application Pool keeps restarting. This is the only pool out of all the ones Exchange created during installation that is recycling constantly. It is frustrating because our Outlook Anywhere clients keep getting disconnection messages several times an hour because of this. The event logs I listed below are the only event logs I can find that trigger when the pool recycles, so as you can see, they give me no useful information in debugging the problem.]

This problem only applies to outlook clients using RPC over HTTP. ActiveSync, OWA and EWS are working fine.

There is a problem with the RPC over HTTP tunnel on our server. Every 20-30 minutes, sometimes more sometimes less, but usually with in that 20-30 minute timeframe, the RPC over HTTP tunnel drops and all Outlook Anywhere clients get immediately disconnected. IT comes back up very fast and all clients reconnect with in a matter of seconds. Not a huge deal for people using cached mode outlook but all the non-cached mode people (Thin clients are an example are not using cached mode to save diskspace). People using non-cached mode would get a couple errors pop up and outlook stopped working.

The only relevant entries I have found in the exchange server event log are here. These same grouping of events show up everytime the RPC over HTTP tunnel shuts down and restarts. I just can't figure out why its doing it:

1-23-2013 9:21:18 AM RPC Proxy 4 (1)
-- RPC Proxy successfully loaded in Internet Information Services (IIS).

1/23/2013 9:22:41 AM WAS 5138 None
--- A worker process '75832' serving application pool 'MSExchangeRpcProxyAppPool' failed to stop a listener channel for protocol 'http' in the allotted time.  The data field contains the error number.

1/23/2013 9:22:41 AM WAS 5013 None
--- A process serving application pool 'MSExchangeRpcProxyAppPool' exceeded time limits during shut down. The process id was '75832'.

Hi Trent. I have the same exact problem... every 15-20 min

Martin

Hello,

Thank you for your post.

This is a quick note to let you know that we are performing research on this issue.

Thanks,

try the below :)

a long term work around by adding a registry key that extends the timeout with the following key

HKEY_LOCAL_MACHINE/Software/Policies/Microsoft/Windows NT/MinimumConnectionTimeout

With a DWORD VALUE of 120

try the below :)

a long term work around by adding a registry key that extends the timeout with the following key

HKEY_LOCAL_MACHINE/Software/Policies/Microsoft/Windows NT/MinimumConnectionTimeout

With a DWORD VALUE of 120

See, I found that possible solution through some google searches. I tried that a few weeks ago and it seemed to work for a few days but then started doing it again.

After I posted this thread, the RPC Tunnel started behaving for a couple days and didn't drop connections, through no action from me. I checked again before I posted this reply and noticed the exchange server started dropping all RPC over HTTP connections again every 20-20 minutes this morning right after midnight and has been doing it ever since.

That DWORD value has been set on the server since the middle of December, and I did double check to make sure it was still set. I've rebooted the server several times since I set that value as well.

Still no news regarding this issue... I have also tried to set the MinimumConnectionTimeout without any luck

Martin

I know, it still happens sporadically to me still. Not sure why my response was marked as an "answer", I wasn't saying it was fixed, I was saying that it still happens.

As an example, this weekend, the exchange server worked perffectly. IT wasn't disconnecting outlook clients connected via RPC over HTTPS and was behaving really well.

I came into the office this morning and the server was doing it again. All clients connected via RPC over HTTPS have been disconnecting and reconnecting every 20-30 minutes since midnight this morning. Nothing was done by me or anyone else that would have changed anything or make the RPC over HTTP start being unstable again.

I have set that Registry value and all it did was turn a chronic problem into a sporadic problem.

Hello,

 

Thank you for your post.

 

This is a quick note to let you know that we are performing research on this issue.

 

Thanks,

Hello

Did you find anything about this problem, since last post?

Thanks.