Hi All:
I've just run into an issue with my exchange OWA. It returns a blank page with the url string https://www.xxxxxxxx/&reason=0.
Nothing in the logs gives me any good reasons.
Here's what I've done so far; 1) reinstall Exchange roll-up 7. 2) recreate virtual directories. 3) reboot. (this was mostly a shot in the dark, but what the hell)
Exchange via rpc/https is still working great.
Anyone run into this before?
EDIT Here is the last snippet from the OWASetupLog. doesn't look like anything blew up.
[09:45:36] *******************************************
[09:45:36] * UpdateOwa.ps1: 5/27/2009 9:45:36 AM
[09:45:40] Updating OWA on server HOMER
[09:45:40] Finding OWA install path on the filesystem
[09:45:40] Updating OWA to version 8.1.375.2
[09:45:40] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.1.375.2'
[09:45:41] Getting all Exchange 2007 OWA virtual directories
[09:45:42] Found 1 OWA virtual directories.
[09:45:42] Updating OWA virtual directories
[09:45:42] Processing virtual directory with metabase path 'IIS://HOMER.DG.LOCAL/W3SVC/1/ROOT/owa'.
[09:45:42] Metabase entry 'IIS://HOMER.DG.LOCAL/W3SVC/1/ROOT/owa/8.1.375.2' exists. Removing it.
[09:45:42] Creating metabase entry IIS://HOMER.DG.LOCAL/W3SVC/1/ROOT/owa/8.1.375.2.
[09:45:42] Configuring metabase entry 'IIS://HOMER.DG.LOCAL/W3SVC/1/ROOT/owa/8.1.375.2'.
[09:45:43] Saving changes to 'IIS://HOMER.DG.LOCAL/W3SVC/1/ROOT/owa/8.1.375.2'
[09:45:43] Saving changes to 'IIS://HOMER.DG.LOCAL/W3SVC/1/ROOT/owa'
-
This error is usually related to a roll-up install.
Can you check the Logs at %systemdrive%\ExchangeSetupLogs\UpdateOwa.log to see if there is anything in there indicating an error.
This error can also occur if the ExchangeSetupLogs folder is missing from the root of the system drive during setup. If it is, restore the folder and install the rollup again.
From Sam Cogan -
Open Exchange Management Shell and run updateowa.ps1. How to remove and to reinstall IIS on a computer that is running Exchange Server might also help.
Dayton Brown : Unfortunately this one was too late for me. I ended up redoing the server and that fixed it:-\From Luke99
0 comments:
Post a Comment