J
J Lunis
XP SR2
Windows Services gives me an error of 'Interface: class not registered'
when I check dependencies of any service.
In addition, I have a frequent Event Viewer error relating to DCOM
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Description:
The server {A1F4E726-8CF1-11D1-BF92-0060081ED811} did not register
with DCOM within the required timeout.
Under Local Area Connection Status>Properties>Advanced I have
'Windows can not display the Properties of this connection. The Windows
Management Instrumentation (WMI)information might be corrupted.'
These errors are related to WMI so I ran WMIdiag. Found some errors but
do not understand how I can correct them. Guidance please.
..1230 08:42:57 (1) !! ERROR: WMI ADAP status:
..................................................................... NOT
AVAILABLE
..1231 08:42:57 (0) ** You can start the WMI AutoDiscovery/AutoPurge
(ADAP) process to resynchronize
..1232 08:42:57 (0) ** the performance counters with the WMI
performance classes with the following commands:
..1233 08:42:57 (0) ** e.g. 'WINMGMT.EXE /CLEARADAP'
..1234 08:42:57 (0) ** e.g. 'WINMGMT.EXE /RESYNCPERF'
..1235 08:42:57 (0) ** The ADAP process logs informative events in the
Windows NT event log.
******NOTE: I ran the above commands in the CMD window. Have no idea
if it made a difference. ******************
..1238 08:42:57 (1) !! ERROR: WMI CONNECTION errors occured for the
following namespaces: ......................... 5 ERROR(S)!
..1239 08:42:57 (0) ** - Root, 0x80040154 - Class not registered.
..1240 08:42:57 (0) ** - Root, 0x80040154 - Class not registered.
..1241 08:42:57 (0) ** - Root/Default, 0x80040154 - Class not registered.
..1242 08:42:57 (0) ** - Root/CIMv2, 0x80040154 - Class not registered.
..1243 08:42:57 (0) ** - Root/WMI, 0x80040154 - Class not registered.
..1253 08:42:57 (0) ** WMI static instances retrieved:
............................................................. 0.
..1254 08:42:57 (0) ** WMI dynamic instances retrieved:
............................................................ 0.
..1255 08:42:57 (0) ** WMI instances request cancellations (to limit
performance impact): ......................... 0.
..1256 08:42:57 (0) **
..1257 08:42:57 (0) ** 5 error(s) 0x80040154 - (WBEM_UNKNOWN) This error
code is external to WMI.
..1258 08:42:57 (0) ** => This error is not a WMI error. This error is a
typical DCOM registration error.
..1259 08:42:57 (0) ** The registry information for DCOM to initialize
a DCOM object is missing or wrongly configured.
..1260 08:42:57 (0) ** => You can correct the DCOM configuration by:
..1261 08:42:57 (0) ** - Executing the 'Filename.EXE /RegServer' command.
..1262 08:42:57 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>'
command.
..1263 08:42:57 (0) ** Note: You can build a list of classes in
relation with their WMI provider and MOF file with WMIDiag.
..1264 08:42:57 (0) ** (This list can be built on a similar and
working WMI Windows installation)
..1265 08:42:57 (0) ** The following command line must be used:
..1266 08:42:57 (0) ** e.g. 'WMIDiag CorrelateClassAndProvider'
..1267 08:42:57 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL
from 'C:\WINDOWS\SYSTEM32\WBEM\'
..1268 08:42:57 (0) ** may not solve the problem as the DLL
supporting the WMI class(es)
..1269 08:42:57 (0) ** can be located in a different folder.
..1270 08:42:57 (0) ** You must refer to the class name to
determine the software delivering the related DLL.
..1271 08:42:57 (0) ** - Re-installing the software.
Windows Services gives me an error of 'Interface: class not registered'
when I check dependencies of any service.
In addition, I have a frequent Event Viewer error relating to DCOM
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Description:
The server {A1F4E726-8CF1-11D1-BF92-0060081ED811} did not register
with DCOM within the required timeout.
Under Local Area Connection Status>Properties>Advanced I have
'Windows can not display the Properties of this connection. The Windows
Management Instrumentation (WMI)information might be corrupted.'
These errors are related to WMI so I ran WMIdiag. Found some errors but
do not understand how I can correct them. Guidance please.
..1230 08:42:57 (1) !! ERROR: WMI ADAP status:
..................................................................... NOT
AVAILABLE
..1231 08:42:57 (0) ** You can start the WMI AutoDiscovery/AutoPurge
(ADAP) process to resynchronize
..1232 08:42:57 (0) ** the performance counters with the WMI
performance classes with the following commands:
..1233 08:42:57 (0) ** e.g. 'WINMGMT.EXE /CLEARADAP'
..1234 08:42:57 (0) ** e.g. 'WINMGMT.EXE /RESYNCPERF'
..1235 08:42:57 (0) ** The ADAP process logs informative events in the
Windows NT event log.
******NOTE: I ran the above commands in the CMD window. Have no idea
if it made a difference. ******************
..1238 08:42:57 (1) !! ERROR: WMI CONNECTION errors occured for the
following namespaces: ......................... 5 ERROR(S)!
..1239 08:42:57 (0) ** - Root, 0x80040154 - Class not registered.
..1240 08:42:57 (0) ** - Root, 0x80040154 - Class not registered.
..1241 08:42:57 (0) ** - Root/Default, 0x80040154 - Class not registered.
..1242 08:42:57 (0) ** - Root/CIMv2, 0x80040154 - Class not registered.
..1243 08:42:57 (0) ** - Root/WMI, 0x80040154 - Class not registered.
..1253 08:42:57 (0) ** WMI static instances retrieved:
............................................................. 0.
..1254 08:42:57 (0) ** WMI dynamic instances retrieved:
............................................................ 0.
..1255 08:42:57 (0) ** WMI instances request cancellations (to limit
performance impact): ......................... 0.
..1256 08:42:57 (0) **
..1257 08:42:57 (0) ** 5 error(s) 0x80040154 - (WBEM_UNKNOWN) This error
code is external to WMI.
..1258 08:42:57 (0) ** => This error is not a WMI error. This error is a
typical DCOM registration error.
..1259 08:42:57 (0) ** The registry information for DCOM to initialize
a DCOM object is missing or wrongly configured.
..1260 08:42:57 (0) ** => You can correct the DCOM configuration by:
..1261 08:42:57 (0) ** - Executing the 'Filename.EXE /RegServer' command.
..1262 08:42:57 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>'
command.
..1263 08:42:57 (0) ** Note: You can build a list of classes in
relation with their WMI provider and MOF file with WMIDiag.
..1264 08:42:57 (0) ** (This list can be built on a similar and
working WMI Windows installation)
..1265 08:42:57 (0) ** The following command line must be used:
..1266 08:42:57 (0) ** e.g. 'WMIDiag CorrelateClassAndProvider'
..1267 08:42:57 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL
from 'C:\WINDOWS\SYSTEM32\WBEM\'
..1268 08:42:57 (0) ** may not solve the problem as the DLL
supporting the WMI class(es)
..1269 08:42:57 (0) ** can be located in a different folder.
..1270 08:42:57 (0) ** You must refer to the class name to
determine the software delivering the related DLL.
..1271 08:42:57 (0) ** - Re-installing the software.