Re: Problem with KB890859 update...

"Me" <> wrote in message
news:1113639033.300aba893973e8fa946fb6afed883a29@t eranews
....
> I also checked out the suggestions provided by Torgeir Bakken (MVP) for the 80070003 error,
> http://groups-beta.google.com/group/...ecd61f37f77fe0
> and the links he provided, all to no avail. All suggested registry settings are as they should
> be.

I would say that that link is not the latest thinking about that error code.

Try a search?

http://groups-beta.google.com/group/...bef75189348e78

(Google Groups search for
0x80070003 OR 80070003 author:torgeir group:microsoft.public.windowsupdate
- sorted by date to try to capture current thinking
- first hit
)


BTW I suspect that your second symptom is another indication
of a corrupt download directory.


Good luck

Robert Aldwinckle
---

Robert,
Yes, I Googled for the problem before I tried posting here in microsoft.public.windowsupdate
The link you provided was no help. The problem persists. If I wanted, I could
just copy the files from the update to where they belong, but I'd rather find the cause
of the failure instead. Thanks for posting the link. I appreciate the effort.

On Fri, 22 Apr 2005 03:35:30 -0400, "Robert Aldwinckle" <> wrote:

>"Me" <> wrote in message
>news:1113639033.300aba893973e8fa946fb6afed883a29@ teranews
>...
>> I also checked out the suggestions provided by Torgeir Bakken (MVP) for the 80070003 error,
>> http://groups-beta.google.com/group/...ecd61f37f77fe0
>> and the links he provided, all to no avail. All suggested registry settings are as they should
>> be.
>
>I would say that that link is not the latest thinking about that error code.
>
>Try a search?
>
>http://groups-beta.google.com/group/...bef75189348e78
>
>(Google Groups search for
> 0x80070003 OR 80070003 author:torgeir group:microsoft.public.windowsupdate
>- sorted by date to try to capture current thinking
>- first hit
>)
>
>
>BTW I suspect that your second symptom is another indication
>of a corrupt download directory.
>
>
>Good luck
>
>Robert Aldwinckle
>---
>

"Unk" <> wrote in message
news:
....
> The link you provided was no help.

So, what did you do with it? <eg>

Hint: if you cleared the SoftwareDistribution Download subdirectory,
(etc.) you would probably have a different pattern in your log now...

What do you have in there now since the next failure?
E.g. what does dir/s of the whole SoftwareDistribution directory show?
You can use the datestamp to tell which files and directories have
been used.

