Exchange Update - KB894689, fails

Hi,

SBS 2000, up to date bar the Subj KB (Exchange 2000 SP whatever (3 I
think)).

I installed via Microsoft Update initially. The Exchange update failed
w' the following message:

store.exe EntryPoint Not Found

The procedure entry point FSetCallTracingCallbacks could not be located
in the dynamic link library EXOSAL.DLL

I used stopped IIS Admin and then removed the KB via Add/Remove
Programs. Rebooted. Downloaded the update manually. Stopped IIS Admin
and Exchange System Attendant. Re-applied the update. No error message
this time until I rebooted, whereupon I got the same error.

I have removed the update now - and all is well - bar I don't have the
Exchange critical update installed - which is of some concern.

This is all on my testbed machine. I feel hesitant now to update client
server machines with this update.

Can anyone help?

--
Duncan

Merv
Tue Jan 10 21:40:37 CST 2006

Best guess Duncan...

Maybe confirm that you have installed Microsoft Exchange 2000 Server Pack 3
with Exchange 2000 Post-Service Pack 3 Update Rollup of August 2004 per:

Microsoft Security Bulletin MS06-003
http://www.microsoft.com/technet/security/bulletin/ms06-003.mspx

For SP info: Start | Programs | Microsoft Exchange | System Manager |
Servers | right click <yourservername> |

Version 6.0 Build 6603.1: Service Pack 3

If the Service Pack is 3 but the build is lower than 6603.1, uninstall
KB894689. Then download and install:

Update Rollup for Exchange 2000 (KB870540)
http://www.microsoft.com/downloads/details.aspx?amp;amp;amp;amp;displaylang=en&familyid=363A57A4-8BED-4BBB-BBE4-ABC11AB04611&displaylang=en

This is the latest rollup for Exchange 2000 SP3. Then reapply KB894689.

I believe that KB894689 requires this latest rollup. You can see from
KB870540 that Exosal.dll is updated in the rollup and this may be affecting
the correct install of KB894689:

Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3
Update Rollup
http://support.microsoft.com/kb/870540/

Update rollup file information
.
.
12-Jun-2004 5:20:24 6.0.6603.0 81,920 Exosal.dll
.


--
Merv Porter [SBS MVP]
===================================
"Duncan McC" <hard@work.ok> wrote in message
news:MPG.1e2f37db60e54ab89897e0@news.microsoft.com...
> Hi,
>
> SBS 2000, up to date bar the Subj KB (Exchange 2000 SP whatever (3 I
> think)).
>
> I installed via Microsoft Update initially. The Exchange update failed
> w' the following message:
>
> store.exe EntryPoint Not Found
>
> The procedure entry point FSetCallTracingCallbacks could not be located
> in the dynamic link library EXOSAL.DLL
>
> I used stopped IIS Admin and then removed the KB via Add/Remove
> Programs. Rebooted. Downloaded the update manually. Stopped IIS Admin
> and Exchange System Attendant. Re-applied the update. No error message
> this time until I rebooted, whereupon I got the same error.
>
> I have removed the update now - and all is well - bar I don't have the
> Exchange critical update installed - which is of some concern.
>
> This is all on my testbed machine. I feel hesitant now to update client
> server machines with this update.
>
> Can anyone help?
>
> --
> Duncan

Duncan
Wed Jan 11 16:58:41 CST 2006

In article <eTCnLDmFGHA.1396@TK2MSFTNGP11.phx.gbl>,
mwport@no_spam_hotmail.com says...
> Best guess Duncan...
>
> Maybe confirm that you have installed Microsoft Exchange 2000 Server Pack 3
> with Exchange 2000 Post-Service Pack 3 Update Rollup of August 2004 per:
>
> Microsoft Security Bulletin MS06-003
> http://www.microsoft.com/technet/security/bulletin/ms06-003.mspx
>
> For SP info: Start | Programs | Microsoft Exchange | System Manager |
> Servers | right click <yourservername> |
>
> Version 6.0 Build 6603.1: Service Pack 3
>
> If the Service Pack is 3 but the build is lower than 6603.1, uninstall
> KB894689. Then download and install:
>
> Update Rollup for Exchange 2000 (KB870540)
> http://www.microsoft.com/downloads/details.aspx?amp;amp;amp;amp;displaylang=en&familyid=363A57A4-8BED-4BBB-BBE4-ABC11AB04611&displaylang=en
>
> This is the latest rollup for Exchange 2000 SP3. Then reapply KB894689.
>
> I believe that KB894689 requires this latest rollup. You can see from
> KB870540 that Exosal.dll is updated in the rollup and this may be affecting
> the correct install of KB894689:
>
> Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3
> Update Rollup
> http://support.microsoft.com/kb/870540/
>
> Update rollup file information
> .
> .
> 12-Jun-2004 5:20:24 6.0.6603.0 81,920 Exosal.dll

Thanks muchly Merv. Any shot is appreciated. 'tis strange though:

In Ex Sys Manager, the Server Version shows:
Version 6.0 (Build 6249.4: Service Pack 3)

In Add/Remove Programs though, Update Rollup for Exchange 2000
(KB870540) is listed (as installed).

KB892986, KB894549 and KB906780 are also all visible in A/R programs.

So I'm still not sure how I should proceed.

--
Duncan

