Error number: 0x8024E001

after september updates "Error number: 0x8024E001" in update.microsoft.com

I have problems with WSUS 3.0 Beta 2. Workstations that are applied to WSUS
cannot update through Microsoft Update or Windows Update web pages. Error
number is 0x8024E001 when I try to go to the update pages. Same error appears
in those workstations' WindowsUpdate.log files. They cannot contact the WSUS
server neither. Apparently some kind of expression handler error..

Yesterday updating through WSUS or Windows Update web pages succeeded. The
problem appeared today.

Anyone having the same problem or same error? Any solutions?

"Evgesh" wrote:

> after september updates "Error number: 0x8024E001" in update.microsoft.com

I am having the same error today. I don't have a solution.

I also have the same problem and I know it has something to do w/ the
Background Intelligence Transfer Service not starting automatically. I even
try starting it manually, it will not start.

"Evgesh" <> wrote in message
news:E5B3DD98-66D3-4E2E-903C-...
> after september updates "Error number: 0x8024E001" in update.microsoft.com

I am also having the same problem on Windows 2000 servers. Any insight in how
to resolve the issue would be appreciated. The servers are managed in a WSUS
environment.

"Roget Luo" wrote:

> I also have the same problem and I know it has something to do w/ the
> Background Intelligence Transfer Service not starting automatically. I even
> try starting it manually, it will not start.
>
> "Evgesh" <> wrote in message
> news:E5B3DD98-66D3-4E2E-903C-...
> > after september updates "Error number: 0x8024E001" in update.microsoft.com
>
>
>

I have the same thing with 3 machines now, 2 XP SP@ and a Windows 2003 SBS
server.

The WindowsUpdate.log shows the same thing crashed on install:
-------------
2006-09-21 09:15:17:104 968 148 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-09-21 09:15:17:104 968 148 PT + ServiceId =
{7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
https://beta.update.microsoft.com/v6...ce/client.asmx
2006-09-21 09:15:35:544 968 148 EEHndlr FATAL: EE Serializer: Encountered
unknown expression b.LicenseDword
2006-09-21 09:15:35:544 968 148 EEHndlr FATAL: Parse failed: error 0x8024e001
--------------
I hope this gets fixed soon

"Evgesh" wrote:

> after september updates "Error number: 0x8024E001" in update.microsoft.com

Just curious, did this start happening to all of you about couple of days
ago. I was configuring a system on Monday (9/18) and everything was fine.


"dcstar" <> wrote in message
news:42D01497-060D-42CF-B52F-...
>I have the same thing with 3 machines now, 2 XP SP@ and a Windows 2003 SBS
> server.
>
> The WindowsUpdate.log shows the same thing crashed on install:
> -------------
> 2006-09-21 09:15:17:104 968 148 PT +++++++++++ PT: Synchronizing server
> updates +++++++++++
> 2006-09-21 09:15:17:104 968 148 PT + ServiceId =
> {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
> https://beta.update.microsoft.com/v6...ce/client.asmx
> 2006-09-21 09:15:35:544 968 148 EEHndlr FATAL: EE Serializer: Encountered
> unknown expression b.LicenseDword
> 2006-09-21 09:15:35:544 968 148 EEHndlr FATAL: Parse failed: error
> 0x8024e001
> --------------
> I hope this gets fixed soon
>
> "Evgesh" wrote:
>
>> after september updates "Error number: 0x8024E001" in
>> update.microsoft.com

We saw this issue in the last couple of days on Windows 2000 desktops,
Windows 2000 Servers and Windows 2000 domain controllers.

"Roget Luo" wrote:

> Just curious, did this start happening to all of you about couple of days
> ago. I was configuring a system on Monday (9/18) and everything was fine.
>
>
> "dcstar" <> wrote in message
> news:42D01497-060D-42CF-B52F-...
> >I have the same thing with 3 machines now, 2 XP SP@ and a Windows 2003 SBS
> > server.
> >
> > The WindowsUpdate.log shows the same thing crashed on install:
> > -------------
> > 2006-09-21 09:15:17:104 968 148 PT +++++++++++ PT: Synchronizing server
> > updates +++++++++++
> > 2006-09-21 09:15:17:104 968 148 PT + ServiceId =
> > {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
> > https://beta.update.microsoft.com/v6...ce/client.asmx
> > 2006-09-21 09:15:35:544 968 148 EEHndlr FATAL: EE Serializer: Encountered
> > unknown expression b.LicenseDword
> > 2006-09-21 09:15:35:544 968 148 EEHndlr FATAL: Parse failed: error
> > 0x8024e001
> > --------------
> > I hope this gets fixed soon
> >
> > "Evgesh" wrote:
> >
> >> after september updates "Error number: 0x8024E001" in
> >> update.microsoft.com
>
>
>

"Roget Luo" wrote:

> Just curious, did this start happening to all of you about couple of days
> ago. I was configuring a system on Monday (9/18) and everything was fine.
>
I only got the WSUS Beta software going yesterday, so that is when all my
problems started...... :-(

I think it got something to do with the workstation's Update Client. And I
think the broken client has come from the WSUS Server. That's because the
(test) workstations that are configured to use the WSUS (3.0 Beta 2) cannot
use the Windows Update pages no more. The error 0x8024E001 appears.

But all of our "normal" workstations can use the Windows Update pages
succesfully without that error.

"Roget Luo" wrote:

> I also have the same problem and I know it has something to do w/ the
> Background Intelligence Transfer Service not starting automatically. I even
> try starting it manually, it will not start.
>
> "Evgesh" <> wrote in message
> news:E5B3DD98-66D3-4E2E-903C-...
> > after september updates "Error number: 0x8024E001" in update.microsoft.com
>
>
>