Actually I have found that an even better diagnostic is FileMon
filtering on both that directory name and on update (to interleave
the writes to WindowsUpdate.log with the accesses to the directory.
There is so much going on transiently in that directory that after
the fact diagnostics aren't very helpful. They're better than none
but they certainly don't give you the whole story.


HTH

Robert
---

On Sat, 23 Apr 2005 19:33:02 -0400, "Robert Aldwinckle" <> wrote:

>"Unk" <> wrote in message
>news:
>...
>> The link you provided was no help.
>
>So, what did you do with it? <eg>
>
>Hint: if you cleared the SoftwareDistribution Download subdirectory,
>(etc.) you would probably have a different pattern in your log now...
>
>What do you have in there now since the next failure?
>E.g. what does dir/s of the whole SoftwareDistribution directory show?
>You can use the datestamp to tell which files and directories have
>been used.
>
>Actually I have found that an even better diagnostic is FileMon
>filtering on both that directory name and on update (to interleave
>the writes to WindowsUpdate.log with the accesses to the directory.
>There is so much going on transiently in that directory that after
>the fact diagnostics aren't very helpful. They're better than none
>but they certainly don't give you the whole story.
>
>
>HTH
>
>Robert

Robert,
I've already done this, bur here goes again...
If I delete the SoftwareDistribution Download subdirectory contents and let autoupdate do it's
thing, it downloads the file anew, then fails. Here's the log: (Read more after the log)

2005-04-24 01:32:46-0400 2192 90c Trying to make out of proc datastore active
2005-04-24 01:32:46-0400 2192 90c Out of proc datastore is now active
2005-04-24 01:32:49-0400 880 b1c AU Client approved 1 updates for download
2005-04-24 01:32:49-0400 880 b1c Found no updates approved for download matching
criteria 0.
2005-04-24 01:32:49-0400 880 b1c Found no updates approved for download matching
criteria 1.
2005-04-24 01:32:49-0400 880 b1c Found no updates approved for download matching
criteria 2.
2005-04-24 01:32:49-0400 880 b1c Found no updates approved for download matching
criteria 3.
2005-04-24 01:32:49-0400 880 b1c Found no updates approved for download matching
criteria 4.
2005-04-24 01:32:49-0400 880 b1c WU client persisted 1 download calls
2005-04-24 01:32:49-0400 880 b1c WU client succeeds
CClientCallRecorder::BeginDownloadUpdates from AutomaticUpdates with call id
{AF334F06-D8EB-4023-BB29-B1F2F49AA642}
2005-04-24 01:32:49-0400 880 b1c Successfully initiated download for 1 updates
2005-04-24 01:32:49-0400 880 b1c Successfully initiated download for 1 updates
matching criteria 5
2005-04-24 01:32:49-0400 880 380 WU client executing call
{AF334F06-D8EB-4023-BB29-B1F2F49AA642} of type Download Call
2005-04-24 01:32:49-0400 880 380 Dumping out update 1 of 1
2005-04-24 01:32:49-0400 880 380 title = Security Update for Windows XP
(KB890859)
2005-04-24 01:32:49-0400 880 380 dumping updateId
{FAA4E626-ED18-4ACA-B2B3-D9711543C05F}.100 bundling 2 updates
2005-04-24 01:32:49-0400 880 380 bundled update No. 1 is
{F3A6695F-5D25-C87C-BAB4-68D285263F31}.100
2005-04-24 01:32:49-0400 880 380 bundled update No. 2 is
{B1FF52C3-7D37-46A9-B813-8BBDDC74A3D5}.100
2005-04-24 01:33:01-0400 880 380 CheckIfDirExists returned error 0x80070002.
2005-04-24 01:33:02-0400 880 380 CheckIfDirExists returned error 0x80070002.
2005-04-24 01:33:03-0400 880 380 Downloading from
http://au.download.windowsupdate.com...16a8f27ecd.exe
to
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\b2d5bf1528590d957dcebbe21530a5a7\WindowsXP-KB890859-x86-express-ENU.exe
(full file).
2005-04-24 01:33:03-0400 880 5e8 WU client calls back to download call
{AF334F06-D8EB-4023-BB29-B1F2F49AA642} with code Call progress and error 0
2005-04-24 01:33:21-0400 880 9ac Download job for update
{B1FF52C3-7D37-46A9-B813-8BBDDC74A3D5}, revision 100 completed successfully.
2005-04-24 01:33:21-0400 880 9ac Successfully downloaded file from
http://au.download.windowsupdate.com...16a8f27ecd.exe
to
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\b2d5bf1528590d957dcebbe21530a5a7\WindowsXP-KB890859-x86-express-ENU.exe.
2005-04-24 01:33:22-0400 880 380 WU client calls back to download call
{AF334F06-D8EB-4023-BB29-B1F2F49AA642} with code Call progress and error 0
2005-04-24 01:33:23-0400 880 9ac Updateci: WinSEUpdateHandler::_Inventory:
Installer returned 0x2 (2)
2005-04-24 01:33:23-0400 880 9ac DM: GenerateDownloadRequest failed with
0x80070002.
2005-04-24 01:33:23-0400 880 9ac Error 80070002 occurred while downloading
update; notifying dependent calls.
2005-04-24 01:33:23-0400 880 9ac WU client persisted 1 download calls
2005-04-24 01:33:23-0400 880 9ac WU client persisted 1 download calls
2005-04-24 01:33:23-0400 880 380 Update Download failed, error is 80070002
2005-04-24 01:33:23-0400 880 380 Download complete for all calls
2005-04-24 01:33:23-0400 880 380 WU client calls back to download call
{AF334F06-D8EB-4023-BB29-B1F2F49AA642} with code Call complete and error 0
2005-04-24 01:33:23-0400 880 380 WU client completed and deleted call
{AF334F06-D8EB-4023-BB29-B1F2F49AA642}
2005-04-24 01:33:23-0400 880 380 WU client persisted 0 download calls
2005-04-24 01:33:23-0400 880 59c AU received event of 0
2005-04-24 01:33:28-0400 880 380 REPORT EVENT:
{DB96BBB7-E75B-4255-AA55-CFAD1B6E0FFD} 671 2005-04-24 01:33:23-0400 1 161
101 {FAA4E626-ED18-4ACA-B2B3-D9711543C05F} 100 80070002 AutomaticUpdates
Failure Content Download Error: Download failed.
2005-04-24 01:33:28-0400 880 380 REPORT EVENT:
{4AFE5EC8-7AE0-4BC2-94E0-B255155DF9C7} 672 2005-04-24 01:33:23-0400 1 161
101 {B1FF52C3-7D37-46A9-B813-8BBDDC74A3D5} 100 80070002 AutomaticUpdates
Failure Content Download Error: Download failed.

--------------------------------------------------------------------------------------
Now, if I open the C:\WINDOWS\SoftwareDistribution\Download\93c9bb589 8f80e6361e0dc6ea165864f
folder and the run "WindowsXP-KB890859-x86-express-ENU.exe" directly, I get a Setup Error
window that states "The system cannot find the file specified."
If I download the larger "WindowsXP-KB890859-x86-ENU.exe" file from the Windows site and execute
it, I get the exact same error. "The system cannot find the file specified."

Apparently, when I uninstalled KB890859 because it didn't install correctly, it deleted a file
or folder that the update requires to be present. I've checked the uninstall logs from another
WinXP system and I haven't found what it's looking for yet.

Thanks again for responding.

"Unk" <> wrote in message
news:...
> On Sat, 23 Apr 2005 19:33:02 -0400, "Robert Aldwinckle" <> wrote:
....
>>What do you have in there now since the next failure?
>>E.g. what does dir/s of the whole SoftwareDistribution directory show?
>>You can use the datestamp to tell which files and directories have
>>been used.
>>
>>Actually I have found that an even better diagnostic is FileMon
>>filtering on both that directory name and on update (to interleave
>>the writes to WindowsUpdate.log with the accesses to the directory.
>>There is so much going on transiently in that directory that after
>>the fact diagnostics aren't very helpful. They're better than none
>>but they certainly don't give you the whole story.

Did you try getting any of these additional diagnostics I suggested?


> Robert,
> I've already done this, bur here goes again...
> If I delete the SoftwareDistribution Download subdirectory contents and let autoupdate do it's
> thing, it downloads the file anew, then fails. Here's the log: (Read more after the log)

....
> 2005-04-24 01:33:22-0400 880 380 WU client calls back to download call
> {AF334F06-D8EB-4023-BB29-B1F2F49AA642} with code Call progress and error 0
> 2005-04-24 01:33:23-0400 880 9ac Updateci: WinSEUpdateHandler::_Inventory:
> Installer returned 0x2 (2)
> 2005-04-24 01:33:23-0400 880 9ac DM: GenerateDownloadRequest failed with
> 0x80070002.

....
> Now, if I open the C:\WINDOWS\SoftwareDistribution\Download\93c9bb589 8f80e6361e0dc6ea165864f
> folder and the run "WindowsXP-KB890859-x86-express-ENU.exe" directly, I get a Setup Error
> window that states "The system cannot find the file specified."

Look at the last message I have quoted. Do you think that the download phase
worked or not? If not it would not be surprising if an attempt to manually execute
what it did manage to create, failed.

However, let's check for that possibility a bit more precisely.
Try using AU in full prompt mode. E.g. wait for it to tell you
that there are updates available. Select for download (only)
only the one that you are having trouble with. If that works
cleanly you should then be informed that there are downloads
available for installation. Then we will know that the download
phase was successful and the real problem is with the install
phase.


> If I download the larger "WindowsXP-KB890859-x86-ENU.exe" file from the Windows site and execute
> it, I get the exact same error. "The system cannot find the file specified."

Then that could mean that there are two problem symptoms,
perhaps indicating two different problems. In any case one
of them is independent of WU or AU. What clues do you get
from the KB890859.log that your install attempt creates/appends to?


>
> Apparently, when I uninstalled KB890859 because it didn't install correctly, it deleted a file
> or folder that the update requires to be present. I've checked the uninstall logs from another
> WinXP system and I haven't found what it's looking for yet.

Those message codes probably mean something to people who have
knowledge of the internals. We are restricted to doing black-box
reverse engineering. As I mentioned I think that your best diagnostic
will be getting a FileMon log of accesses to SoftwareDistribution
interleaved with the writes done to WindowsUpdate.log. You could
do exactly the same thing to get more information about your install
failure but I suspect that first you can some clues in the install log.


>
> Thanks again for responding.
>


Good luck

Robert
---