Exchange Rollup, OWA, & Mobile Active Synch - Please Help

[Jennifer Mann]

I installed an Exchange 2007 Rollup today among many other updates from
Microsoft on my exchange server (2003 x64 box). The box required a reboot.
After a reboot, OWA (404 page cannot be displayed) & Active Synch
(0x85010004 - account in exchange does not have permission) connectivity
disappeared.

Per some internet searching, and previous success with this... I removed the
OWA virtual directory (Remove-OWAVirtualDirectory) and attempted to recreate
it (New-OWAVirtualDirectory). I get the following message:

New-OWAVirtualDirectory: An error occurred while creating the IIS virtual
directory 'IIS://TPA-EXCHANGE.nuairmfg.nuair1.com/W3SVC/1/ROOT/owa' on
'TPA-EXCHANGE'.
At line:1 char:24
+ New-OWAVirtualDirectory <<<< -Name OWA

It does not matter if I specify OWA Version, Domain Controller, etc. I get
the same error message.

Any ideas? At this point I do not have any web or active synch connectivity
for my sales staff... :-(

Thanks!

[Bharat Suneja [MVP]]

Anything in the Application Event Log?

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
------------------------------

"Jennifer Mann" <jenn...@nuair.com> wrote in message
news:518D3D8F-2D93-490B...@microsoft.com...

[Jennifer Mann]

No, unfortunately nothing useful in the Application event log.

Rollup 3 (KB ID 935999) was installed. Here's what it logged in
ServiceControl.log from the update:

Unable to restore service 'MSExchangeADTopology'
Unable to restore all services for 'ClientAccess'

I'm sure this is related to my issue, but I'm unsure how to correct.

"Bharat Suneja [MVP]" <bha...@nospam.org> wrote in message
news:%23U92SXU...@TK2MSFTNGP04.phx.gbl...

[Oliver Moazzezi [MVP]]

Jennifer,

The actual kb article shows there are apparent issues installing this in
certain circumstances. Read here: http://support.microsoft.com/kb/935999

I would check to see if you did infact recieved the MSIinstaller errors and
then follow the article for resolution.

Oliver

[Jennifer Mann]

It was performed as a silent install... through WSUS.

The application log has this for MsiInstaller relating to Exchange (no
failures or errors):
-EventID 1025 & 1005 - The windows installer initiaed a system restart to
complete or continue the configuration of Microsoft Exchange Server.
-EventID 11728 - Product: Microsoft Exchange Server - Configuration
Completed Successfully.
-EventID 1022 - Product: Microsoft Exchange Server - Update 'Update Rollup 3
for Exchange Server 2007 (KB935999) 8.0.730.1' installed successfully.

All of my services in the msc were set back to either auto or manual and
were started as they should have been before the rollup was installed, by
the install of the update.

It's getting rather frustrating. Everything logged is success, except in the
SystemControl.log where it stated Unable to restore service
'MSExchangeADTopology' & Unable to restore all services for 'ClientAccess'.

WSUS even says the system was updated successfully.

As always, your help is greatly appreciated... any other ideas to try?

[Oliver Moazzezi [MVP]]

I would follow the kb to rollback the change, test to see if OWA/EAS then
works, and then manually apply the patch again.

Oliver

[Jennifer Mann]

"Patch Removal was disallowed by policy"... any ideas?

[Jennifer Mann]

Duh... Group Policy setting... it's uninstalling... the rollup 3 of exchange
now.

[Jennifer Mann]

Ok, the rollup has been removed and reinstalled all a success... everything
same as before. This time, on the reinstall, I downloaded it from Microsoft
and did it myself. No unattended and no errors.

I'm still at the same point. I cannot recreate my owa virtual directory to
get owa or active synch to work.

New-OWAVirtualDirectory: An error occurred while creating the IIS virtual
directory 'IIS://TPA-EXCHANGE.nuairmfg.nuair1.com/W3SVC/1/ROOT/owa' on
'TPA-EXCHANGE'.
At line:1 char:24
+ New-OWAVirtualDirectory <<<< -Name OWA

Any other suggestions?

[Jennifer Mann]

Ok guys... I worked with microsoft on this to get it resolved. I had to
uninstall and reinstall the CAS. One trick... when trying to remove the CAS
(through add/remove which is the recommended way... not through cmd) it gave
me an error message telling me that a policy restricted which DC I could use
and that I had to use the /domaincontroller switch. I had to remove
HKLM/System/CurrentControlSet/Services/MSExchange ADAccess/Instance0 (use at
own risk!) to get the CAS to remove. After removal, reinstalled the CAS and
everything is working beautifully again.