Sorry if this is in the wrong forum or has been addressed before. Here's what is going on: We have 2 Exchange 2003 servers, one operating as the back-end mail server and the other as the front-end OWA and push server. Last night, I applied updates that were pending for our servers, including these two. Unfortunately, I did not realize that the front-end server needed to be done first. Also, when updating the front-end server, one of the updates failed (KB976569 for Dot-Net 2.0 SP2). I had it install again this morning and it went in fine. However, OWA is not working now. I can get to the login page, but get an error page after trying to log in (error 500 - Internal Server Error to be exact). Any ideas what needs to be fixed? Thanks in advance.

Since updating, are all of your Exchange services running on that box?

All services that are set to Automatic are currently running. MS Exchange Event is set to manual and is not running, POP3 and Site Replication are both set to disabled.

On Mon, 15 Mar 2010 22:04:56 +0000, Steve - GOFCC Admin wrote:>Sorry if this is in the wrong forum or has been addressed before. Here's what is going on: We have 2 Exchange 2003 servers, one operating as the back-end mail server and the other as the front-end OWA and push server. Last night, I applied updates that were pending for our servers, including these two. Unfortunately, I did not realize that the front-end server needed to be done first. Also, when updating the front-end server, one of the updates failed (KB976569 for Dot-Net 2.0 SP2). I had it install again this morning and it went in fine. However, OWA is not working now. I can get to the login page, but get an error page after trying to log in (error 500 - Internal Server Error to be exact). Any ideas what needs to be fixed? Thanks in advance. Can you get to the default web site on the FE server?Can you connect directly to the BE server with a browser? How about tothe default web site on that machine?Sometimes running .Net updates undo stuff.Try running:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i-enable . . . and see if that gets things going.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

"Can you get to the default web site on the FE server?"Yes."Can you connect directly to the BE server with a browser? How about tothe default web site on that machine?"Yes."Sometimes running .Net updates undo stuff.Try running:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i-enable. . . and see if that gets things going."I get this..."Finished installing ASP.NET (2.0.50727).Setup has detected some errors during the operation. For details, please read the setup log file C:\DOCUME~1\ITSUPP~1\LOCALS~1\Temp\1\ASPNETSetup_00002.log"