The website has encountered a problem...Error number: 0x800B0003

I have 3 computers running Windows XP (2 Pro, 1 home) that both have this
problem when I try and go to Microsoft Update. I have used MS update on these
same machines before for almost a year without a problem. At home my Win2K
and Win XP Pro machines updated fine.

Trying all the various regsvr32 fixes found by searching this forum did NOT
fix the problem. All machines have been rebooted, caches cleared, spyware
checks run, etc.

Any ideas?

Softpub.dll, Wintrust.dll, Initpki.dll, Dssenh.dll, Rsaenh.dll, Gpkcsp.dll,
Sccbase.dll, Slbcsp.dll, Mssip32.dll, and Cryptdlg.dll are the files that
should get the treatment according to
http://support.microsoft.com/default...b;en-us;813442

Did you try that?

"Eric Harman" <Eric > wrote in message
news:39C706E4-1858-40DE-B7BF-...
>I have 3 computers running Windows XP (2 Pro, 1 home) that both have this
> problem when I try and go to Microsoft Update. I have used MS update on
> these
> same machines before for almost a year without a problem. At home my Win2K
> and Win XP Pro machines updated fine.
>
> Trying all the various regsvr32 fixes found by searching this forum did
> NOT
> fix the problem. All machines have been rebooted, caches cleared, spyware
> checks run, etc.
>
> Any ideas?

Yes, I had seen an earlier suggestion from someone here to make a batch file
that runs regsvr32 on a total of 20 .dlls. I checked that against the list
you gave me and indeed every 1 of the 10 is there. It didn't do a thing. I
ran it, rebooted, same problem still persists for 3 days now.

Thanks for helping, though.

Eric Harman

"Michael Jennings" wrote:

> Softpub.dll, Wintrust.dll, Initpki.dll, Dssenh.dll, Rsaenh.dll, Gpkcsp.dll,
> Sccbase.dll, Slbcsp.dll, Mssip32.dll, and Cryptdlg.dll are the files that
> should get the treatment according to
> http://support.microsoft.com/default...b;en-us;813442
>
> Did you try that?
>
> "Eric Harman" <Eric > wrote in message
> news:39C706E4-1858-40DE-B7BF-...
> >I have 3 computers running Windows XP (2 Pro, 1 home) that both have this
> > problem when I try and go to Microsoft Update. I have used MS update on
> > these
> > same machines before for almost a year without a problem. At home my Win2K
> > and Win XP Pro machines updated fine.
> >
> > Trying all the various regsvr32 fixes found by searching this forum did
> > NOT
> > fix the problem. All machines have been rebooted, caches cleared, spyware
> > checks run, etc.
> >
> > Any ideas?
>
>
>

Also, here is some info from WindowsUpdate.log when I try and manually go to
the Microsoft Update website with my XP Pro machine:

2005-10-14 14:27:00 3340 cfc COMAPI ----------- COMAPI:
IUpdateServiceManager::AddService -----------
2005-10-14 14:27:00 3340 cfc COMAPI - ServiceId =
{7971f918-a847-4430-9279-4a52d1efe18d}
2005-10-14 14:27:00 3340 cfc COMAPI - AuthorizationCabPath =
C:\WINDOWS\SoftwareDistribution\AuthCabs\muauth.ca b
2005-10-14 14:27:00 4076 fa0 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0700) ===========
2005-10-14 14:27:00 4076 fa0 Misc = Process: C:\WINDOWS\system32\wuauclt.exe
2005-10-14 14:27:00 4076 fa0 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2005-10-14 14:27:00 4076 fa0 DtaStor Update service properties: service
registered with AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
2005-10-14 14:27:00 3340 cfc COMAPI - Added service, URL =
http://update.microsoft.com/microsoftupdate/
2005-10-14 14:27:00 3340 cfc COMAPI ----------- COMAPI:
IUpdateServiceManager::RegisterServiceWithAU -----------
2005-10-14 14:27:00 3340 cfc COMAPI - ServiceId =
{7971f918-a847-4430-9279-4a52d1efe18d}


Here is what I believe happens when AutoUpdates tries in vain to get the
updates:

2005-10-14 13:42:54 1084 260 AU #############
2005-10-14 13:42:54 1084 260 AU ## START ## AU: Search for updates
2005-10-14 13:42:54 1084 260 AU #########
2005-10-14 13:42:54 1084 260 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {4132E9A6-33FF-4180-BBC5-56273F89B5AE}]
2005-10-14 13:42:54 1084 44c Agent *************
2005-10-14 13:42:54 1084 44c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-10-14 13:42:54 1084 44c Agent *********
2005-10-14 13:42:55 1084 44c Setup FATAL: IsUpdateRequired failed with error
0x800b0003
2005-10-14 13:42:55 1084 44c Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed: 0x800b0003
2005-10-14 13:42:55 1084 44c Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed, error = 0x800B0003
2005-10-14 13:42:55 1084 44c Agent * WARNING: Skipping scan, self-update
check returned 0x800B0003
2005-10-14 13:42:56 1084 44c Agent * WARNING: Exit code = 0x800B0003
2005-10-14 13:42:56 1084 44c Agent *********
2005-10-14 13:42:56 1084 44c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-10-14 13:42:56 1084 44c Agent *************
2005-10-14 13:42:56 1084 44c Agent WARNING: WU client failed Searching for
update with error 0x800b0003
2005-10-14 13:42:57 1084 44c AU >>## RESUMED ## AU: Search for updates
[CallId = {4132E9A6-33FF-4180-BBC5-56273F89B5AE}]
2005-10-14 13:42:57 1084 44c AU # WARNING: Search callback failed, result
= 0x800B0003
2005-10-14 13:42:57 1084 44c AU #########
2005-10-14 13:42:57 1084 44c AU ## END ## AU: Search for updates [CallId
= {4132E9A6-33FF-4180-BBC5-56273F89B5AE}]
2005-10-14 13:42:57 1084 44c AU #############
2005-10-14 13:42:57 1084 44c AU AU setting next detection timeout to
2005-10-15 01:42:57

On one of my other machines (XP Home) the messages are a little different,
but still include,
"Error: Agent failed detecting with reason: 0x800b0003.

It also includes "Update is not allowed to download due to regulation." I'm
not exactly sure what "regulation" I'm inviolation of here, these are legal
copies and they've been updating for the last 9-10 months.

Perhaps I do not have a licownze for my menkey? Because Microsoft Update is
beginning to look like some Inspector Clouseau farce.

"Eric Harman" wrote:

> Yes, I had seen an earlier suggestion from someone here to make a batch file
> that runs regsvr32 on a total of 20 .dlls. I checked that against the list
> you gave me and indeed every 1 of the 10 is there. It didn't do a thing. I
> ran it, rebooted, same problem still persists for 3 days now.
>
> Thanks for helping, though.
>
> Eric Harman
>
> "Michael Jennings" wrote:
>
> > Softpub.dll, Wintrust.dll, Initpki.dll, Dssenh.dll, Rsaenh.dll, Gpkcsp.dll,
> > Sccbase.dll, Slbcsp.dll, Mssip32.dll, and Cryptdlg.dll are the files that
> > should get the treatment according to
> > http://support.microsoft.com/default...b;en-us;813442
> >
> > Did you try that?
> >
> > "Eric Harman" <Eric > wrote in message
> > news:39C706E4-1858-40DE-B7BF-...
> > >I have 3 computers running Windows XP (2 Pro, 1 home) that both have this
> > > problem when I try and go to Microsoft Update. I have used MS update on
> > > these
> > > same machines before for almost a year without a problem. At home my Win2K
> > > and Win XP Pro machines updated fine.
> > >
> > > Trying all the various regsvr32 fixes found by searching this forum did
> > > NOT
> > > fix the problem. All machines have been rebooted, caches cleared, spyware
> > > checks run, etc.
> > >
> > > Any ideas?
> >
> >
> >

Maybe there's a newsgroup for MU. I didn't look thoroughly. My
second suggestion is also something you've probably tried, which
is to use Windows Update instead of Microsoft Update.

Microsoft Most Valuable Professionals (MVPs) have not joined
this thread, and I don't think you clicked on the link I gave
you.

If you are willing to tangle with Microsoft support, start here:
http://support.microsoft.com/oas/def...-us&gprid=6527
Unlimited WU support requests are included at no charge.

