On the client access server the following application pools continued to crash even after restarting them:
The following errors were experianced in the system log in event viewer:
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 11/11/2009
Time: 2:06:56 PM
User: N/A
Computer: EXCHANGESERVER
Description:
A process serving application pool 'MSExchangeUMAppPool' reported a failure. The process id was '8048'. The data field contains the error number.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 11/11/2009
Time: 2:06:56 PM
User: N/A
Computer: EXCHANGESERVER
Description:
A process serving application pool 'DefaultAppPool' reported a failure. The process id was '9136'. The data field contains the error number.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 11/11/2009
Time: 2:06:56 PM
User: N/A
Computer: EXCHANGESERVER
Description:
A process serving application pool 'MSExchangeAutodiscoverAppPool' reported a failure. The process id was '4712'. The data field contains the error number.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 11/11/2009
Time: 2:06:56 PM
User: N/A
Computer: EXCHANGESERVER
Description:
A process serving application pool 'MSExchangeOWAAppPool' reported a failure. The process id was '7460'. The data field contains the error number.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 11/11/2009
Time: 2:06:56 PM
User: N/A
Computer: EXCHANGESERVER
Description:
A process serving application pool 'MSExchangeServicesAppPool' reported a failure. The process id was '4016'. The data field contains the error number.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Date: 11/11/2009
Time: 2:07:02 PM
User: N/A
Computer: EXCHANGESERVER
Description:
Application pool 'MSExchangeAutodiscoverAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 11/11/2009
Time: 2:07:02 PM
User: N/A
Computer: EXCHANGESERVER
Description:
A process serving application pool 'MSExchangeOWAAppPool' reported a failure. The process id was '1352'. The data field contains the error number.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Date: 11/11/2009
Time: 2:07:40 PM
User: N/A
Computer: EXCHANGESERVER
Description:
Application pool 'MSExchangeOWAAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
These problems occured because .NET framework 1.1 was installed on a x64 exchange server. .NET framework 1.1 only comes in 32bit. When you install it on a x64 server it enables 32bitAppOnWin64 for IIS which causes the application pools to crash. To resolve this problem perform the following acctions:
1. Uninstall .NET Framework 1.1 from add and remove windows components.
2. Disable 32bit support in IIS by running the following command:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
3. Reinstall ASP.NET by running the following command:
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
4. Restart IIS by running the following command:
iisreset
Here is a list of all commands entered into the shell to resolve the problem, click to expand:
Now OWA is working again as normal:
This was an absolute life saver. I will put an article on my site linking to yours about this issue along with my symptoms. Keep up the good work with post like this.
ReplyDeleteI have same issue on server 2008, I did try as per above, but had no luck, I already Installed 2010 on windows server 2008 R2 edition,I am getting http error 503. the service is unavailable. After entering Username & Password on OWA Page, & I Saw MSExchnageOwAAppPoll is stoped in IIS under Application Pool, I tried to troubleshoot as per above but no luck
ReplyDeleteBrilliant! Exactly what I needed after installing PFDAVAdmin on my Exchange box. Use PFDAVAdmin from a desktop people! Thanks Clint!
ReplyDeleteYour solution worked perfectly. I installed the Exchange BPA to troubleshoot an unrelated issue. The BPA installation required .NET Framework 1.1, so I installed it, as well. Even after uninstalling .NET 1.1 the problem still occurred. Thanks for taking the time to post a solution!
ReplyDelete