OWA not working after applying SP3 to Exchange 2007

Last night we applied SP3 to Exchange 2007.  Outlook access is fine but OWA stopped working.  
Just get back "Internet Explorer cannot display the web page" whether outside or inside of our
network.  Looking for troubleshooting steps to see if it is an Exchange, IIS, Certificate, etc. issue.
davidmoralesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

endital1097Commented:
is there an http error code displayed in the web browser?
check the iis logs for the connection attempt
davidmoralesAuthor Commented:
Just "Internet Explorer cannot display the webpage".  No other message or error code.  As for the IIS logs, where would I look for that exactly?  I checked the \\inetpub\logs\logfile directory but did not see anything for the times I attempted.  I've seen some postings with this error message that pertain to
certificate issues.  Not sure if there were any post-upgrade steps I needed to take after applying the
Service Pack.  I did not see any in the release notes.
endital1097Commented:
make sure that the www service is running on the cas server and that the default web site is in a running state

also attempt to go to owa using the ip address to eliminate a name resolution issue

certificate issue would cause a 403 error or cert prompt
CEOs need to know what they should worry about

Nearly every week during the past few years has featured a headline about the latest data breach, malware attack, ransomware demand, or unrecoverable corporate data loss. Those stories are frequently followed by news that the CEOs at those companies were forced to resign.

davidmoralesAuthor Commented:
The www service is running (I restarted to see if that helped).  The default web site is also running (also restarted to see if it helped).  I tried the using the internal IP from within our network and I get the same error screen.  
endital1097Commented:
the http logs should be under C:\inetpub\logs\LogFiles\W3SVC1 for a windows 2008 server
c:\windows\system32\logfiles\w3svc1 for windows 2003
davidmoralesAuthor Commented:
Below is what I can pull from the log related to OWA

2010-06-30 17:07:12 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 31
2010-06-30 17:07:12 10.10.1.54 GET /owa/ - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 401 2 5 0
2010-06-30 17:07:12 10.10.1.54 GET /owa/auth/logon.aspx url=https://gabriel.jpthegreat.org/owa/&reason=0 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 17:07:12 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 17:07:12 10.10.1.54 GET /owa/ - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 401 2 5 15
2010-06-30 17:07:12 10.10.1.54 GET /owa/auth/logon.aspx url=https://gabriel.jpthegreat.org/owa/&reason=0 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 17:07:12 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 17:07:12 10.10.1.54 GET /owa/ - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 401 2 5 0
2010-06-30 17:07:12 10.10.1.54 GET /owa/auth/logon.aspx url=https://gabriel.jpthegreat.org/owa/&reason=0 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 17:07:12 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 15
2010-06-30 17:07:12 10.10.1.54 GET / - 80 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 403 4 5 202
endital1097Commented:
you are getting a bunch of redirects 301s followed by an authorized 401 and the last entry is forbidden 403 on the main page (no /owa) most likely because require ssl is enabled

check the iis configuration for the owa directory under iis manager for a redirect setting and the authentication settings
something appears to have changed during the upgrade
davidmoralesAuthor Commented:
I have attached screen shots of those two IIS pages
IIS-Screens.pdf
endital1097Commented:
try changing the redirect by using the error pages
modify the 403 status code similar to the image below
this requires the ssl required to be enabled
redirect.PNG
davidmoralesAuthor Commented:
When I went to the Error Page for the OWA directory, I found that the redirect to the OWA site was already in place for Status Codes 403 and 403.4  
endital1097Commented:
then i would turn off the other redirect you have
davidmoralesAuthor Commented:
I removed the redirects then and reverted back to the canned error message files (i.e. 403.htm)  When I do this and try to access the site via https I get the same old message.  However, this time when I try to access via http it gives me the 403 message (See attached)
403-Screen.pdf
endital1097Commented:
now you need to turn the custom error page with the settings i gave earlier and you should be set
davidmoralesAuthor Commented:
I've attached the screen shot to make sure that I modified what you had suggested.  The problem is that even if I type in explicitly the URL we are redirecting to, it comes up with the original error.  If I'm misunderstood your earlier instructions, let me know.
Custom-Error.pdf
endital1097Commented:
attempt to access the site again after this change and check the iis logs for the most recent activity
davidmoralesAuthor Commented:
Here is whats in the log for this try

2010-06-30 19:18:52 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 19:18:52 10.10.1.54 GET /owa/ - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 401 2 5 0
2010-06-30 19:18:52 10.10.1.54 GET /owa/auth/logon.aspx url=https://gabriel.jpthegreat.org/owa/&reason=0 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 19:18:52 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 19:18:52 10.10.1.54 GET /owa/ - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 401 2 5 0
2010-06-30 19:18:52 10.10.1.54 GET /owa/auth/logon.aspx url=https://gabriel.jpthegreat.org/owa/&reason=0 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 19:18:52 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 19:18:52 10.10.1.54 GET /owa/ - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 401 2 5 0
2010-06-30 19:18:52 10.10.1.54 GET /owa/auth/logon.aspx url=https://gabriel.jpthegreat.org/owa/&reason=0 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 0
2010-06-30 19:18:52 10.10.1.54 GET /owa - 443 - 10.10.1.206 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2)+chromeframe/5.0.375.62 301 0 0 15
endital1097Commented:
the destination mailbox is on 2007, correct? it should not be doing a 301 redirect unless the mailbox is either on 2003 or in another site and it is redirecting to another cas server
davidmoralesAuthor Commented:
Yes, we are running only 1 server (Windows 2008) and that has Exchange 2007 SP3
davidmoralesAuthor Commented:
I was able to glean some more information on this problem.  I ran test-owaconnectivity and have attached the results of that.  I also was able to get OWA to come up if I turned off SSL on the root and owa pages as well as turned off the HTTP Redirect on the Default Web Site.  Coudl the problem just be perhaps with the SSL Certs needing to be reloaded after the update to SP3?
owa-test.pdf
davidmoralesAuthor Commented:
Ok, I was able to figure out the problem, although it seems kind of nonsensical.  After trying different settings with SSL on/off, HTTP redirects, etc. it seems that what fixed the problem was just changing the HTTP redirect on the Default web site to include the owa directory.  Somehow this was working in the RTM version of Exchange 2007 but maybe with SP3 the path had to be explictly stated.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
samcoryCommented:
How did you do that please
TriYoungCommented:
I had a very similar problem.  Post SP3 install the OWA site would not show up.  After checking it out a little I found that the https bindings for the Default web site were missing.  I added them back in and Poof it was fixed.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.