SBS 2003 R2 Upgrade from Server 2003 Standard leads to 80246002 er

Hello all,

This problem has me stumped. I just upgraded my Standard 2003 to SBS 2003
R2, and its been a nightmare so far. This is the latest in a string of MANY
problems that I feel stem from a failure to register certain DLL's properly.

As far as I know the other problems have been resolved, this is the last
little remnant.

When I go to Windows Update, it finds the 45 updates or so I need to
install. I go to download them, the files are downloaded, but as they are
each being processed they are given the "fail" code prior to actually being
installed (but after being downloaded).

I pull up the windowsupdate.log and it supplies the same error code for all
of the updates past the SBS Upgrade


2008-05-29 20:47:09:404 884 16c8 DnldMgr *********** DnldMgr: New download
job [UpdateId = {705FBEA0-A687-4706-A75D-C65AE364543E}.100] ***********
2008-05-29 20:47:09:419 884 16c8 DnldMgr * BITS job initialized, JobId =
{A3916FBD-40D3-4F58-B4BA-7F9B9AFCF5B8}
2008-05-29 20:47:09:419 884 16c8 DnldMgr * Downloading from
http://www.download.windowsupdate.co...932589866e.exe
to
C:\WINDOWS\SoftwareDistribution\Download\fa7431e5b 6c6ef5b2a4a86419ca21980\9602589c6ae9e584f496000ad8 18c3932589866e (full file).
2008-05-29 20:47:12:591 884 1580 Report REPORT EVENT:
{76AF5FE9-300F-4158-88AF-707B1009A616} 2008-05-29
20:47:07:591-0700 1 161 101 {F02399FB-9130-4097-8202-43DCD4A7C100} 102 80246002 WindowsUpdate Failure Content Download Error: Download failed.
2008-05-29 20:47:12:591 884 1580 Report REPORT EVENT:
{65DA63DC-EB81-422F-BC6A-EE576AD3A6DF} 2008-05-29
20:47:09:419-0700 1 161 101 {EED8DDD8-3E3E-43AE-B87E-E4E543FF099D} 102 80246002 WindowsUpdate Failure Content Download Error: Download failed.
2008-05-29 20:47:41:810 884 174c DnldMgr BITS job
{A3916FBD-40D3-4F58-B4BA-7F9B9AFCF5B8} completed successfully
2008-05-29 20:47:41:857 884 174c DnldMgr WARNING: File failed
postprocessing, error = 80246002
2008-05-29 20:47:41:857 884 174c DnldMgr Failed file: URL =
'http://www.download.windowsupdate.com/msdownload/update/software/uprl/2008/05/windows-kb890830-v1.41_9602589c6ae9e584f496000ad818c3932589866e.exe ',
Local path =
'C:\WINDOWS\SoftwareDistribution\Download\fa7431e5 b6c6ef5b2a4a86419ca21980\9602589c6ae9e584f496000ad 818c3932589866e'
2008-05-29 20:47:41:857 884 174c DnldMgr Error 0x80246002 occurred while
downloading update; notifying dependent calls.


I'm pretty certain the issue is a unregistered or corrupted DLL. I have
searched the forums but most people experiencing this issue are on XP based
workstations. Any info for a SBS based user?

Thanks!

"Hopefully" <Hopefully@discussions.microsoft.com> wrote in message
news:27A47E33-8973-496C-AB9E-3513836974AF@microsoft.com
....

> I'm pretty certain the issue is a unregistered or corrupted DLL. I have
> searched the forums but most people experiencing this issue are on XP based
> workstations. Any info for a SBS based user?


Does that mean that you have been ignoring the advice to try any of the suggestions
in KB943144? Notice that often whenever it is mentioned posters are advised to
"ignore the title"? ; )


Otherwise, I would suspect the download is actually failing,
resulting in corrupted files. E.g. believe this

> 20:47:09:419-0700 1 161 101 {EED8DDD8-3E3E-43AE-B87E-E4E543FF099D} 102 80246002 WindowsUpdate Failure Content Download Error:
> Download failed.

and not this

> 2008-05-29 20:47:41:810 884 174c DnldMgr BITS job
> {A3916FBD-40D3-4F58-B4BA-7F9B9AFCF5B8} completed successfully


If you want to try to diagnose that I would try getting more detail about it
using the verbose logging option. (Ref. KB902093) Since that is extremely
cryptic I would also supplement it with a ProcMon trace.



>
> Thanks!
>


Good luck

Robert Aldwinckle
---

Actually I had already gone through KB943144, I reregistered the wups2.dll
to no avail. Also the Windows Update Agent tells me its already installed
when I try to download it again. So no luck with that one

