Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to do Window Updates- Error # 0x8024E001

657 views
Skip to first unread message

Roget Luo

unread,
Sep 20, 2006, 6:41:50 PM9/20/06
to
Before I buck up and pay Microsoft $250 for support, I hope someone here can
help me out. Thanks in advance.

Running in Windows 2003 environment and was successful using a Win 2003 R2
system to host WSUS. Everything was fine as of Monday, but now, none of the
computers can do Win Updates. Once I click on the Express or Custom scan,
it gives me the following msg:

"The website has encountered a problem and cannot display the page you are
trying to view. The options provided below might help you solve the problem.
and Error Number: 0x8024E001.

For a while there I thought it was the Background Intelligence Transfer
Service that is giving me problems, it was Stopped and set to Manual start.
I was not able to start/ restart it until I deleted the group policy
associated to WSUS. However, I still get the same error message even after
starting BITS. Also, this problem affects all systems in our network, 2003,
XP & 2000.

Also, we didn't make any group policy changes in our network the past couple
of days.

Thanks,
Roget


Dave Allerton

unread,
Sep 21, 2006, 12:43:02 PM9/21/06
to
Roget,
Thats a coincidence - i'm getting exactly the same error on all of my WSUS
clients. We're using 2003 R2 as well. We're also using WSUS 3.0 Beta, which i
thought may be causing the problem. What version of WSUS are you running?

Galvan@discussions.microsoft.com Isaac Galvan

unread,
Sep 21, 2006, 1:11:02 PM9/21/06
to
We are also having the same issue suddenly and it was seemingly unprovoked.
Here is WindowsUpdate.log from one of the clients:

2006-09-21 11:31:13:607 1360 ae4 AU Triggering AU detection through
DetectNow API
2006-09-21 11:31:13:607 1360 314 AU #############
2006-09-21 11:31:13:607 1360 314 AU ## START ## AU: Search for updates
2006-09-21 11:31:13:607 1360 314 AU #########
2006-09-21 11:31:13:607 1360 314 Misc cached token 00001450 for elevated non
admin
2006-09-21 11:31:13:607 1360 314 Misc cached token 00001450 released
2006-09-21 11:31:13:607 1360 314 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {C0280578-9BA2-40B1-A402-34A10935C157}]
2006-09-21 11:31:13:623 1360 52c Agent *************
2006-09-21 11:31:13:623 1360 52c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-09-21 11:31:13:623 1360 52c Agent *********
2006-09-21 11:31:13:623 1360 52c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2006-09-21 11:31:13:623 1360 52c Misc Microsoft signed: Yes
2006-09-21 11:31:13:623 1360 52c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2006-09-21 11:31:13:623 1360 52c Misc Microsoft signed: Yes
2006-09-21 11:31:13:639 1360 52c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2006-09-21 11:31:13:639 1360 52c Misc Microsoft signed: Yes
2006-09-21 11:31:13:654 1360 52c Setup *********** Setup: Checking whether
self-update is required ***********
2006-09-21 11:31:13:654 1360 52c Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.0.5451.90, required version =
7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.0.5451.90, required version
= 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.5451.90, required
version = 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.0.5451.90, required version
= 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.0.5451.90, required version
= 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.0.5451.90, required version
= 7.0.5451.90
2006-09-21 11:31:13:654 1360 52c Setup * IsUpdateRequired = No
2006-09-21 11:31:14:484 1360 52c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-09-21 11:31:14:484 1360 52c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus/ClientWebService/client.asmx
2006-09-21 11:31:14:641 1360 52c PT WARNING: Cached cookie has expired or
new PID is available
2006-09-21 11:31:14:641 1360 52c PT Initializing simple targeting cookie,
clientId = f50b81da-560b-48b2-9ff3-4b461eb71277, target group = , DNS name =
(Client Name)
2006-09-21 11:31:14:641 1360 52c PT Server URL =
http://WSUS/SimpleAuthWebService/SimpleAuth.asmx
2006-09-21 11:31:15:628 1360 52c EEHndlr FATAL: EE Serializer: Encountered
unknown expression b.LicenseDword
2006-09-21 11:31:15:628 1360 52c EEHndlr FATAL: Parse failed: error 0x8024e001
2006-09-21 11:31:15:628 1360 52c EEHndlr FATAL: Parse failed with 0x8024e001

