https://evan.wtf/tags/0x800703e9/Recent content in 0x800703e9 on Evan HoffmanHugoen-USEvan HoffmanMon, 17 Jan 2011 19:09:15 +0000https://evan.wtf/2011/01/17/exchange-cas-crashes-users-get-503-when-accessing-owa-but-activesync-works/Mon, 17 Jan 2011 19:09:15 +0000https://evan.wtf/2011/01/17/exchange-cas-crashes-users-get-503-when-accessing-owa-but-activesync-works/<p>Since migrating to Exchange 2010, every couple of weeks it looks like IIS crashes on the CAS. Going to the OWA URL in a browser would yield a 503 error. Strangely enough, ActiveSync worked fine (though Outlook Anywhere over HTTPS didn&rsquo;t). Rebooting the CAS resolved the issue.</p> <p>This is what the logs show (<a href="http://www.websitepulse.com/">Website Pulse</a> reported the outage around 11:45):</p> <pre tabindex="0"><code>Information 1/16/2011 11:59 EventLog 6013 None The system uptime is 1726976 seconds. Error 1/16/2011 11:43 Microsoft-Windows-WAS 5002 None Application pool &#39;MSExchangeOWAAppPool&#39; is being automatically disabled due to a series of failures in the process(es) serving that application pool. Warning 1/16/2011 11:43 Microsoft-Windows-WAS 5011 None A process serving application pool &#39;MSExchangeOWAAppPool&#39; suffered a fatal communication error with the Windows Process Activation Service. The process id was &#39;13180&#39;. The data field contains the error number. Warning 1/16/2011 11:43 Microsoft-Windows-WAS 5011 None A process serving application pool &#39;MSExchangeOWAAppPool&#39; suffered a fatal communication error with the Windows Process Activation Service. The process id was &#39;12856&#39;. The data field contains the error number. Warning 1/16/2011 11:42 Microsoft-Windows-WAS 5011 None A process serving application pool &#39;MSExchangeOWAAppPool&#39; suffered a fatal communication error with the Windows Process Activation Service. The process id was &#39;15328&#39;. The data field contains the error number. Warning 1/16/2011 11:41 Microsoft-Windows-WAS 5011 None A process serving application pool &#39;MSExchangeOWAAppPool&#39; suffered a fatal communication error with the Windows Process Activation Service. The process id was &#39;11724&#39;. The data field contains the error number. Warning 1/16/2011 11:41 Microsoft-Windows-WAS 5009 None A process serving application pool &#39;MSExchangeOWAAppPool&#39; terminated unexpectedly. The process id was &#39;15868&#39;. The process exit code was &#39;0x800703e9&#39;. Information 1/16/2011 11:21 Service Control Manager 7036 None The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped state. </code></pre><p>This happened before we had any antivirus on the machine (antivirus has been suggested as a culprit). The machine is Win 2008r2 x64 with all updates running Exchange 2010 with all updates.</p>