Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

OWA broken after SP1 Update Rollup 2

30 views
Skip to first unread message

Dressel@discussions.microsoft.com Tim Dressel

unread,
May 14, 2008, 10:54:02 AM5/14/08
to
Hi folks,

I installed update rollup 2 on my Exchange 2007 Sp1 install that already had
Update rollup 1 installed. The base OS is Windows Server 2003 Standard 64bit
running on a 4 processor proliant with 4GB ram.

After the reboot, several services did not start because they were set to
disabled. I set them all back to automatic, rebooted again, and all seems
fine. However, OWA is not working properly. Using Internet Explorer and
pointing to https://myserver/owa it redirects to the following URL:

https://myserver/owa/auth/logon.aspx?url=https://myserver/owa&reason=0

And coughs up a script error on Line 7 Character 1 with the error being
"Syntax error" Code: 0 (that's a zero). I've tried clearing browser cache,
and tried a few other computers here, they all give the same result.

If I use Firefox, I get a wierdo text only logon screen which works, and I
am dumped into the standard "light" client. Everything appears to work as
specified.

Any thoughts on how to fix my OWA?

Thanks in advance,

Tim

Tim Dressel

unread,
May 14, 2008, 11:25:01 AM5/14/08
to
Hi folks,

Google was my friend. Found someone else having the exact same problem.
Issue was resolved by adding back the checkmark in the OWA directory security
for the anonymous access.

Can someone please confirm for me that this is OK?

Thanks in advance...

Tim

Rich Matheisen [MVP]

unread,
May 14, 2008, 9:24:48 PM5/14/08
to
Tim Dressel <TimDr...@discussions.microsoft.com> wrote:

>Google was my friend. Found someone else having the exact same problem.
>Issue was resolved by adding back the checkmark in the OWA directory security
>for the anonymous access.
>
>Can someone please confirm for me that this is OK?

Ummm . . . no, it's not. At least it's not unless you plan on
allowing unauthenticated users to access OWA.

What form of authentication are you allowing on the OWA virtual
directory?

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.p...@getronics.com
Or to these, either: mailto:h.p...@pinkroccade.com mailto:melvin.mcp...@getronics.com mailto:melvin.mcp...@pinkroccade.com

Cary Shultz

unread,
May 19, 2008, 6:47:28 AM5/19/08
to
Tim,

Did you install the update package with "local" credentials (read: local
account to that computer, not a domain user account)? I betcha that you
did. If that is the case, uninstall the update and then reinstall with
domain account.

Also, if you look at the directory structure (c:\program
files\microsoft\exchange server\client access\owa\) and then look for the
"numbered directories" (for example, 8.1.240.5) you will see that the
internal directory structure is indeed there and correct but that those
directories are empty. You will see the same thing in IIS.

HTH,

Cary

"Tim Dressel" <Tim Dre...@discussions.microsoft.com> wrote in message
news:BCBAED93-3E63-4930...@microsoft.com...

Weinie

unread,
May 20, 2008, 9:35:01 AM5/20/08
to

I am having the exact same problem Tim discribes. I accepted the rollup
update from Automatic Updates, using a domain account btw, then rebooted.

Excahnge was totially down when I logged in because every service associated
with Exchange or IIS was set to Disabled. Every one. I set them all to
Automatic and started them all. This brough Excahnge back online, and email
flow seems to be happening.

However, OWA now does not work. When you try to access it you get a blank
page with this URL ...

https://mail.xxxxxxxxxxxxxxx.com/owa/auth/logon.aspx?url=https://mail.xxxxxxxxxxxxx.com/owa&reason=0


No login box, nothing.

What should I look for? If this is what happens on installing the rollup,
I'm really scared to uninstall it.

Joe


--
Joe

Weinie

unread,
May 20, 2008, 10:08:03 AM5/20/08
to

Ok, got it fixed.

In reading thorough everything again I ran across a reference to the
services being "disabled". Seems if "a file" is locked, somewhere, that the
install will fail on that portion and cause the services to be disabled.
Heven forbid that the install would tell you that it encountered a locked
file and could not continue.

We run GFI Mail Essentials for SPAM. On a hunch, I turned off all services
for this application, reapplied SP1 Rollup 2 again, and now OWA seems to be
working

Was it GFI? I don't know, but if anyone else runs into this problem, try
stopping those services and reapply the Rollup.

Joe

--
Joe

Library Sysadmin

unread,
Jul 5, 2008, 1:55:00 PM7/5/08
to
So, OWA failing after a rollup install is STILL an issue???
I'm working on scheduled updates right now and checking to see if it is
finally safe to install an Exchange 2007 rollup or service pack. Apparently
not.

I've had trouble with OWA after every single rollup install and have not
installed an update rollup since 5 because I couldn't get OWA working again
afterwards. Many of our users use it exclusively and it can't be down.

I'm amazed that no one has fixed this issue for over a year now.
Guess I still sit on rollup 5 and check in 3 months to see if anyone will
finally tackle this problem and fix it.

Rick

Andy David {MVP}

unread,
Jul 5, 2008, 2:56:05 PM7/5/08
to
On Sat, 5 Jul 2008 10:55:00 -0700, Library Sysadmin
<Library...@discussions.microsoft.com> wrote:

>So, OWA failing after a rollup install is STILL an issue???
>I'm working on scheduled updates right now and checking to see if it is
>finally safe to install an Exchange 2007 rollup or service pack. Apparently
>not.
>
>I've had trouble with OWA after every single rollup install and have not
>installed an update rollup since 5 because I couldn't get OWA working again
>afterwards. Many of our users use it exclusively and it can't be down.
>
>I'm amazed that no one has fixed this issue for over a year now.
>Guess I still sit on rollup 5 and check in 3 months to see if anyone will
>finally tackle this problem and fix it.

Havent had any issues with rollups. I would suggest calling Microsoft
support.

0 new messages