"longwoodaugustsystem" wrote:
> Try this
>
> http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windowsxp.security_admin&tid=dd0d065a-7140-40c8-bcb9-18c8a0857a37
>
> "racegrl" wrote:
>
> > I am trying to download SP2 using automatic update. Every time I hit the
> > button to scan for updates (whether it's the express install or custom
> > install), I get the error 0x8024401A. I have the services automatic update,
> > BITS, and event log all set to "automatic" and "started". I am running the
> > English version. I get no errors in the event logs. The only thing the
> > website tells me is:
> >
> > "Windows Update has encountered an error and cannot display the requested
> > page. You may find the following resources helpful in resolving the problem"
> >
> > Any help is greatly appreciated, I've been trying for two days to get this
> > downloaded.
> >
> > Thanks,
> >
> > Lynda
-I manually downloaded and installed the BITS 2.0 and HTTP
5.1 update from Microsoft. You can find the link at
http://support.microsoft.com/default.aspx?scid=kb;en-
us;842773. I tried the other solutions suggested on the
newsgroups first and they didn't work, but installing the
updates did.
-Nick D. JAT (Just Another Techie, no Microsoft Alphabet
soup ^^)
>-----Original Message-----
>I am trying to download SP2 using automatic update. Every
time I hit the
>button to scan for updates (whether it's the express
install or custom
>install), I get the error 0x8024401A. I have the services
automatic update,
>BITS, and event log all set to "automatic" and "started".
I am running the
>English version. I get no errors in the event logs. The
only thing the
>website tells me is:
>
>"Windows Update has encountered an error and cannot
display the requested
>page. You may find the following resources helpful in
resolving the problem"
>
>Any help is greatly appreciated, I've been trying for two
days to get this
>downloaded.
>
>Thanks,
>
>Lynda
>.
>
> Youre link dosn't work anymore
Hi
You need to unwrap it (it was over two lines), like this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842773
--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx
Are you saying you're using a proxy server?
What diagnostics does it have?
Perhaps it would give you some clues about what is happening.
Otherwise since there are clearly no canned solutions for you
you are going to have to troubleshoot your case.
Have you looked in the windowsupdate.log for some context
for the error code?
If there is not enough detail in there to definitely point to a cause
you might have to resort to a packet trace.
Is this XP Pro? In that case you could activate its netcap packet
trace. Otherwise you could use third-party tools such as Ethereal.
Torgeir also mentions something called "verbose" tracing.
Perhaps it would be a simpler substitute.
Good luck
Robert Aldwinckle
---
I'm having the same problem.
This is an extract from windowsupdate.log:
004-09-17 20:09:38+0200 816 d40 Trying to make out of proc datastore active
2004-09-17 20:09:38+0200 816 d40 Out of proc datastore is now active
2004-09-17 20:09:39+0200 856 f24 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-09-17 20:09:39+0200 856 f24 PT: Using server URL
https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
2004-09-17 20:09:39+0200 856 f24 Add header for accept-encoding: xpress
succeeded
2004-09-17 20:09:40+0200 856 f24 DetectCompressionType returning type 0,
hr=0x1
2004-09-17 20:09:40+0200 856 f24 SyncUpdates: 0x8024401a
2004-09-17 20:09:40+0200 856 f24 PT: Cannot recover from fault,
origin=SyncUpdates, hr=0x8024401a
2004-09-17 20:09:40+0200 856 f24 Sync of Updates: 0x8024401a
2004-09-17 20:09:40+0200 856 f24 WU client failed Searching for update with
error 0x8024401a
2004-09-17 20:09:40+0200 856 f24 WU client calls back to search call
WindowsUpdate with code Call failed and error 0x8024401a
2004-09-17 20:09:40+0200 856 f24 WU client completed and deleted call
{45ED8D9C-BFBF-499F-A392-B197ADC7E77B}
2004-09-17 20:09:40+0200 2864 f90 Operation completed due to earlier error.
(hr=8024401A)
2004-09-17 20:09:40+0200 2864 f90 Unable to complete asynchronous search
successfully. (hr=8024401A)
2004-09-17 20:09:45+0200 856 f24 REPORT EVENT:
{28396566-F12D-443A-A04C-A41449524A38} 70 2004-09-17
20:09:40+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024401a WindowsUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8024401a
2004-09-17 20:14:40+0200 816 d40 Out of proc datastore is shutting down
2004-09-17 20:14:41+0200 816 d40 Out of proc datastore is now inactive
Surely some Microsoft tech should be able to figure out what this hResult
code means?
Koen
Thanks,
Rahul
"Koen C" <Koen C...@discussions.microsoft.com> wrote in message
news:73FCE323-E295-4FBB...@microsoft.com...
BITS ATTEMPTS TO RETRIEVE PROXY DATA VIA WAPD (windows automatic proxy
discovery) EVEN WHEN IT'S TOLD NOT TO!!!
All the attemts to do WAPD on my network lead to a stub WWW server
displaying a "you connected to this network without my authorization, it is
illegal" (a deterrent for people with Windows with default connection
settings who try to sneak onto my wireless network). Though "automatic proxy
discovery" was disabled in my laptop's Internet options, Windows Update was
seemingly bumping into my stub server all the time! :/ How stupid. As I
removed the stub WAPD.DAT file from my web server, thus disabling WAPD on the
server side, WU started to work!
I haven't diagnosed the problem, if I have time later I can have a look and
get back to this thread. I am running SP2 on a Professional. My guess is that
the new firewall in windows is doing something wrong (it has a few very
annoying bugs when it comes to two or more NIC cards)
Cheers,
Niclas
You can check your actual configuration by typing "proxycfg" (without
quotes!) in the command line. However, to establish the correct configuration
of the proxy, you can execute "proxycfg -u" to use the MSIE settings, or
execute "proxycfg -d" for direct connection settings. If you use a specific
proxy, please refer to the proxycfg help ("proxycfg /?").
Do not forget to reboot your computer in order to restore the new settings!
Good luck,
Alex
In english:
1. disable all check boxes in Internet Explorer Lan settings
(IE>Extra>Options>Connections> Lan Settings button)
2. open a command prompt window and enter proxycfg -d (this activates DIRECT
TYPE proxy setting; verify with proxycfg (without parameters)
3. reboot
4. run windows update
good luck!
Koen