It's true that convenience for developers introduces absurb
stuff into software. For example, on the support page, it says
after you run through unlimited, more than that costs set
amounts. That's due I guess to a template applied to all the
pages, of which none but this page offers unlimited free support.

If newsgroups suit you better, consider using a newsreader.
The web interface is pretty good, Outlook Express is better,
however there is a precaution you must take, which is to
conceal your email address to avoid getting spammed.

Start with this link, copied and pasted in IE's address window:
news://msnews.microsoft.com/microsof....windowsupdate
It ought to open this newsgroup in Outlook Express. Before
you post any messages, munge the email it gives out.

I was considering trying MU. I'll think I'll stick with WU. Thanks.
I'm sorry I couldn't solve your problem, but I'm willing to listen
and continue to suggest stuff if that helps you to solve it.

"Eric Harman" <Eric > wrote in
message
news:416D73DF-F41D-44E4-A8AA-...

> Also, here is some info from WindowsUpdate.log when I try and
> manually go to the Microsoft Update website with my XP Pro
> machine:
>
> <snip>
>
> On one of my other machines (XP Home) the messages are a
> little different, but still include, "Error: Agent failed
> detecting with reason: 0x800b0003.
>
> It also includes "Update is not allowed to download due to
> regulation." I'm not exactly sure what "regulation" I'm
> inviolation of here, these are legal copies and they've been
> updating for the last 9-10 months.
>
> Perhaps I do not have a licownze for my menkey? Because
> Microsoft Update is beginning to look like some Inspector
> Clouseau farce.
>
> "Eric Harman" wrote:
>
>> Yes, I had seen an earlier suggestion from someone here to
>> make a batch file that runs regsvr32 on a total of 20 .dlls.
>> I checked that against the list you gave me and indeed every
>> 1 of the 10 is there. It didn't do a thing. I ran it,
>> rebooted, same problem still persists for 3 days now.
>>
>> Thanks for helping, though.
>>
>> Eric Harman
>>
>> "Michael Jennings" wrote:
>>
>>> Softpub.dll, Wintrust.dll, Initpki.dll, Dssenh.dll,
>>> Rsaenh.dll, Gpkcsp.dll, Sccbase.dll, Slbcsp.dll,
>>> Mssip32.dll, and Cryptdlg.dll are the files that should get
>>> the treatment according to
>>> http://support.microsoft.com/default...b;en-us;813442
>>>
>>> Did you try that?
>>>
>>> "Eric Harman" <Eric > wrote
>>> in message
>>> news:39C706E4-1858-40DE-B7BF-...
>>>> I have 3 computers running Windows XP (2 Pro, 1 home) that
>>>> both have this problem when I try and go to Microsoft
>>>> Update. I have used MS update on these same machines before
>>>> for almost a year without a problem. At home my Win2K and
>>>> Win XP Pro machines updated fine.
>>>>
>>>> Trying all the various regsvr32 fixes found by searching
>>>> this forum did NOT fix the problem. All machines have been
>>>> rebooted, caches cleared, spyware checks run, etc.
>>>>
>>>> Any ideas?

Problem solved!

Apparently there must have been a change made to the settings on one of our
corporate firewalls. The last test I tried was to plug my systems into an
external drop so that it was only behind my firewall. That has done it.

Unfortunately when you search for the 0x800b0003 error message in the MS
knowledge base the suggestions don't mention anything about firewall
settings. Worse than that, for the period I was looking for it the article
was unavailable.

Anyway, Michael, thanks much for your help. Finally it was just good old
trial and error. Oh, and I did check the link you'd posted, but none of those
things worked.

Thanks again.

-Eric

"Michael Jennings" wrote:

