Error 80040154 Windows Updates on Windows 2000!

Hi everyone,

Can anyone help with the following?

I have got a Windows 2000 Advanced Server with SP4.

I have been trying to donwload windows updates on
http://update.microsoft.com/windowsu....aspx?ln=en-us

and I am getting the following error: "Files required to use Windows Update
are no longer registered or installed on your computer"

I follow the instructions regarding downloading a new version and then the
page loops back on to checking the updates. I always end up with the same
error.

Here are the details of the WindowsUpdate.log file:

2006-01-18 13:17:08 2488 a40 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0000) ===========
2006-01-18 13:17:08 2488 a40 Misc = Process: C:\WINNT\system32\svchost.exe
2006-01-18 13:17:08 2488 a40 Misc = Module: C:\WINNT\system32\wuaueng.dll
2006-01-18 13:17:08 2488 a40 Service *************
2006-01-18 13:17:08 2488 a40 Service ** START ** Service: Service startup
2006-01-18 13:17:08 2488 a40 Service *********
2006-01-18 13:17:08 2488 a40 Agent * WU client version 5.8.0.2469
2006-01-18 13:17:08 2488 a40 Agent * SusClientId =
'8e200c94-a688-43bc-8baa-3b8abf923401'
2006-01-18 13:17:08 2488 a40 Agent * Base directory:
C:\WINNT\SoftwareDistribution
2006-01-18 13:17:08 2488 a40 Agent * Access type: No proxy
2006-01-18 13:17:08 2488 a40 Agent * Network state: Connected
2006-01-18 13:17:18 2488 658 Report WARNING: CEventNamespaceDefinition::Init
failed = 80040154.
2006-01-18 13:17:18 2488 658 Report WARNING: InitReportingComponents failed:
80040154
2006-01-18 13:17:18 2488 658 Agent *********** Agent: Initializing Windows
Update Agent ***********
2006-01-18 13:17:18 2488 658 Agent *********** Agent: Initializing global
settings cache ***********
2006-01-18 13:17:18 2488 658 Agent * WSUS server: <NULL>
2006-01-18 13:17:18 2488 658 Agent * WSUS status server: <NULL>
2006-01-18 13:17:18 2488 658 Agent * Target group: (Unassigned Computers)
2006-01-18 13:17:18 2488 658 Agent * Windows Update access disabled: No
2006-01-18 13:17:20 2488 658 DnldMgr Download manager restoring 0 downloads
2006-01-18 13:17:30 2364 334 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0000) ===========
2006-01-18 13:17:30 2364 334 Misc = Process: C:\Program Files\Internet
Explorer\iexplore.exe
2006-01-18 13:17:30 2364 334 Misc = Module: C:\WINNT\system32\wuweb.dll
2006-01-18 13:17:30 2364 334 Setup *********** Setup: Checking whether
self-update is required ***********
2006-01-18 13:17:30 2364 334 Setup * Inf file:
C:\WINNT\SoftwareDistribution\WebSetup\wusetup.inf
2006-01-18 13:17:30 2364 334 Setup Update NOT required for
C:\WINNT\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-01-18 13:17:30 2364 334 Setup Update NOT required for
C:\WINNT\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-01-18 13:17:30 2364 334 Setup Update NOT required for
C:\WINNT\system32\wuapi.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-01-18 13:17:30 2364 334 Setup Update NOT required for
C:\WINNT\system32\wuauclt.exe: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-01-18 13:17:30 2364 334 Setup Update NOT required for
C:\WINNT\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-01-18 13:17:30 2364 334 Setup Update NOT required for
C:\WINNT\system32\wuaucpl.cpl: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-01-18 13:17:31 2364 334 Setup Update NOT required for
C:\WINNT\system32\wuaueng.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-01-18 13:17:31 2364 334 Setup Update NOT required for
C:\WINNT\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-01-18 13:17:31 2364 334 Setup Update NOT required for
C:\WINNT\system32\wucltui.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-01-18 13:17:31 2364 334 Setup Update NOT required for
C:\WINNT\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-01-18 13:17:31 2364 334 Setup Update NOT required for
C:\WINNT\system32\wups2.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-01-18 13:17:31 2364 334 Setup * IsUpdateRequired = No
2006-01-18 13:17:37 2364 334 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0000) ===========
2006-01-18 13:17:37 2364 334 Misc = Process: C:\Program Files\Internet
Explorer\iexplore.exe
2006-01-18 13:17:37 2364 334 Misc = Module: C:\WINNT\system32\wuapi.dll
2006-01-18 13:17:37 2364 334 COMAPI -------------
2006-01-18 13:17:37 2364 334 COMAPI -- START -- COMAPI: Search [ClientId =
WindowsUpdate]
2006-01-18 13:17:37 2364 334 COMAPI ---------
2006-01-18 13:17:37 2364 334 COMAPI - Online = Yes; Ignore download
priority = No
2006-01-18 13:17:37 2364 334 COMAPI - Criteria = "IsInstalled=0 and
IsHidden=1"
2006-01-18 13:17:37 2364 334 COMAPI - ServiceID =
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2006-01-18 13:17:37 2364 334 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = WindowsUpdate]
2006-01-18 13:17:38 2488 50c Agent *************
2006-01-18 13:17:38 2488 50c Agent ** START ** Agent: Finding updates
[CallerId = WindowsUpdate]
2006-01-18 13:17:38 2488 50c Agent *********
2006-01-18 13:17:41 2488 50c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-01-18 13:17:41 2488 50c PT + ServiceId =
{9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
https://update.microsoft.com/v6/Clie...ce/client.asmx
2006-01-18 13:17:45 2488 50c PT WARNING: Sync of Updates: 0x80040154
2006-01-18 13:17:45 2488 50c Agent * WARNING: Failed to synchronize, error
= 0x80040154
2006-01-18 13:17:45 2488 50c Report WARNING: CEventNamespaceDefinition::Init
failed = 80040154.
2006-01-18 13:17:45 2488 50c Report WARNING: InitReportingComponents failed:
80040154
2006-01-18 13:17:45 2488 50c Agent * WARNING: Exit code = 0x80040154
2006-01-18 13:17:45 2488 50c Agent *********
2006-01-18 13:17:45 2488 50c Agent ** END ** Agent: Finding updates
[CallerId = WindowsUpdate]
2006-01-18 13:17:45 2488 50c Agent *************
2006-01-18 13:17:45 2488 50c Agent WARNING: WU client failed Searching for
update with error 0x80040154
2006-01-18 13:17:45 2364 7d4 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = WindowsUpdate]
2006-01-18 13:17:45 2364 7d4 COMAPI - Updates found = 0
2006-01-18 13:17:45 2364 7d4 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x80040154
2006-01-18 13:17:45 2364 7d4 COMAPI ---------
2006-01-18 13:17:45 2364 7d4 COMAPI -- END -- COMAPI: Search [ClientId =
WindowsUpdate]
2006-01-18 13:17:45 2364 7d4 COMAPI -------------
2006-01-18 13:17:45 2364 334 COMAPI WARNING: Operation failed due to earlier
error, hr=80040154
2006-01-18 13:17:45 2364 334 COMAPI FATAL: Unable to complete asynchronous
search. (hr=80040154)
2006-01-18 13:17:54 2488 a40 Report WARNING: CEventNamespaceDefinition::Init
failed = 80040154.
2006-01-18 13:17:54 2488 a40 Report WARNING: InitReportingComponents failed:
80040154
2006-01-18 13:17:54 2488 a40 AU ########### AU: Initializing Automatic
Updates ###########
2006-01-18 13:17:54 2488 a40 AU # Approval type: Scheduled (User
preference)
2006-01-18 13:17:54 2488 a40 AU # Scheduled install day/time: Every day at
11:00
2006-01-18 13:17:54 2488 a40 AU # Auto-install minor updates: Yes (User
preference)

