Ramesh,
I ran the WBEM repair and got this in the setup.log:
(Wed May 03 11:29:44 2006): Beginning WBEM Service Pack Installation
(Wed May 03 11:29:44 2006): Current build of wbemupgd.dll is 5.1.2600.2180
(xpsp_sp2_rtm.040803-2158)
(Wed May 03 11:29:44 2006): Current build of wbemcore.dll is 5.1.2600.2180
(xpsp_sp2_rtm.040803-2158)
(Wed May 03 11:29:44 2006): Failing Connecting to Namespace [root\default]
with result [80040154]
(Wed May 03 11:29:44 2006): One or more core modules is not registered;
registering.
(Wed May 03 11:29:46 2006): Failing Connecting to Namespace [root\default]
with result [80040154]
(Wed May 03 11:29:46 2006): Failing Connecting to Namespace [root\default]
with result [80040154]
(Wed May 03 11:29:46 2006): Failing Connecting to Namespace [root\default]
with result [80040154]
(Wed May 03 11:29:47 2006): Failing Connecting to Namespace [root] with
result [80040154]
(Wed May 03 11:29:47 2006): Wbemupgd.dll Service Security upgrade succeeded
(XP SP update).
(Wed May 03 11:29:47 2006): WBEM Service Pack Installation completed.
(Wed May 03 11:29:47 2006):
Then, with the WMI Diag, I got this report--I don't know which files in WBEM
to register or exactly what to do:
ERROR(S)!
..1272 10:33:33 (0) ** - Root, 0x80040154 - Class not registered.
..1273 10:33:33 (0) ** - Root, 0x80040154 - Class not registered.
..1274 10:33:33 (0) ** - Root/Default, 0x80040154 - Class not registered.
..1275 10:33:33 (0) ** - Root/CIMv2, 0x80040154 - Class not registered.
..1276 10:33:33 (0) ** - Root/WMI, 0x80040154 - Class not registered.
..1277 10:33:33 (0) **
..1278 10:33:33 (0) ** WMI GET static operations:
.................................................................. OK.
..1279 10:33:33 (0) ** WMI MOF representations:
.................................................................... OK.
..1280 10:33:33 (0) ** WMI QUALIFIER access operations:
............................................................ OK.
..1281 10:33:33 (0) ** WMI ENUMERATION operations:
................................................................. OK.
..1282 10:33:33 (0) ** WMI EXECQUERY operations:
................................................................... OK.
..1283 10:33:33 (0) ** WMI PUT operations:
......................................................................... OK.
..1284 10:33:33 (0) ** WMI DELETE operations:
...................................................................... OK.
..1285 10:33:33 (0) ** WMI GET VALUE operations:
................................................................... OK.
..1286 10:33:33 (0) ** WMI static instances retrieved:
............................................................. 0.
..1287 10:33:33 (0) ** WMI dynamic instances retrieved:
............................................................ 0.
..1288 10:33:33 (0) ** WMI instances request cancellations (to limit
performance impact): ......................... 0.
..1289 10:33:33 (0) **
..1290 10:33:33 (0) ** 5 error(s) 0x80040154 - (WBEM_UNKNOWN) This error code
is external to WMI.
..1291 10:33:33 (0) ** => This error is not a WMI error. This error is a
typical DCOM registration error.
..1292 10:33:33 (0) ** The registry information for DCOM to initialize a
DCOM object is missing or wrongly configured.
..1293 10:33:33 (0) ** => You can correct the DCOM configuration by:
..1294 10:33:33 (0) ** - Executing the 'Filename.EXE /RegServer' command.
..1295 10:33:33 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>'
command.
..1296 10:33:33 (0) ** Note: You can build a list of classes in relation
with their WMI provider and MOF file with WMIDiag.
Ken
Ramesh said:
Ken,
See if WMIDiag / repairing WMI helps
http://windowsxp.mvps.org/repairwmi.htm
Create a System Restore point first.
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting
http://www.winhelponline.com
Ramesh,
Unfortunately, that didn't do it either, even after reboot.
Any other thoughts?
Thanks for your interest.
Ken