Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

Outlook disconnects from Exchange 2013 several times an hour.

$
0
0

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'.

I have been searching for weeks on the problem and all I really have found is that the problem can sometimes be caused by RPC timeouts so I set the RPC timeout on the server to 120 seconds via the registry. That actually helped for about 5 days and then the problem mysteriously came back and I can not get it to go away even though the registry value is still set to 120 seconds on that RPC time out.

Does anyone else know of any thing else that causes this? Its Exchange 2013 on Server 2012 and is a pretty fresh install. Was setup in mid-December.


--Trent W.




Viewing all articles
Browse latest Browse all 10580

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>