I have already regsvr32 the msxml3.dll and rebooted but no chance so far

Any suiggestions

Thank you

Corinne

"corinne" <> wrote in message
news:
....
> Here are the details of the WindowsUpdate.log file:
....
> 2006-01-18 13:17:18 2488 658 Report WARNING: CEventNamespaceDefinition::Init failed = 80040154.
> 2006-01-18 13:17:18 2488 658 Report WARNING: InitReportingComponents failed: 80040154


Another case of messages with inadequate supplementary information IMO.

The error code means

http://docxp.mvps.org/WU5-ERR.htm

(MSN search for
0x80040154 microsoft codes
)

<extract>
0x80040154 -2147221164 REGDB E CLASSNOTREG
BITS in Windows 2000 is dependent on SENS and EventSystem services.
If COM+ catalog is corrupted, one of these errors was seen.
</extract>


In previous versions of WU this code was associated with the message
"class not registered" but never gave a clue about which .dll needed to be
registered. In many cases people have been helped by guessing that msxml3.dll
might be the right one. Others have resorted to using a cmd file which
re-registers anything remotely associated with WU (a sort of superset of the
registrations associated with an IE Repair.)

It's possible that you might be able to get sufficient additional information
by applying the verbose logging registry edit

<title>KB902093 - How to read the Windowsupdate.log file</title>

However, I haven't been very impressed with the quality of the verbose
diagnostics that I have seen; so what I usually recommend as a supplement
to the standard logging is to use SysInternals freeware tools FileMon and
RegMon. Then the FileMon filter I like to use for supplementing WU and AU
logging is SoftwareDistribution;update;CatRoot

With RegMon I usually don't have as clear an idea of what a useful inclusive
filter will be so I tend to include everything and exclude stuff which obviously
has no bearing on the session of interest. FWIW if I had to guess
for a more restrictive filter I would try: wu;svchost;iexplore