Duncan
Wed Jan 11 17:01:02 CST 2006

In article <eTCnLDmFGHA.1396@TK2MSFTNGP11.phx.gbl>,
mwport@no_spam_hotmail.com says...
> Best guess Duncan...
>
> Maybe confirm that you have installed Microsoft Exchange 2000 Server Pack 3
> with Exchange 2000 Post-Service Pack 3 Update Rollup of August 2004 per:
>
> Microsoft Security Bulletin MS06-003
> http://www.microsoft.com/technet/security/bulletin/ms06-003.mspx
>
> For SP info: Start | Programs | Microsoft Exchange | System Manager |
> Servers | right click <yourservername> |
>
> Version 6.0 Build 6603.1: Service Pack 3
>
> If the Service Pack is 3 but the build is lower than 6603.1, uninstall
> KB894689. Then download and install:
>
> Update Rollup for Exchange 2000 (KB870540)
> http://www.microsoft.com/downloads/details.aspx?amp;amp;amp;amp;displaylang=en&familyid=363A57A4-8BED-4BBB-BBE4-ABC11AB04611&displaylang=en
>
> This is the latest rollup for Exchange 2000 SP3. Then reapply KB894689.
>
> I believe that KB894689 requires this latest rollup. You can see from
> KB870540 that Exosal.dll is updated in the rollup and this may be affecting
> the correct install of KB894689:
>
> Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3
> Update Rollup
> http://support.microsoft.com/kb/870540/
>
> Update rollup file information
> .
> .
> 12-Jun-2004 5:20:24 6.0.6603.0 81,920 Exosal.dll

Further... Exosal is the SP3 version by the looks, dated 2002.

Perhaps I should redo the Update Rollup for Exchange ?

--
Duncan

Merv
Wed Jan 11 17:24:42 CST 2006

Yes, reinstalling the latest Rollup is what I'd try. Then look at your
Exchange server info and see if the Build number increases to 6603.1.

--
Merv Porter [SBS MVP]
===================================
"Duncan McC" <hard@work.ok> wrote in message
news:MPG.1e3055586aee0dec9897e2@news.microsoft.com...
> In article <eTCnLDmFGHA.1396@TK2MSFTNGP11.phx.gbl>,
> mwport@no_spam_hotmail.com says...
>> Best guess Duncan...
>>
>> Maybe confirm that you have installed Microsoft Exchange 2000 Server Pack
>> 3
>> with Exchange 2000 Post-Service Pack 3 Update Rollup of August 2004 per:
>>
>> Microsoft Security Bulletin MS06-003
>> http://www.microsoft.com/technet/security/bulletin/ms06-003.mspx
>>
>> For SP info: Start | Programs | Microsoft Exchange | System Manager |
>> Servers | right click <yourservername> |
>>
>> Version 6.0 Build 6603.1: Service Pack 3
>>
>> If the Service Pack is 3 but the build is lower than 6603.1, uninstall
>> KB894689. Then download and install:
>>
>> Update Rollup for Exchange 2000 (KB870540)
>> http://www.microsoft.com/downloads/details.aspx?amp;amp;amp;amp;displaylang=en&familyid=363A57A4-8BED-4BBB-BBE4-ABC11AB04611&displaylang=en
>>
>> This is the latest rollup for Exchange 2000 SP3. Then reapply KB894689.
>>
>> I believe that KB894689 requires this latest rollup. You can see from
>> KB870540 that Exosal.dll is updated in the rollup and this may be
>> affecting
>> the correct install of KB894689:
>>
>> Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3
>> Update Rollup
>> http://support.microsoft.com/kb/870540/
>>
>> Update rollup file information
>> .
>> .
>> 12-Jun-2004 5:20:24 6.0.6603.0 81,920 Exosal.dll
>
> Further... Exosal is the SP3 version by the looks, dated 2002.
>
> Perhaps I should redo the Update Rollup for Exchange ?
>
> --
> Duncan

Duncan
Thu Jan 12 22:44:18 CST 2006

In article <u9gJ1YwFGHA.312@TK2MSFTNGP09.phx.gbl>,
mwport@no_spam_hotmail.com says...
> Yes, reinstalling the latest Rollup is what I'd try. Then look at your
> Exchange server info and see if the Build number increases to 6603.1.

Still 6249.4

However, the re-addition of the Rollup fixed the datetime stamp on the
exosal.dll file. And the KB worked fine.

--
Duncan

Merv
Thu Jan 12 22:51:50 CST 2006

Hmmm... not sure why the Build didn't increase to 6603.1 (but then I really
haven't looked into this before). I'm glad that applying the latest Rollup
worked though.

--
Merv Porter [SBS MVP]
===================================

"Duncan McC" <hard@work.ok> wrote in message
news:MPG.1e31f74acffc82bc9897e4@news.microsoft.com...
> In article <u9gJ1YwFGHA.312@TK2MSFTNGP09.phx.gbl>,
> mwport@no_spam_hotmail.com says...
>> Yes, reinstalling the latest Rollup is what I'd try. Then look at your
>> Exchange server info and see if the Build number increases to 6603.1.
>
> Still 6249.4
>
> However, the re-addition of the Rollup fixed the datetime stamp on the
> exosal.dll file. And the KB worked fine.
>
> --
> Duncan