OWA 2007 Quit Working after SP3 #CU14 installation

Posted on 2014-12-07
Medium Priority
Last Modified: 2014-12-27
Just installed Exchange 2007 SP3 CU#14 and OWA quit working. It doesn't work at the server, from a workstation within the local network or outside the network. when I enter:

https://mail.<domain>.com.owa I get: https://mail.<domain>.com/owa/auth/logon.aspx?url=https://mail.<domain>.com/owa/%3Fae=Folder%26t=IPF.Note%26id=LgAAAADxK4Ljl%252bqJS4SzoYlmmxCxAQAbf8M3kUhZSIK7yPsGBoJdAABEr8XzAAAB%26slUsng=0%26pg=1&reason=0

That's it. No logon screen or nothing.

I'm attempting to uninstall CU14 to see if that restores the OWA functionality.
Question by:abustraan
  • 7
  • 3

Expert Comment

ID: 40485285
Shouldn't you be entering /owa and not .owa? Also, can you use https://your_cas_server/owa and get a logon page? What steps have you taken so far so we don't repeat ourselves?

Author Comment

ID: 40485289
Sorry for the mistype yes I am entering https://mail.<domain>.com/owa.

I've tried https://<server>/owa
I've tried https://<serverip>/owa
I've tried https://<server.domain.local>/owa
I've tried https://<server.domain.com>/owa

Just finished uninstalling CU14 and OWA is functioning.

Author Comment

ID: 40485291
Here's Update OWA log from the installation of CU#14

[02:38:32] ***********************************************
[02:38:32] * UpdateOwa.ps1: 12/7/2014 2:38:32 AM
[02:38:34] Updating OWA on server <Server>
[02:38:34] Finding OWA install path on the filesystem
[02:38:34] Updating OWA to version 8.3.379.2
[02:38:34] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.3.379.2'
[02:38:35] Getting all Exchange 2007 OWA virtual directories
[02:38:35] Found 1 OWA virtual directories.
[02:38:35] Updating OWA virtual directories
[02:38:37] Processing virtual directory with metabase path 'IIS://<Server>.domain.local/W3SVC/1/ROOT/owa'.
[02:38:37] Creating metabase entry IIS://<server>.<domain>.local/W3SVC/1/ROOT/owa/8.3.379.2.
[02:38:37] Configuring metabase entry 'IIS://<server>.<domain>.local/W3SVC/1/ROOT/owa/8.3.379.2'.
[02:38:37] Saving changes to 'IIS://<server>.<domain>.local/W3SVC/1/ROOT/owa/8.3.379.2'
[02:38:37] Saving changes to 'IIS://<server>.<domain>.local/W3SVC/1/ROOT/owa'
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.


Author Comment

ID: 40485294
In searching for a resolution I came across this:


It talks about enabling anonymous access to OWA in IIS and the check box is indeed "unchecked". However, it was unchecked prior to CU#14 and OWA works. Should I enable that, and what would be the downside to that?

Author Comment

ID: 40485357
Grrrrr..... reinstalled CU#14 to try the suggestion about the Anonymous Permission and OWA is working....

Expert Comment

ID: 40485477
Permissions are usually the cause of most IIS error after updates. Usually the OWA and the EWS need to be checked for that. I always do as I find it sometimes gets reset.

Author Comment

ID: 40485489
Thing of it is, I didn't have to change the permissions. The Anonymous check box is still unchecked.

Expert Comment

ID: 40485505
Yeah sometimes though I have even had to check then recheck the authentication types I wasn't using or vice versa to get things where they should have been back in 2007 version. Not as much in 2010, but I do find that it changes some of the permissions I had set back to default whenever I did service pack updates. It is usually pretty easy to troubleshoot the changed permission issue in 2010, 2007 is harder to troubleshoot though since things look right but aren't working. Rollup updates never have caused me any issues with permissions in 2010. So I've been lucky there.

Anyway, glad you got it fixed.

Accepted Solution

abustraan earned 0 total points
ID: 40513799
I resolved my own issue by uninstalling and reinstalling the CU 14 update. Permissions didn't have to be changed.

Author Closing Comment

ID: 40519473
If all else fails, undo recent changes, if possible, and attempt to recreate the problem and determine what actually caused the problem,

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

There are literally thousands of Exchange recovery applications out there. So how do you end up picking one that’s ideal for your business & purpose? By carefully scouting the product’s features, the benefits it offers you, & reading ample reviews f…
Disk errors can be the source of sundry problems for the Exchange server, the most common one being that the database fails to mount.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question