Ok I install Exchaneg 2007 Sp1 Rollup 1 and reboot. I was nto exepcting it as this update came via Automatic updates, so too late to stop it. Upon reboot OWA never comes up in IE, the URL ends in /owa&reason=0. Tried resinstalling the Rollup and rebooting again, no errors in the logs, actually log shows OWA starting fine. I see others have had similar issues in past but not same bug I am seeing. Any ideas?

Same Problem here. Win 2003 R2 SP 2, AMD Athlon 64 X2 Dual, Exchange 2007, even https://localhost/owa doesnt work anymore. With Firefox the login into owa ist possible, but Internet Explorer 7.0.5730.11 stops at https://localhost/owa/auth/logon.aspx?url=https://localhost/owa&reason=0in Adress line, bevore LOGIN into owa. c:\ExchangeSetupLogs\UpdateOwa.log [22:21:49] ***********************************************[22:21:49] * UpdateOwa.ps1: 17.08.2007 22:21:49[22:21:53] Updating OWA on server SERVER7[22:21:53] Finding OWA install path on the filesystem[22:21:53] Updating OWA to version 8.0.730.1[22:21:53] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.0.730.1'[22:21:58] Getting all Exchange 2007 OWA virtual directories[22:22:00] Found 1 OWA virtual directories.[22:22:00] Updating OWA virtual directories[22:22:00] Processing virtual directory with metabase path 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa'.[22:22:00] Creating metabase entry IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.730.1.[22:22:00] Configuring metabase entry 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.730.1'.[22:22:00] Saving changes to 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.730.1'[22:22:00] Saving changes to 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa'[00:31:08] ***********************************************[00:31:08] * UpdateOwa.ps1: 24.08.2007 00:31:08[00:31:11] Updating OWA on server SERVER7[00:31:11] Finding OWA install path on the filesystem[00:31:11] Updating OWA to version 8.0.744.0[00:31:11] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.0.744.0'[00:31:20] Getting all Exchange 2007 OWA virtual directories[00:31:21] Found 1 OWA virtual directories.[00:31:21] Updating OWA virtual directories[00:31:21] Processing virtual directory with metabase path 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa'.[00:31:21] Creating metabase entry IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.744.0.[00:31:21] Configuring metabase entry 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.744.0'.[00:31:21] Saving changes to 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.744.0'[00:31:21] Saving changes to 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa'[18:14:09] ***********************************************[18:14:09] * UpdateOwa.ps1: 26.10.2007 18:14:09[18:14:16] Updating OWA on server SERVER7[18:14:16] Finding OWA install path on the filesystem[18:14:16] Updating OWA to version 8.0.752.0[18:14:16] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.0.752.0'[18:14:21] Getting all Exchange 2007 OWA virtual directories[18:14:23] Found 1 OWA virtual directories.[18:14:23] Updating OWA virtual directories[18:14:23] Processing virtual directory with metabase path 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa'.[18:14:23] Creating metabase entry IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.752.0.[18:14:23] Configuring metabase entry 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.752.0'.[18:14:23] Saving changes to 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa/8.0.752.0'[18:14:23] Saving changes to 'IIS://server7.mediothek.local/W3SVC/1/ROOT/owa'[04:00:48] ***********************************************[04:00:48] * UpdateOwa.ps1: 07.03.2008 04:00:48[04:00:54] CAS role is not installed on server SERVER7

Same Problem. No errors in Log, but OWA didnt work.

Yeah What is up with the Exchange dev team, crappy QA and an obvious rushed to market product. I'm not to sure I want to deploy such a buggy product. Exchange 2003 was rock solid.

Same thing has happened to me on every Rollup update since I installed Exchange 2007. (3rd time for us, now) All of our Exchange 2007 roles are on a single machine. (no Edge server role, though) The problem lies around the fact that each successive rollup creates a new folder in the C:\Program Files\Microsoft\Exchange Server\ClientAccess\OWA folder, with a numerical designation like 8.0.783.2. Then, the scripts and themes folders within these aren't populated with anyfiles. The owa virtual web server is reconfigured to usethis new directory for the scripts and they aren't there. I usually just manually copy the scripts and themes into these folders and restart OWA, but this time the IISOWA app pool isn't updating with the new entry. (There's an entry for each of these numerical folders in the OWA app pool...) Rick

Try creating a new user accoutn with correct permissions and do the rollup, mine turned out to be a corrupt user account profile in Documents and Settings. Only thing it was effecting was Rollup and abaility to use Exchnage Management tools. Seems liek MS needs to do better QA work, I am very dissapointed with quailty of 2007.

Mein Lsung am Win 2003 R2 mit Exchange 2007 SP1 war: 1. Einen anderen Administrator erstellen (zum Beispiel SUBAD) und alle Rechte geben, in die Gruppen einloggen etc.. 2. Als SUBAD einloggen 3. In der Festplatte die in das Dokumente und Einstellungen Ordner. Rechtsklick auf den Administrator. 4. Nimm dem Administrator alle Rechte an seinem eigenen Ordner, bernimm als SUBAD die Besitzrechte des Administrator Ordners. 5. Neustarten des Systems 4. Wieder als SUBAD einloggen. 6. Den Ordner Administrator.domne so behandeln wie Nummer 3 und 4 7. Lsche den Ordner Administrator 8. Reboot 9. Als SUBAD einloggen und den Administratir.Domne Ordner lschen 10. Abmelden und als Administrator einloggen 11. Den SUBAD lsschen Danach geht mein Exchange Verwaltungstool wieder, Dann Das Rollup 1 Deinstallieren. Reboot Danach als Administrator direkt am Pc nicht ber Remotedesktop das Rollup erneut installieren. (Habe die neue Version vom 6.3.2008 nochmal runtergeladen) Danach geht auch das OWA wieder. Gru