As far as enabling extended logging, this one I havent tried! Didnt know
there was such a thing. I just enabled it, there is QUITE a bit of
information. As far as the procmon is concerned, just keep procmon running
while I run the Windowsupdate?

Shall I try and distill the information in this log file? It would seem
difficult to post the entire thing..



"Robert Aldwinckle" wrote:

> "Hopefully" <Hopefully@discussions.microsoft.com> wrote in message
> news:27A47E33-8973-496C-AB9E-3513836974AF@microsoft.com
> ....
>
> > I'm pretty certain the issue is a unregistered or corrupted DLL. I have
> > searched the forums but most people experiencing this issue are on XP based
> > workstations. Any info for a SBS based user?
>
>
> Does that mean that you have been ignoring the advice to try any of the suggestions
> in KB943144? Notice that often whenever it is mentioned posters are advised to
> "ignore the title"? ; )
>
>
> Otherwise, I would suspect the download is actually failing,
> resulting in corrupted files. E.g. believe this
>
> > 20:47:09:419-0700 1 161 101 {EED8DDD8-3E3E-43AE-B87E-E4E543FF099D} 102 80246002 WindowsUpdate Failure Content Download Error:
> > Download failed.
>
> and not this
>
> > 2008-05-29 20:47:41:810 884 174c DnldMgr BITS job
> > {A3916FBD-40D3-4F58-B4BA-7F9B9AFCF5B8} completed successfully
>
>
> If you want to try to diagnose that I would try getting more detail about it
> using the verbose logging option. (Ref. KB902093) Since that is extremely
> cryptic I would also supplement it with a ProcMon trace.
>
>
>
> >
> > Thanks!
> >
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>

"Hopefully" <Hopefully@discussions.microsoft.com> wrote in message
news82D61B0-7F9A-4770-9753-D3664EACE9D0@microsoft.com...
>
> Actually I had already gone through KB943144, I reregistered the wups2.dll
> to no avail. Also the Windows Update Agent tells me its already installed
> when I try to download it again. So no luck with that one
>
> As far as enabling extended logging, this one I havent tried! Didnt know
> there was such a thing. I just enabled it, there is QUITE a bit of
> information. As far as the procmon is concerned, just keep procmon running
> while I run the Windowsupdate?
>
> Shall I try and distill the information in this log file? It would seem
> difficult to post the entire thing..


That would be a good idea. The way that I use it is look for the WRITE
records for the WindowsUpdate.log. From there you can infer which
log record it will refer to by its length. E.g. I open the log in Notepad
with Word Wrap off and Status bar on, then tab to the end of a line
to know what its length is. Add 1 to account for the line end character.
So, whatever, precedes that WRITE may have had something to do
with the production of that log message.


One quick thing that may be worth doing is checking out your BITS service
with bitsadmin (from a cmd window):

bitsadmin /util /version /verbose

There's also a repair service option available that way.


Good luck

Robert
---


>
>
>
> "Robert Aldwinckle" wrote:
>
>> "Hopefully" <Hopefully@discussions.microsoft.com> wrote in message
>> news:27A47E33-8973-496C-AB9E-3513836974AF@microsoft.com
>> ....
>>
>> > I'm pretty certain the issue is a unregistered or corrupted DLL. I have
>> > searched the forums but most people experiencing this issue are on XP based
>> > workstations. Any info for a SBS based user?
>>
>>
>> Does that mean that you have been ignoring the advice to try any of the suggestions
>> in KB943144? Notice that often whenever it is mentioned posters are advised to
>> "ignore the title"? ; )
>>
>>
>> Otherwise, I would suspect the download is actually failing,
>> resulting in corrupted files. E.g. believe this
>>
>> > 20:47:09:419-0700 1 161 101 {EED8DDD8-3E3E-43AE-B87E-E4E543FF099D} 102 80246002 WindowsUpdate Failure Content Download Error:
>> > Download failed.
>>
>> and not this
>>
>> > 2008-05-29 20:47:41:810 884 174c DnldMgr BITS job
>> > {A3916FBD-40D3-4F58-B4BA-7F9B9AFCF5B8} completed successfully
>>
>>
>> If you want to try to diagnose that I would try getting more detail about it
>> using the verbose logging option. (Ref. KB902093) Since that is extremely
>> cryptic I would also supplement it with a ProcMon trace.
>>
>>
>>
>> >
>> > Thanks!
>> >
>>
>>
>> Good luck
>>
>> Robert Aldwinckle
>> ---
>>
>>
>>