2006-09-21 11:31:15:628 1360 52c PT WARNING: PopulateDataStore failed:
0x8024e001
2006-09-21 11:31:15:628 1360 52c PT WARNING: Sync of Updates: 0x8024e001
2006-09-21 11:31:15:628 1360 52c PT WARNING: SyncServerUpdatesInternal
failed: 0x8024e001
2006-09-21 11:31:15:628 1360 52c Agent * WARNING: Failed to synchronize,
error = 0x8024E001
2006-09-21 11:31:15:644 1360 52c Agent * WARNING: Exit code = 0x8024E001
2006-09-21 11:31:15:644 1360 52c Agent *********
2006-09-21 11:31:15:644 1360 52c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-09-21 11:31:15:644 1360 52c Agent *************
2006-09-21 11:31:15:644 1360 52c Agent WARNING: WU client failed Searching
for update with error 0x8024e001
2006-09-21 11:31:15:659 1360 52c AU >>## RESUMED ## AU: Search for updates
[CallId = {C0280578-9BA2-40B1-A402-34A10935C157}]
2006-09-21 11:31:15:659 1360 52c AU # WARNING: Search callback failed,
result = 0x8024E001
2006-09-21 11:31:15:659 1360 52c AU # WARNING: Failed to find updates with
error code 8024E001
2006-09-21 11:31:15:659 1360 52c AU #########
2006-09-21 11:31:15:659 1360 52c AU ## END ## AU: Search for updates
[CallId = {C0280578-9BA2-40B1-A402-34A10935C157}]
2006-09-21 11:31:15:659 1360 52c AU #############
2006-09-21 11:31:15:659 1360 52c AU AU setting next detection timeout to
2006-09-21 21:31:15
2006-09-21 11:31:20:656 1360 52c Report REPORT EVENT:
{E5B75E8E-862E-4F81-A219-9FDA855FF1BE} 2006-09-21
11:31:15:628-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024e001 AutomaticUpdates Failure Software
Synchronization Windows Update Client failed to detect with error 0x8024e001.


I've tried looking all over for error 0x8024e001 and "Serializer:
Encountered unknown expression b.LicenseDword" with no luck. Any ideas here?
Thanks.

Scott

unread,
Sep 21, 2006, 1:16:02 PM9/21/06
to
I am having the same problem and i have no idea why . I cant find anything
my log stats


2006-09-21 10:03:33:401 1172 4a4 EEHndlr FATAL: EE Serializer: Encountered
unknown expression b.LicenseDword
2006-09-21 10:03:33:401 1172 4a4 EEHndlr FATAL: Parse failed: error 0x8024e001
2006-09-21 10:03:33:401 1172 4a4 EEHndlr FATAL: Parse failed with 0x8024e001

2006-09-21 10:03:33:401 1172 4a4 PT WARNING: PopulateDataStore failed:
0x8024e001
2006-09-21 10:03:33:401 1172 4a4 PT WARNING: Sync of Updates: 0x8024e001
2006-09-21 10:03:33:401 1172 4a4 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024e001
2006-09-21 10:03:33:401 1172 4a4 Agent * WARNING: Failed to synchronize,
error = 0x8024E001
2006-09-21 10:03:33:401 1172 4a4 Agent * WARNING: Exit code = 0x8024E001
2006-09-21 10:03:33:401 1172 4a4 Agent *********
2006-09-21 10:03:33:401 1172 4a4 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-09-21 10:03:33:401 1172 4a4 Agent *************
2006-09-21 10:03:33:401 1172 4a4 Agent WARNING: WU client failed Searching

for update with error 0x8024e001

2006-09-21 10:03:33:401 1172 4a4 AU >>## RESUMED ## AU: Search for updates
[CallId = {5919F012-DDB0-4EB2-BC84-56CEF83AE927}]
2006-09-21 10:03:33:401 1172 4a4 AU # WARNING: Search callback failed,
result = 0x8024E001
2006-09-21 10:03:33:401 1172 4a4 AU # WARNING: Failed to find updates with
error code 8024E001
2006-09-21 10:03:33:401 1172 4a4 AU #########
2006-09-21 10:03:33:401 1172 4a4 AU ## END ## AU: Search for updates
[CallId = {5919F012-DDB0-4EB2-BC84-56CEF83AE927}]
2006-09-21 10:03:33:401 1172 4a4 AU #############
2006-09-21 10:03:33:416 1172 4a4 AU AU setting next detection timeout to
2006-09-21 22:03:33
2006-09-21 10:03:38:373 1172 4a4 Report REPORT EVENT:
{8ECD62C9-F1A0-432F-ABE3-897BBD3B45F8} 2006-09-21
10:03:33:401-0700 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024e001 AutomaticUpdates Failure Software

