owa 2003 corrupted by KB888619?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Morten R. Rasmussen - 22 Sep 2005 00:16 GMT

English Exchange 2003 / SBS 2003 .

After installing an Exchange 2003 update, KB888619, the OWA has stopped
functioning.
http://support.microsoft.com/default.aspx?scid=kb;en-us;888619

Login dialog is shown correct, but after logging in, you are presented with
the following html:

==================================



<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=en-us,da;q=0.5">
<TITLE>Microsoft Outlook Web Access</TITLE>
<BASE href="https://servername/exchange/username/">
</HEAD>
<SCRIPT language="JavaScript">
var g_iNewWindowWidth = 700;
var g_iNewWindowHeight = 500;
var g_fWarnOnLogOff=true;
function WarnOnLogOff()
{
if (g_fWarnOnLogOff)
alert("To help protect your mailbox from unauthorized access, close all
browser windows when you finish using Outlook Web Access.");
}
</SCRIPT>
<OPTION id="splChsOpt" value="">(Select a Language)</OPTION><OPTION
value="ar">Arabic</OPTION><OPTION value="da">Danish</OPTION><OPTION
value="nl">Dutch</OPTION><OPTION value="en-au">English
(Australia)</OPTION><OPTION value="en-ca">English (Canada)</OPTION><OPTION
selected value="en-gb">English (United Kingdom)</OPTION><OPTION
value="en-us">English (United States)</OPTION><OPTION
value="fi">Finnish</OPTION><OPTION value="fr">French</OPTION><OPTION
value="de-p">German (post-reform)</OPTION><OPTION value="de-a">German
(pre-reform)</OPTION><OPTION value="he">Hebrew</OPTION><OPTION
value="it">Italian</OPTION><OPTION value="ko">Korean</OPTION><OPTION
value="nb">Norwegian (Bokmål)</OPTION><OPTION value="no">Norwegian
(Nynorsk)</OPTION><OPTION value="es">Spanish</OPTION><OPTION
value="sw">Swedish</OPTION>
<NOFRAMES>
<BODY><P>This page uses frames, but your browser doesn't support
them.</P></BODY>
</NOFRAMES>
</FRAMESET>
</HTML>

===================
Attempts to access user-folders directly gives the same html.
Apparently OWA worked fine before update, but this is hearsay.

Any ideas?

Best regards
Morten Rasmussen

Reply to this Message

Morten R. Rasmussen - 22 Sep 2005 13:10 GMT

KB888619 has been uninstalled, and everything is working again.

A reinstall returned the error.

> English Exchange 2003 / SBS 2003 .
>
[quoted text clipped - 56 lines]
> Best regards
> Morten Rasmussen

Reply to this Message

Scott Roberts [MSFT] - 22 Sep 2005 18:19 GMT

I almost missed the SBS scenario that you outlined.

My guess is that a reboot needed to happen *or* anything else could have
happened :) There is a log in the %SystemRoot% called KB88619 that should
help diagnose what happened.

Scott

> KB888619 has been uninstalled, and everything is working again.
>
[quoted text clipped - 61 lines]
>> Best regards
>> Morten Rasmussen

Reply to this Message

Morten R. Rasmussen - 22 Sep 2005 21:20 GMT

The server was restarted after installation, but it looks like it didn't
install a couple of files during the restart.

Excerpt from the log:
144.687: Source:C:\Program Files\Exchsrvr\bin\SETEA7.tmp (6.5.7233.28)
144.687: Destination:C:\Program Files\Exchsrvr\bin\exoledb.dll (6.5.7226.0)
144.687: Source:C:\Program Files\Exchsrvr\bin\SETEA8.tmp (6.5.7233.28)
144.687: Destination:C:\Program Files\Exchsrvr\bin\davex.dll (6.5.7226.1)

the two .tmp files were present on the daily backup, so something didn't
work after reboot.

Thanks

I may try again at some point.

- Morten

>I almost missed the SBS scenario that you outlined.
>
[quoted text clipped - 69 lines]
>>> Best regards
>>> Morten Rasmussen

Reply to this Message

Scott Roberts [MSFT] - 22 Sep 2005 22:30 GMT

Thanks.

The below output means that the installer detected that these files were in
use at this moment. This isn't fatal because the installer will finish and
alert the installer that a reboot is required to fully complete the
installation. On the reboot, the files listed below will be replaced and
everything should work.

*Issues* happen if the reboot does not happen because then you have the old
files for exoledb.dll and davex trying to work with the newer files that
make up the rest of the package. This scenario happens every once in awhile
when Inetinfo when the installer tries to stop the service. Inetinfo then
tries to restart itself (or trying to dump the crash to Watson) at the same
time that the installer thought it was already shut down. File in use
scenario.

> The server was restarted after installation, but it looks like it didn't
> install a couple of files during the restart.
[quoted text clipped - 88 lines]
>>>> Best regards
>>>> Morten Rasmussen

Reply to this Message

Morten R. Rasmussen - 24 Sep 2005 01:48 GMT

As I stated, the server WAS restarted after installation.
Upon finishing the install, it asked to reboot, and I let it.

> Thanks.
>
[quoted text clipped - 104 lines]
>>>>> Best regards
>>>>> Morten Rasmussen

Reply to this Message