> Maybe there's a newsgroup for MU. I didn't look thoroughly. My
> second suggestion is also something you've probably tried, which
> is to use Windows Update instead of Microsoft Update.
>
> Microsoft Most Valuable Professionals (MVPs) have not joined
> this thread, and I don't think you clicked on the link I gave
> you.
>
> If you are willing to tangle with Microsoft support, start here:
> http://support.microsoft.com/oas/def...-us&gprid=6527
> Unlimited WU support requests are included at no charge.
>
> It's true that convenience for developers introduces absurb
> stuff into software. For example, on the support page, it says
> after you run through unlimited, more than that costs set
> amounts. That's due I guess to a template applied to all the
> pages, of which none but this page offers unlimited free support.
>
> If newsgroups suit you better, consider using a newsreader.
> The web interface is pretty good, Outlook Express is better,
> however there is a precaution you must take, which is to
> conceal your email address to avoid getting spammed.
>
> Start with this link, copied and pasted in IE's address window:
> news://msnews.microsoft.com/microsof....windowsupdate
> It ought to open this newsgroup in Outlook Express. Before
> you post any messages, munge the email it gives out.
>
> I was considering trying MU. I'll think I'll stick with WU. Thanks.
> I'm sorry I couldn't solve your problem, but I'm willing to listen
> and continue to suggest stuff if that helps you to solve it.
>
> "Eric Harman" <Eric > wrote in
> message
> news:416D73DF-F41D-44E4-A8AA-...
>
> > Also, here is some info from WindowsUpdate.log when I try and
> > manually go to the Microsoft Update website with my XP Pro
> > machine:
> >
> > <snip>
> >
> > On one of my other machines (XP Home) the messages are a
> > little different, but still include, "Error: Agent failed
> > detecting with reason: 0x800b0003.
> >
> > It also includes "Update is not allowed to download due to
> > regulation." I'm not exactly sure what "regulation" I'm
> > inviolation of here, these are legal copies and they've been
> > updating for the last 9-10 months.
> >
> > Perhaps I do not have a licownze for my menkey? Because
> > Microsoft Update is beginning to look like some Inspector
> > Clouseau farce.
> >
> > "Eric Harman" wrote:
> >
> >> Yes, I had seen an earlier suggestion from someone here to
> >> make a batch file that runs regsvr32 on a total of 20 .dlls.
> >> I checked that against the list you gave me and indeed every
> >> 1 of the 10 is there. It didn't do a thing. I ran it,
> >> rebooted, same problem still persists for 3 days now.
> >>
> >> Thanks for helping, though.
> >>
> >> Eric Harman
> >>
> >> "Michael Jennings" wrote:
> >>
> >>> Softpub.dll, Wintrust.dll, Initpki.dll, Dssenh.dll,
> >>> Rsaenh.dll, Gpkcsp.dll, Sccbase.dll, Slbcsp.dll,
> >>> Mssip32.dll, and Cryptdlg.dll are the files that should get
> >>> the treatment according to
> >>> http://support.microsoft.com/default...b;en-us;813442
> >>>
> >>> Did you try that?
> >>>
> >>> "Eric Harman" <Eric > wrote
> >>> in message
> >>> news:39C706E4-1858-40DE-B7BF-...
> >>>> I have 3 computers running Windows XP (2 Pro, 1 home) that
> >>>> both have this problem when I try and go to Microsoft
> >>>> Update. I have used MS update on these same machines before
> >>>> for almost a year without a problem. At home my Win2K and
> >>>> Win XP Pro machines updated fine.
> >>>>
> >>>> Trying all the various regsvr32 fixes found by searching
> >>>> this forum did NOT fix the problem. All machines have been
> >>>> rebooted, caches cleared, spyware checks run, etc.
> >>>>
> >>>> Any ideas?
>
>
>

You are *most* welcome, Eric. Thanks for posting the resolution.
Googlegroups searches on 800B0003 could pick up this thread,
indicating firewall settings for this error per your finding.

"Eric Harman" <> wrote in message
news:659E60FC-25E1-484E-AD1B-...
> Problem solved!
>
> Apparently there must have been a change made to the settings on one of
> our
> corporate firewalls. The last test I tried was to plug my systems into an
> external drop so that it was only behind my firewall. That has done it.
>
> Unfortunately when you search for the 0x800b0003 error message in the MS
> knowledge base the suggestions don't mention anything about firewall
> settings. Worse than that, for the period I was looking for it the article
> was unavailable.
>
> Anyway, Michael, thanks much for your help. Finally it was just good old
> trial and error. Oh, and I did check the link you'd posted, but none of
> those
> things worked.
>
> Thanks again.
>
> -Eric