Comments on: Exchange 2007 OWA stops working with “reason=0” error

By: John

John — Fri, 30 Sep 2011 14:12:07 +0000

Just hit this problem last night on a client’s Exchange 2007 server, and found this link right on top in my google search. Was issue 2 and updateowa.ps1 worked great for me. Thanks for this post, even after all this time it’s helping people!

By: Andrea

Andrea — Mon, 30 May 2011 11:51:19 +0000

Thanks Paul. I made some search by Google and i see that the remove of client access role is a dangerous operation. There are some people that had a lot of problem with this procedure.

MyTekki, you had find the problem after the installation of rollup 3v2 for Exchange 2007 Sp3? I have the Exchange 2007 installed on a Windows 2003 Sp2 x64bit platform so i can’t use the powershell commands

I have install the Rollup 3v2 on Exchange 2007 Sp3 and after that i have the external OWA URL blank. Only the client into the domain and the same lan of Exchange server can access to OWA by the internal URL

By: Paul Cunningham

Paul Cunningham — Mon, 30 May 2011 10:56:26 +0000

That KB explains how to uninstall and reinstall IIS on an Exchange server. Part of that process is removing and reinstalling the Client Access role.

MyTekki is describing the process of just removing and reinstalling the Client Access role. When you reinstall it all of the virtual directories are recreated for you, but with the default settings, so you would need to redo your custom configurations (if any).

By: Andrea

Andrea — Mon, 30 May 2011 07:32:28 +0000

But if i uninstall the client access role, which is the effects? I have to recreate all IIS virtual Directory? How can i recreate the virtual directory for Public Folders Exchadmin, Exchange and ExchWeb?

The procedure describe from MyTekki, is similar to this KB?

http://support.microsoft.com/kb/320202/en-us

Andrea

By: Paul Cunningham

Paul Cunningham — Sat, 28 May 2011 10:13:16 +0000

That will remove the Client Access server role from the server.

By: Andrea

Andrea — Sat, 28 May 2011 10:08:08 +0000

Dear MyTekki,

which is the effect of this command?

setup.com /mode:uninstall /role:c

I have OWA blank page after Exchange 2007 Sp3 Rollup 3v2 on a Windows 2003 Sp2 x64. This a producation enviroment so i didn’t made a lot of down time period.

With setup.com /mode:uninstall /role:c i uninstall the entire exchange server?

Best Regards

Andrea

By: John Austin

John Austin — Tue, 24 May 2011 18:17:48 +0000

Thanks, MyTekki. We were plagued by the blank OWA screen with the “reason=0″ error, but neither of the two fixes above applied (tried them anyway, but they didn’t work). Following your instructions to remove/reinstall the CAS worked great.

By: MyTekki

MyTekki — Tue, 19 Apr 2011 16:13:32 +0000

I ran into this with a brand new installation of Server 2008 R2 x64 Enterprise and Exchange 2007 SP3. I did the following steps after 4-5 hours of trouble shooting. Got it working. I have included the commands.

Step 1: open command prompt and cd to the location of the install files

Run the following command (Removes the Client Access Role)
setup.com /mode:uninstall /role:c

Step 2: Reboot the server

Step 3: Install all pre reqs just in case (by script)
Open PowerShell (Run as Admin)

add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy

Step 4: Reboot the server

Step 5: ReInstall the Client Access Role (same direction as Step 1)
setup.com /mode:install /role:c

Step 6: Should be up and working

By: Bas

Bas — Mon, 19 Apr 2010 06:16:47 +0000

Verry usefull! This information saved me hours of work on this issue.

By: Taom

Taom — Sat, 30 Jan 2010 01:48:53 +0000

I’m having the same problem,I am open the Management Shell and run “updateowa.ps1,It’s fine,get flowing text:

Add-PSSnapin : Cannot add Windows PowerShell snap-in Microsoft.Exchange.Managem
ent.PowerShell.Admin because it is already added. Verify the name of the snap-i
n and try again.
At D:\Program Files\Microsoft\Exchange Server\bin\UpdateOwa.ps1:36 char:13
+ add-PSSnapin <<<< -Name Microsoft.Exchange.Management.PowerShell.Admin
[09:41:56] ***********************************************
[09:41:56] * UpdateOwa.ps1: 2010/1/30 上午 09:41:56
[09:41:57] Updating OWA on server LHEXCH07A
[09:41:57] Finding OWA install path on the filesystem
[09:41:57] Updating OWA to version 8.1.340.0
[09:41:57] Copying files from 'D:\Program Files\Microsoft\Exchange Server\Clien
tAccess\owa\Current' to 'D:\Program Files\Microsoft\Exchange Server\ClientAcces
s\owa\8.1.340.0'
[09:41:59] Getting all Exchange 2007 OWA virtual directories
[09:41:59] Found 1 OWA virtual directories.
[09:41:59] Updating OWA virtual directories
[09:41:59] Processing virtual directory with metabase path 'IIS://xxx.xxx.xxx/W3SVC/1/ROOT/owa'.
[09:41:59] Creating metabase entry IIS://xxx.xxx.xxx/W3SVC/1/ROOT/owa/
8.1.340.0.
[09:41:59] Configuring metabase entry 'IIS://xxx.xxx.xxx/W3SVC/1/ROOT/
owa/8.1.340.0'.
[09:41:59] Saving changes to 'IIS://xxx.xxx.xxx/W3SVC/1/ROOT/owa/8.1.3
40.0'
[09:41:59] Saving changes to 'IIS://xxx.xxx.xxx/W3SVC/1/ROOT/owa'