OWA 2007 Quit Working after SP3 #CU14 installation

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.
abustraanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tshearonCommented:
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?
0
abustraanAuthor Commented:
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.
0
abustraanAuthor Commented:
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'
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

abustraanAuthor Commented:
In searching for a resolution I came across this:

http://forums.petri.com/showthread.php?t=24576&page=2

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?
0
abustraanAuthor Commented:
Grrrrr..... reinstalled CU#14 to try the suggestion about the Anonymous Permission and OWA is working....
0
tshearonCommented:
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.
0
abustraanAuthor Commented:
Thing of it is, I didn't have to change the permissions. The Anonymous check box is still unchecked.
0
tshearonCommented:
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.
0
abustraanAuthor Commented:
I resolved my own issue by uninstalling and reinstalling the CU 14 update. Permissions didn't have to be changed.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
abustraanAuthor Commented:
If all else fails, undo recent changes, if possible, and attempt to recreate the problem and determine what actually caused the problem,
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.