thanks for your prompt reply. but in this case it's obviously nothing to do
with
1. Wups2.dll
2. agent.
Pls take several minutes to read the log that autoupdate wrote.
MSP Error List:
2008-07-23 22:24:12:953 2540 b08 Handler 1: 1327 2: E:\
2008-07-23 22:24:12:953 2540 b08 Handler : MSI transaction completed. MSI:
0x80070643, Handler: 0x8024200b, Source: No, Reboot: 0
2008-07-23 22:24:12:953 2540 b08 Handler : WARNING: First failure for
update {3BFC3924-FF81-4907-994D-CF5B2A71ADB1}, transaction error =
0x8024200b, MSI result = 0x80070643, MSI action = SetLocalCacheFolder
the case was caused by the stupid update package that trys to locate
msocache folder by calling such MSI action - SetLocalCacheFolder . when it
found the folder wasn't there, the installation failed directly.
if having time, you can reproduce this problem on your machine, pls download
this update package and change your drive letter on which MSOCache\ locates,
and then run the update.
==========================================
"Shenan Stanley" wrote:
> Jazz wrote:
> > after i installed winxp sp3, i could never get any update
> > successfully installed.
> > yesterday, i eventually decided to reinstall a whole brandnew
> > WindowsXp. everything looked ok until i applied the update for
> > Microsoft Office Publisher 2003 (KB950213). It always failed
> > silently without any message window telling me what happened.
> >
> > fortunately I found the update process would write sth to a log
> > file: \windows\windowsupdate.log. from there i get some useful
> > information:
> <snipped>
> >
> > Note there were lines containing 'error' or 'warning'.
> >
> > then i separately downloaded the update package from microsoft
> > again. started it up manually from explorer (double click the
> > package file in the download folder), i saw a message window jumped
> > out and reported "invalid E:\" , after click ok, the installation
> > failed and exited.
> >
> > I recalled that I ever changed my drive letter from E: to D: before
> > doing this update and MSOCache directory located on that drive. so
> > i tried to change it back to E:. after this change, the package got
> > successfully installed.
> >
> > conclusion:
> > 1. the security update from microsoft needs to be more improved.
> > 2. auto-update will hide everything. if you can update
> > successfully, check windowsupdate.log under your windows directory
> > for any possible 'error' or 'warning' and then run the update
> > manually.
> >
> > but not every the bug can be solved by simply changing driver
> > letter..hope you are as lucky as me.
>
> As many will tell you - ignore the title and symptoms listed in the article
> referred to. Do method 1 and 2 and see if it fixes your issue whether or
> not you repaired anything.
>
> http://support.microsoft.com/kb/943144
> Try method 1 and try to update*.
> If fails - try method 2 and try to update*.
>
> *try to update:
> - Visit http://windowsupdate.microsoft.com/
> - If it asks you to install anything before you see a selection of "Custom"
> or "Express" - do so.
> - Once you see the "Custom" or "Express" selection, choose "Custom".
> - Scan for updates.
> - When it lists what it finds - install the critical ones.
> - You are generally safe doing the Optional Software Updates. I suggest
> avoiding the Optional Hardware Updates completely.
>
> Hope that helps - come back and let us know!
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>
Similar Threads
Linear Mode