If you use the tools' common options Clock Time and Show Milleseconds
you can further more easily correlate the additional trace information
with the messages in the install log(s). Although the granularity of the
timestamps in the install logs is not sufficient to directly identify
which message was being written when you notice FileMon
tracing a write to it, it is surprisingly easy to match them up based on
the pattern in the lengths of consecutive records. I use Notepad
with Word Wrap off and Status bar on to be able to see how long
each log record is.

Similarly, in the case of RegMon it is very helpful having the the exact timestamp
for each log record down to the millesecond to be able to find the correct context
in it too. E.g. a procedure would be:

1. list the lengths of the messages you are interested in getting
more information about;
2. then search the FileMon trace for writes to the install log,
looking specifically for the set of them whose "write length:" values
match the lengths you observed using Notepad;
3. then take the timestamps from those trace records and prefix
them to the install log's records. (I actually open up a new Notepad
window and copy just the records I'm interested in to do this.)
4. (optionally) look at all the interleaved other file accesses which
may have had something to do with the production of the message
(e.g. in case a permissions problem is really an ACLS issue
and not a registry permissions issue after all.)
5. browse the RegMon log looking for records whose timestamps
fit within the same time period implied by the install log record
you are interested in and its preceding message.

Somewhere in those interleaved FileMon and RegMon trace entries
should be a clue to help explain the above message, e.g. at least
the name of a .dll which was referenced just before it, etc.


Good luck

Robert Aldwinckle
---

Hi Robert,

Thank you for your reply
I will try your suggestion and report the results later.

Ta!

Regards

Corinne



"Robert Aldwinckle" <> wrote in message
news:...
> "corinne" <> wrote in message
> news:
> ...
>> Here are the details of the WindowsUpdate.log file:
> ...
>> 2006-01-18 13:17:18 2488 658 Report WARNING:
>> CEventNamespaceDefinition::Init failed = 80040154.
>> 2006-01-18 13:17:18 2488 658 Report WARNING: InitReportingComponents
>> failed: 80040154
>
>
> Another case of messages with inadequate supplementary information IMO.
>
> The error code means
>
> http://docxp.mvps.org/WU5-ERR.htm
>
> (MSN search for
> 0x80040154 microsoft codes
> )
>
> <extract>
> 0x80040154 -2147221164 REGDB E CLASSNOTREG
> BITS in Windows 2000 is dependent on SENS and EventSystem
> services.
> If COM+ catalog is corrupted, one of these errors was seen.
> </extract>
>
>
> In previous versions of WU this code was associated with the message
> "class not registered" but never gave a clue about which .dll needed to
> be
> registered. In many cases people have been helped by guessing that
> msxml3.dll
> might be the right one. Others have resorted to using a cmd file which
> re-registers anything remotely associated with WU (a sort of superset of
> the
> registrations associated with an IE Repair.)
>
> It's possible that you might be able to get sufficient additional
> information
> by applying the verbose logging registry edit
>
> <title>KB902093 - How to read the Windowsupdate.log file</title>
>
> However, I haven't been very impressed with the quality of the verbose
> diagnostics that I have seen; so what I usually recommend as a supplement
> to the standard logging is to use SysInternals freeware tools FileMon
> and
> RegMon. Then the FileMon filter I like to use for supplementing WU and
> AU
> logging is SoftwareDistribution;update;CatRoot
>
> With RegMon I usually don't have as clear an idea of what a useful
> inclusive
> filter will be so I tend to include everything and exclude stuff which
> obviously
> has no bearing on the session of interest. FWIW if I had to guess
> for a more restrictive filter I would try: wu;svchost;iexplore
>
> If you use the tools' common options Clock Time and Show Milleseconds
> you can further more easily correlate the additional trace information
> with the messages in the install log(s). Although the granularity of the
> timestamps in the install logs is not sufficient to directly identify
> which message was being written when you notice FileMon
> tracing a write to it, it is surprisingly easy to match them up based on
> the pattern in the lengths of consecutive records. I use Notepad
> with Word Wrap off and Status bar on to be able to see how long
> each log record is.
>
> Similarly, in the case of RegMon it is very helpful having the the exact
> timestamp
> for each log record down to the millesecond to be able to find the correct
> context
> in it too. E.g. a procedure would be:
>
> 1. list the lengths of the messages you are interested in getting
> more information about;
> 2. then search the FileMon trace for writes to the install log,
> looking specifically for the set of them whose "write length:" values
> match the lengths you observed using Notepad;
> 3. then take the timestamps from those trace records and prefix
> them to the install log's records. (I actually open up a new Notepad
> window and copy just the records I'm interested in to do this.)
> 4. (optionally) look at all the interleaved other file accesses which
> may have had something to do with the production of the message
> (e.g. in case a permissions problem is really an ACLS issue
> and not a registry permissions issue after all.)
> 5. browse the RegMon log looking for records whose timestamps
> fit within the same time period implied by the install log record
> you are interested in and its preceding message.
>
> Somewhere in those interleaved FileMon and RegMon trace entries
> should be a clue to help explain the above message, e.g. at least
> the name of a .dll which was referenced just before it, etc.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>