Synchronization Windows Update Client failed to detect with error 0x8024e001.

using Windows Server Update Services 3.0
Need help bad

Scott

unread,
Sep 21, 2006, 1:22:01 PM9/21/06
to
the only other thing i see in event viewer is

Event Type: Information
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 3454
Date: 9/21/2006
Time: 9:42:06 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: CCR-PS
Description:
The description for Event ID ( 3454 ) in Source ( MSSQL$MICROSOFT##SSEE )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote computer.
You may be able to use the /AUXSOURCE= flag to retrieve this description; see
Help and Support for details. The following information is part of the event:
SUSDB, 5.
Data:
0000: 7e 0d 00 00 0a 00 00 00 ~.......
0008: 17 00 00 00 43 00 43 00 ....C.C.
0010: 52 00 2d 00 50 00 53 00 R.-.P.S.
0018: 5c 00 4d 00 49 00 43 00 \.M.I.C.
0020: 52 00 4f 00 53 00 4f 00 R.O.S.O.
0028: 46 00 54 00 23 00 23 00 F.T.#.#.
0030: 53 00 53 00 45 00 45 00 S.S.E.E.
0038: 00 00 07 00 00 00 6d 00 ......m.
0040: 61 00 73 00 74 00 65 00 a.s.t.e.
0048: 72 00 00 00 r...


But look like were all having the same problem. I was worried I changed
something but it look like their wroung. My was working fine for about a 2
weeks then every pc and server started getting this error. I am lost

Tempted to uninstall and reinstall but have not idea what more that going to
break

Scott

unread,
Sep 21, 2006, 2:08:02 PM9/21/06
to
All I can find is this
0x8024e001
-2145067007
WU_E_EE_UNKNOWN_EXPRESSION
an expression handler was passed an expression that it doesn't know about

http://www.wsus.info/forums/index.php?act=Attach&type=post&id=177

So not helping me

Roget Luo

unread,
Sep 22, 2006, 12:23:12 AM9/22/06
to
Hi guys,

I found this post from another newsgroup, I just tested it out and it works.

"Here is the post from the official WSUS 3.0 beta newsgroup:

Hi Folks - just wanted you to know revised categories have been
published
and verified not to cause errors and issues with downlevel clients. Two
new
categories which were published yesterday in the Windows product family
were
revised to address this issue.

To obtain the repaired categories and get your clients operating
without
error due to this issue, you should resynch your WSUS 3.0 B2 server
manually
to get the category revisions. Client behaivor will resume as before
this
issue. If you prefer you can wait for your next scheduled synch to
revise
these categories and resolve this issue. Either way this issue will no

longer be a problem after your next server synch with BUMC.

Thank you for your patience and enduring any delay to your testing.
-Bobbie
--
Bobbie Harder
Program Manager, WSUS
Microsoft"


Good luck,
Roget


"Roget Luo" <roge...@hotmail.com> wrote in message
news:eIpL3XQ3...@TK2MSFTNGP05.phx.gbl...

Dave Allerton

unread,
Sep 22, 2006, 4:06:01 AM9/22/06
to
Just saw the same posting! Works here too.

Thanks all

Isaac Galvan

unread,
Sep 22, 2006, 11:13:01 AM9/22/06
to
Did a manual windows update on my WSUS server before leaving work last night,
and this morning its working again. I wish they would have let us know that
it was broken so that I didn't have to spend half a day trying to figure out
what I did wrong. It is still a beta though....

Lawrence Garvin (MVP)

unread,
Sep 22, 2006, 6:50:46 PM9/22/06
to
"Roget Luo" <roge...@hotmail.com> wrote in message
news:OkVBx6f3...@TK2MSFTNGP04.phx.gbl...

> Hi guys,
>
> I found this post from another newsgroup, I just tested it out and it
> works.
>
> "Here is the post from the official WSUS 3.0 beta newsgroup:

Please DO NOT CROSSPOST from the WSUS 3.0 beta newsgroup into this
newsgroup.

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....


0 new messages