Exchange 2010 SP1 on SBS 2011 - Blank Page when launching OWA

I have Exchange 2010 SP1installed on SBS 2011, when I attempt to launch OWA, i get a blank page. The URL displays: https://localhost/owa/auth/logon.aspx?url=https://localhost/owa/&reason=0

I have done/checked the following and none of them have resolved the issue:

1.      No event log errors  - just a Success log – indicating successfully launch of Outlook Web App
2.      Checked permissions on IIS  OWA virtual directories
3.      Checked OWA configuration ( Forms-based authentication) and restarted Forms based authentication service.
4.      Checked all pre-reqs for OWA have been installed
5.      Ran Updatecas.ps1 script
6.      Reset IIS
7.     Installed Roll Up 7

Does anyone have any other ideas or where else I should be looking.

Many thanks in advance
mandaljAsked:
Who is Participating?
 
mandaljAuthor Commented:
I'm leaning towards uninstalling/reinstalling IIS & CAS?
0
 
LeeDerbyshireCommented:
It would be interesting to see the IIS log entries.  Look for the most recent file in C:\Inetpub\logs\LogFiles\W3SVC1 , and double-click it to open it in Notepad.  You should see entries containing GET /owa followed by GET requests for the logon.aspx file you already mentioned.  Let us know if you find them.
0
 
mandaljAuthor Commented:
See attached for iislog
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
mandaljAuthor Commented:
I also deleted and created the OWA virtual directories - still no luck.
0
 
LeeDerbyshireCommented:
Sorry, I don't see an attachment anywhere.  Can you see it?
0
 
mandaljAuthor Commented:
Sorry, try now.
IISLog.bmp
0
 
Rob WilliamsCommented:
Are you using the FQDN?  SBS 2003 allowed you to use localhost, servername, or the IP but SBS 2008/2011 requires the correct URL, even internally.  The default would be:
https://remote.YourPublicDomain.abc/owa
0
 
mandaljAuthor Commented:
Yes, I am, but it still fails.
0
 
LeeDerbyshireCommented:
Thanks for the screen shot, but it would help more to see the full copied/pasted lines instead of just the first part.  The most interesting part is right at the end (the last four numbers of each line), but unfortunately, it got clipped from the image for the lines we're most interested in.
0
 
Exchange_GeekCommented:
I'd agree I've seen two such instances before while working with Microsoft for different customers and want to check if you faced a similar issue, it can be only checked if you upload the IIS logs for us.

If your errors match, we can fix this with just slight modifications on IIS.

Regards,
Exchange_Geek
0
 
mandaljAuthor Commented:
Thanks. The logs will be uploaded tonorrow.
0
 
Exchange_GeekCommented:
Great :)

Regards,
Exchange_Geek
0
 
mandaljAuthor Commented:
Here's the IIS Log
IIS-Log.txt
0
 
LeeDerbyshireCommented:
Interesting - you can see that requests for .css (and some other) files are getting a 403.1 response

2012-08-16 16:07:33 ::1 GET /owa/14.1.420.0/themes/resources/logon.css - 443 - ::1 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET4.0C;+.NET4.0E;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+InfoPath.3;+MS-RTC+EA+2) https://localhost/owa/auth/logon.aspx?url=https://localhost/owa/&reason=0 403 1 5 17

which means something like Execute Access Denied.  But these aren't executable files, so something appears to be misconfigured in IIS.  First, I would look at the properties of the default web site, and then look at the list of MIME types.  Just make sure that .css is in the list, and has a mime type of "text/css" .
0
 
mandaljAuthor Commented:
Thanks. The default web site looks fine. Also MIME types were present.
0
 
LeeDerbyshireCommented:
Well, that's another possibility.  I don't like reinstalling on a production server myself, but lots of other people just go for it.
0
 
Exchange_GeekCommented:
Check for the solution mentioned in KB http://support.microsoft.com/kb/942065

Regards,
Exchange_Geek
0
 
mandaljAuthor Commented:
Thanks for the responses. Just waiting for MS to provide some assistance.
0
 
mandaljAuthor Commented:
Not an ideal solution, but it worked.
0
 
mediamanagerCommented:
Can you be more precise? What solution did work for you? (having the same problem on a SBS 2011 machine)
0
 
mandaljAuthor Commented:
The solution detailed in KB9426065 worked for me.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.