OWA 2007 not displaying (blank page)
- Hi there..
I also had this problem, took a while to figure it out..
At first the page would not load and there would be a yellow exclamation mark in the bottom left corner, if you click that it would say “syntax error on line 7 of login.aspx” or something to that effect. After trying may things, I removed and then re-created the OWA virtual directory in IIS using . After this, the yellow exclamation mark in the bottom left corner went away and you were presented with a blank white page.
After much search around for some log file or explanation for why this was happening, I once again recreated the OWA virtual directory, checked all rights and permissions and still the blank white page.
In absolute desperation, I looked at the code in the source code for the OWA site, here are some of the relevant bits:
<!-- Copyright (c) 2006 Microsoft Corporation. All rights reserved. -->
<!-- OwaPage = ASP.auth_logon_aspx -->
<!-- {57A118C6-2DA9-419d-BE9A-F92B0F9A418B} -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; CHARSET=utf-8">
<meta name="Robots" content="NOINDEX, NOFOLLOW">
<title>Microsoft Exchange - Outlook Web Access</title>
<link type="text/css" rel="stylesheet" href="/owa/8.0.709.0/themes/base/logon.css">
<link type="text/css" rel="stylesheet" href="/owa/8.0.709.0/themes/base/owafont.css">
<script type="text/javascript" src="/owa/8.0.709.0/scripts/premium/flogon.js"></script>
Compared to another server of mine:
<!-- Copyright (c) 2006 Microsoft Corporation. All rights reserved. -->
<!-- OwaPage = ASP.auth_logon_aspx -->
<!-- {57A118C6-2DA9-419d-BE9A-F92B0F9A418B} -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; CHARSET=utf-8">
<meta name="Robots" content="NOINDEX, NOFOLLOW">
<title>Microsoft Exchange - Outlook Web Access</title>
<link type="text/css" rel="stylesheet" href="/owa/8.0.685.24/themes/base/logon.css">
<link type="text/css" rel="stylesheet" href="/owa/8.0.685.24/themes/base/owafont.css">
<script type="text/javascript" src="/owa/8.0.685.24/scripts/premium/flogon.js"></script>
Notice the difference in the paths.. the OWA virtual directory looks like this: (http://www.g7web.net/downloads/owa1.jpg)
Perhaps a dodgy update on the 29th or something, whatever the reason the files in the 8.0.709.0 folder don’t seem to be working, so, I used the files from the 8.0.685.24 folder and copied them into the 8.0.709.0 folder, now everything works!
Not sure what update of patch caused the problem, will do some more investigation into it.
Hope this helps someone.
Chris
All Replies
- Issue 2 toward the bottom of this Microsoft Knowledgebase article:
http://support.microsoft.com/default.aspx/kb/935490/en-us
explains that this problem (which I also suffered from) is caused by executing Update Rollup 2 for Exchange 2007 after having moved, renamed, or deleted the C:\ExchangeSetupLogs folder. I deleted mine after completing the install of Exchange, thinking that it was no longer needed.
The solution according to the article is to replace the folder or to recreate an empty folder and then to reapply the Rollup 2 update. The article supplies a link to the update. I created an empty folder and applied the update and OWA then worked like a charm.
I hope this helps others that suffer the same fate (and I have seen several posts out there!).
Art Everyone,
I am having the same problem as several others, but can not seem to get it resolved with the information here…
My setup is as follows:
Single Exchange 2003 Server supporting OWA, Mailboxes, Public folders and RPC-HTTP – works great, as designed, installed like a piece of cake 4 years ago.
Setting up a new Exchange 2007 SP1 server on Windows Server 2008 x64 Enterprise Edition (I have done about a dozen Exchange 2003 installs in the last 5 years, never had this many headaches, glad to see we are improving the install process along with the application – HINT, HINT)
The new server is also an all in one setup as once my mailboxes can be moved, the old server gets reloaded. So it is a BRAND NEW, Clean 2008 install with 2007 SP1 and for better or worse SP1 rollup update 1 for Exchange (this was installed directly behind the Exchange install so I do not know if OWA was working or not prior…)
I get the same reason 0 answer as everyone else, but deleting the folder and reinstalling update 1 did not help
Removing and reinstalling CAS did not help
I have a wildcard SSL Cert installed and set to be used by everything (the blank page does show it is secured by godaddy.com)
Copying the 8.1.240.5 – over the top 8.1.263.0 did not help
Uninstalling rollup 1, uninstalling CAS and reinstalling CAS did not help
Any Thoughts Comments or concerns would be appreciated
Thanks,
Daniel Ma Gill
- I had this error today and removing the sp1 rollup1 (rollup6) solved my problem. I've actually had lots of problems with these various rollups on several different client sites!
Did you ever get any resolution to this? I have Exchange Server 2007 SP1 installed on Windows Server 2008 as well. I have an empty 8.1.263.0 directory but 8.1.240.5 is full and correct.
Thanks,
Anthony
Hi Daniel--
I was having the same issue w/ all of the ***exact*** same problems you have listed. In my case, windows update had updated my server to SP1 rollup 1 prior to the client access role being applied. I thought i had tried everything and was really surprised when i got it working. This is what worked for me:
Un install SP1 rollup 1 from "installed updates". (owa still doesn't work at this point)
browse to your exchange install via windows explorer. go to the owa folder and delete folder/directory 8.1.263.0
start IIS 7 mgr and browse to the owa application > then expand the owa app. you will prob. still see an app / directory for 8.1.263.0 (I did) ? Right click on 8.1.263.0 and select remove.
now re-run the msp for exchange 2007 sp1 - rollup 1 (the file i ran was: Exchange2007-KB945684-x64-EN.msp).
notice that at the complete of the rollup 1 install you'll see a message saying the .net app needs to be created (never saw this before)...this took a good few minutes to complete. once this was done, i launched my exchange site / owa and (among the shock!) it worked....
this was something i had been working on for 2 days....and i couldn't find a single post that addressed this issue with SP1 rollup 1 (everyone talks about rollups withOUT sp1..)
hope this helps.
Curtis
Here is my updateowa.log file. the first 2 did not work...and the last one did...interesting (notice the log file says it is removing the app/metabase...but must have not been working correctly).
[08:56:18] ***********************************************
[08:56:18] * UpdateOwa.ps1: 4/19/2008 8:56:18 AM
[08:56:20] CAS role is not installed on server EXCH01
[12:20:07] ***********************************************
[12:20:07] * UpdateOwa.ps1: 4/26/2008 12:20:07 PM
[12:20:10] Updating OWA on server EXCH01
[12:20:10] Finding OWA install path on the filesystem
[12:20:10] Updating OWA to version 8.1.263.0
[12:20:10] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.1.263.0'
[12:20:14] Getting all Exchange 2007 OWA virtual directories
[12:20:16] Found 1 OWA virtual directories.
[12:20:16] Updating OWA virtual directories
[12:20:16] Processing virtual directory with metabase path 'IIS://exch01.local/W3SVC/1/ROOT/owa'.
[12:20:16] Metabase entry 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0' exists. Removing it.
[12:20:16] Creating metabase entry IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0.
[12:20:16] Configuring metabase entry 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0'.
[12:20:16] Saving changes to 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0'
[12:20:16] Saving changes to 'IIS://exch01.local/W3SVC/1/ROOT/owa'
[13:28:41] ***********************************************
[13:28:41] * UpdateOwa.ps1: 4/26/2008 1:28:41 PM
[13:28:42] Updating OWA on server EXCH01
[13:28:42] Finding OWA install path on the filesystem
[13:28:42] Updating OWA to version 8.1.263.0
[13:28:42] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.1.263.0'
[13:28:43] Getting all Exchange 2007 OWA virtual directories
[13:28:43] Found 1 OWA virtual directories.
[13:28:43] Updating OWA virtual directories
[13:28:43] Processing virtual directory with metabase path 'IIS://exch01.local/W3SVC/1/ROOT/owa'.
[13:28:43] Metabase entry 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0' exists. Removing it.
[13:28:43] Creating metabase entry IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0.
[13:28:43] Configuring metabase entry 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0'.
[13:28:43] Saving changes to 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0'
[13:28:43] Saving changes to 'IIS://exch01.local/W3SVC/1/ROOT/owa'
[14:22:06] ***********************************************
[14:22:06] * UpdateOwa.ps1: 4/26/2008 2:22:06 PM
[14:22:07] Updating OWA on server EXCH01
[14:22:07] Finding OWA install path on the filesystem
[14:22:07] Updating OWA to version 8.1.263.0
[14:22:07] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.1.263.0'
[14:22:11] Getting all Exchange 2007 OWA virtual directories
[14:22:11] Found 1 OWA virtual directories.
[14:22:11] Updating OWA virtual directories
[14:22:12] Processing virtual directory with metabase path 'IIS://exch01.local/W3SVC/1/ROOT/owa'.
[14:22:12] Creating metabase entry IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0.
[14:22:12] Configuring metabase entry 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0'.
[14:22:12] Saving changes to 'IIS://exch01.local/W3SVC/1/ROOT/owa/8.1.263.0'
[14:22:12] Saving changes to 'IIS://exch01.local/W3SVC/1/ROOT/owa'One of my user, suddenly getting the below erro, when he try to access his mailbox;
Outlook Web Access could not open the requested mailbox. Please verify that the address is spelled correctly. If the problem continues, contact technical support for your organization and tell them the following: No match was found for the address "smtp:XXX@nebs.com".
Any one knows, solution for this error?
I am using Exchange 2007 SP1/Windows 2003.
Many thanks to Chris for the post, after much pulling out of hair, I came across this solution and pleased to say it worked for me
Colin
I wonder if you can help. My sitution is similiar. Everything was working fine. rollup 3 was already installed on the exchange server. I installed rollup 3 on the domain controller that runs the exchange tools and the next day users said that no one could access OWA. internally or externally. they get a blank page. I have tried to reinstall rollup three on both servers and nothing. tried to recreate OWA virtual directory, nothing. restarted both servers and also restarted IIS again. nothing
any ideas??
- I had this issue on my exchange 2007 server. Have installed up through update rollup 4. After looking around, I decided to check the contents of the OWA sub folders at C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa. I had a total of 6 of the 8.1.... folders. The last two did not have any contents withint the Themes folders, so I copied the contents from one of the others into the last one, and that corrected the issue. Hope this helps someone else!
Joe I have Windows 2008 with a fresh copy of Exchange 2007 with rollup 5 installed through Windows update. I was receiving the reason=0 error for OWA. I tried every single one of these ideas and none worked. The following worked and did not affect anything on my existing Exchange 2007 server because it had the CAS role.
1. Uninstall CAS role by going to Programs and Features and clicking on Microsoft Exchange Server 2007 and clicking Uninstall
2. Deselect CAS role and uninstall
3. Remove the Owa, Autodiscover, exchweb and Sync folders from c:\program files\microsoft\exchange server\clientaccess
4. Reboot and re-install the CAS role
OWA loaded perfectly after this.
- The exact same thing as in the initial post still happens with Microsoft Update Rollup 6. (Disgusting, eh?) Copying files from subfolders from an earlier version (e.g. ..\client access\owa\8.1.375.2 to 8.1.393.1), then recreating the OWA virtual directory fixed the issue. I did not replace any new files that were placed by the rollup.
My setup is brand new. Windows Server 2008 64 bit w/ Exchange Server 2007 SP1. We applied rollup 6 last night, this morning OWA got the yellow exclamation mark in the bottom left corner. Error seen when double-click on mark:
Message: Syntax error
Line: 6
Char: 1
Code: 0
URI: https://myserver.com/owa/8.1.393.1/scripts/premium/uglobal.js
Thank you, Chris, for your initial post! I had the same problem as Chris but on a newer version (the 8.1.393.1 folder). Checked IIS and the folder was not created as an Application. After that I checked permissions on the folder against another “version folder” and in my case I had to change from basic authentication to anonymous authentication. I think my problem was that I needed to login to use the files that the login page needs to login the user J. But changing to anonymous on this folder removed that problem.
I have seen this issue sometimes when developing ASP.Net sites when you want to show some images for the layout of the login page and the user does not have access to the images before logging in
/Mårten
MHAfter the recent roll up 8.1.393.1, I had to do a combination of the above:
- Copy the contents of the subfolders of the previous update (in my case C:\Program Files\Microsoft\Exchange\ClientAccess\owa\8.1.340.0) to the same sub folders in the new 8.1.393.1 folder. The 8.1.393.1 subfolders (cabs, scripts, themes) were empty before!
- In IIS, convert the 8.1.393.1 directory to an Application and select the Owa pool.
- Change the authentication in IIS to anonymous.
- Restart IIS (I always do this after any IIS changes)
thanks for the pointers everyone, clearly something went wrong during the installation of the update. We also found that after the update nearly all of the Exchange services had been stopped and disabled!
