OWA error http 500 when mailbox is on one particular backend server
Hi We are experiencing an Error Http 500 when trying to connect to one of our mailbox servers via Outlook Web Access on one particular mailbox server . Here is our setup: ISA 2006 Server in the DMZ presents the initial login page fine. Put in user credentials and the request goes off to our Exchange Front End Server (Exchange 2003 SP2) If a users mailbox is on MAILSERVER3 they get an HTTP 500 This page cannot be displayed error. If their mailbox is on one of the two other mailbox servers, or if their mailbox is moved back to one of the others, the problem goes away. All Exchange servers are running Windows 2003 SP2 Exchange 2003 SP2. I rebooted the MAILSERVER3 server and the problem went away for a couple of days but now it is back!! Restarting the Exchange Virtual Server on MAILSERVER3 makes no difference Any advice appreciated! Thanks Andy
November 26th, 2010 4:29am

could you check the application pool for owa on Mailserver3, is it still alive during error message comes out? and check this KB http://support.microsoft.com/kb/829167/en-us
Free Windows Admin Tool Kit Click here and download it now
November 26th, 2010 4:43am

Hi Sangok Thanks very much for the idea, unfortunately we checked what you suggested and the application pools are running when we try to log in via OWA. We also followed the tech note and all looked to be correct. We hadn't thought of checking this though so please keep the ideas coming as we are stumped! Thanks again Andy
November 26th, 2010 6:03am

Hi again OK your idea has helped us narrow down the problem by thinking about IIs on our mailbox servers. Doing a little testing we find that if I log onto either of the healthy mailbox servers, from an ie session, if I browse to localhost I receive the standard IIS message - page under construction. If however I do this on MAILSERVER3 I get "Internet Explorer cannot display this web page" I feel we might be homing in to the problem! Any tips of what to check next would be appreciated Thanks again Andy
Free Windows Admin Tool Kit Click here and download it now
November 26th, 2010 6:38am

Hi, alyne 1. netstat -na | findstr ":80" netstat -na | findstr ":443" Web port is listening correctly? Proto Local Address Foreign Address State TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 2. Check IIS Manager on Default Web Site binding setting which is All Unassigned IP binding 3. IISAdmin, W3SVC Service are running state verify owa site working correctly http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html http://support.microsoft.com/kb/830827/en-us
November 29th, 2010 1:37am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics