WMI diagnostics

J

J Lunis

Posted to windowsxp.general 12/22 without response.
----------------------------
Before I start, two additional comments.
1) I am receiving Event ID 4610 which suggests a reinstall of COM+
2) Control Panel > Network Connections > Local Area Network >
Client for Microsoft Network > Advanced
reads in part "WMI information may be corrupted" and "Use System Restore."

I can not find how to reinstall COM+
I can not find how System Restore will affect (notice I didn't say
'impact')XP settings or how nuch work it will cause me.

Nonetheless, my WMI diagnostics question follows.
---------------------------------------------------

Win XP SR2
Ran WMI diagnostics this morning. I think I understand it to say I have
5 errors. Problem is, I do not understand what it is telling me. I
would appreciate any advice that can help. My comments will be
proceeded by '+++++++++++++++'
-----------------------------------

..1249 08:35:06 (0) ** WMI dynamic instances retrieved:
............................................................ 0.
..1250 08:35:06 (0) ** WMI instances request cancellations (to limit
performance impact): ......................... 0.
..1251 08:35:06 (0) **
..1252 08:35:06 (0) ** 5 error(s) 0x80040154 - (WBEM_UNKNOWN) This error
code is external to WMI.
..1253 08:35:06 (0) ** => This error is not a WMI error. This error is a
typical DCOM registration error.
..1254 08:35:06 (0) ** The registry information for DCOM to initialize
a DCOM object is missing or wrongly configured.
..1255 08:35:06 (0) ** => You can correct the DCOM configuration by:
..1256 08:35:06 (0) ** - Executing the 'Filename.EXE /RegServer' command.
+++++++++++++++++ what is 'Filename.EXE'

..1257 08:35:06 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>'
command.
+++++++++++++++++ what is 'provider.DLL'

..1258 08:35:06 (0) ** Note: You can build a list of classes in
relation with their WMI provider and MOF file with WMIDiag.
..1259 08:35:06 (0) ** (This list can be built on a similar and
working WMI Windows installation)
..1260 08:35:06 (0) ** The following command line must be used:
..1261 08:35:06 (0) ** e.g. 'WMIDiag CorrelateClassAndProvider'
+++++++++++++++++ enter 'WMIDiag CorrelateClassAndProvider' in cmd screen?

..1262 08:35:06 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL
from 'C:\WINDOWS\SYSTEM32\WBEM\'
..1263 08:35:06 (0) ** may not solve the problem as the DLL
supporting the WMI class(es)
..1264 08:35:06 (0) ** can be located in a different folder.
..1265 08:35:06 (0) ** You must refer to the class name to
determine the software delivering the related DLL.
++++++++++++++++++ I am completely lost here. Refer to WHAT Class
name? Where is the list?

..1266 08:35:06 (0) ** - Re-installing the software.
..1267 08:35:06 (0) **
..1268 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1269 08:35:06 (0) ** WMI Registry key setup:
..................................................................... OK.
..1270 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1271 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1272 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1273 08:35:06 (0) ** --------------------------------------- WMI
REPORT: END --------------------------------------------
..1274 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1275 08:35:06 (0) **
..1276 08:35:06 (0) ** ERROR: WMIDiag detected issues that could prevent
WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG'
for details.
..1277 08:35:06 (0) **
..1278 08:35:06 (0) ** WMIDiag executed in 33 second(s).
..1279 08:35:06 (3)
..1280 08:35:06 (3) 1.10,12/22/2006,8:34:59 AM,12/15/2006 2:26:28
PM,False,False,False,32-bit,x86 Family 15 Model 2 Stepping 9
GenuineIntel,5.1,2600,Service Pack 2,Windows XP - Service pack 2 -
32-bit,XP__.CLI.SP2.32,00000409,STUDY,STUDY\USER,False,Root, ,0,0,0,0,
,5,54275,5,54275,0, ,
,0,2,0,0,0,0,0,0,0,0,N/A,0,5,0,0,0,0,0,0,0,0,0,0,0,
,0,0,0,0,18,0,12/22/2006,8:35:06
AM,0,0,0,33,24,9,1,WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG,C:\DOCUMENTS
AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG
..1281 08:35:06 (3)
..1282 08:35:06 (0) ** WMIDiag v1.10 ended on Friday, December 22, 2006
at 08:35 (W:24 E:9 S:1).
..1283 08:35:06 (0) ** CSV file "C:\DOCUMENTS AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33-STATISTICS.CSV"
closed.
..1284 08:35:06 (0) ** LOG file "C:\DOCUMENTS AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG"
closed.
 
R

Ramesh, MS-MVP

Hi Lunis,

It could be a DCOM issue, as the log suggests. However, try the method here from Philip Nunn [MSFT]

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/50730a873f3454d0?hl=en&
(Rebuilding the WMI repository)

and this from Ivan Brugiolo [MSFT] :

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/739aad70dd09e173?hl=en&
(Read the caveats mentioned)

<quote>
Some legacy application from the Win9x era are known to create
those key that impair many DCOM functionality on the machine.
</quote>

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


Posted to windowsxp.general 12/22 without response.
----------------------------
Before I start, two additional comments.
1) I am receiving Event ID 4610 which suggests a reinstall of COM+
2) Control Panel > Network Connections > Local Area Network >
Client for Microsoft Network > Advanced
reads in part "WMI information may be corrupted" and "Use System Restore."

I can not find how to reinstall COM+
I can not find how System Restore will affect (notice I didn't say
'impact')XP settings or how nuch work it will cause me.

Nonetheless, my WMI diagnostics question follows.
---------------------------------------------------

Win XP SR2
Ran WMI diagnostics this morning. I think I understand it to say I have
5 errors. Problem is, I do not understand what it is telling me. I
would appreciate any advice that can help. My comments will be
proceeded by '+++++++++++++++'
-----------------------------------

..1249 08:35:06 (0) ** WMI dynamic instances retrieved:
............................................................ 0.
..1250 08:35:06 (0) ** WMI instances request cancellations (to limit
performance impact): ......................... 0.
..1251 08:35:06 (0) **
..1252 08:35:06 (0) ** 5 error(s) 0x80040154 - (WBEM_UNKNOWN) This error
code is external to WMI.
..1253 08:35:06 (0) ** => This error is not a WMI error. This error is a
typical DCOM registration error.
..1254 08:35:06 (0) ** The registry information for DCOM to initialize
a DCOM object is missing or wrongly configured.
..1255 08:35:06 (0) ** => You can correct the DCOM configuration by:
..1256 08:35:06 (0) ** - Executing the 'Filename.EXE /RegServer' command.
+++++++++++++++++ what is 'Filename.EXE'

..1257 08:35:06 (0) ** - Executing the 'REGSVR32.EXE <Provider.DLL>'
command.
+++++++++++++++++ what is 'provider.DLL'

..1258 08:35:06 (0) ** Note: You can build a list of classes in
relation with their WMI provider and MOF file with WMIDiag.
..1259 08:35:06 (0) ** (This list can be built on a similar and
working WMI Windows installation)
..1260 08:35:06 (0) ** The following command line must be used:
..1261 08:35:06 (0) ** e.g. 'WMIDiag CorrelateClassAndProvider'
+++++++++++++++++ enter 'WMIDiag CorrelateClassAndProvider' in cmd screen?

..1262 08:35:06 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL
from 'C:\WINDOWS\SYSTEM32\WBEM\'
..1263 08:35:06 (0) ** may not solve the problem as the DLL
supporting the WMI class(es)
..1264 08:35:06 (0) ** can be located in a different folder.
..1265 08:35:06 (0) ** You must refer to the class name to
determine the software delivering the related DLL.
++++++++++++++++++ I am completely lost here. Refer to WHAT Class
name? Where is the list?

..1266 08:35:06 (0) ** - Re-installing the software.
..1267 08:35:06 (0) **
..1268 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1269 08:35:06 (0) ** WMI Registry key setup:
..................................................................... OK.
..1270 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1271 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1272 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1273 08:35:06 (0) ** --------------------------------------- WMI
REPORT: END --------------------------------------------
..1274 08:35:06 (0) **
----------------------------------------------------------------------------------------------------
..1275 08:35:06 (0) **
..1276 08:35:06 (0) ** ERROR: WMIDiag detected issues that could prevent
WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG'
for details.
..1277 08:35:06 (0) **
..1278 08:35:06 (0) ** WMIDiag executed in 33 second(s).
..1279 08:35:06 (3)
..1280 08:35:06 (3) 1.10,12/22/2006,8:34:59 AM,12/15/2006 2:26:28
PM,False,False,False,32-bit,x86 Family 15 Model 2 Stepping 9
GenuineIntel,5.1,2600,Service Pack 2,Windows XP - Service pack 2 -
32-bit,XP__.CLI.SP2.32,00000409,STUDY,STUDY\USER,False,Root, ,0,0,0,0,
,5,54275,5,54275,0, ,
,0,2,0,0,0,0,0,0,0,0,N/A,0,5,0,0,0,0,0,0,0,0,0,0,0,
,0,0,0,0,18,0,12/22/2006,8:35:06
AM,0,0,0,33,24,9,1,WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG,C:\DOCUMENTS
AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG
..1281 08:35:06 (3)
..1282 08:35:06 (0) ** WMIDiag v1.10 ended on Friday, December 22, 2006
at 08:35 (W:24 E:9 S:1).
..1283 08:35:06 (0) ** CSV file "C:\DOCUMENTS AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33-STATISTICS.CSV"
closed.
..1284 08:35:06 (0) ** LOG file "C:\DOCUMENTS AND SETTINGS\USER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_STUDY_2006.12.22_08.34.33.LOG"
closed.
 
J

J Lunis

Ramesh,
thanks for the reply.
--------------------------
Went to the 'Nunn' link and followed the cmd prompt. Rebooted.
I see no where the winmgmt is restarted. Normal?
Event Viewer - I get an error ASPNET.MOF failed to load.
---------------------------
Went to the 'Ivan' link.
I am directed to
HKLM\System\Software\Microsoft\WBEM\CIMOM\AutoRecover MOFs.
I have no such folder as 'HKLM\System\Software.' Is this a bad sign to
have no 'Software' folder?
The article states I should have 'about 40' MOFs. I have 37. Close enough?
---------------------------
Finally, Event Viewer. I have 3 errors.
All are 'The server did not register' with 3 different servers(?)
03DC0FA4F493
0060081ED811
00AA005FF586
Related?

=============================
 
J

J Lunis

BONUS: Just rebooted again.
On reboot, XP found a new device - Residential Gateway. First time I
have ever seen this. But once I closed it I can't find it again so I
can give no more info. Any idea what this is?
 
F

frodo

J Lunis said:
BONUS: Just rebooted again.
On reboot, XP found a new device - Residential Gateway. First time I
have ever seen this. But once I closed it I can't find it again so I
can give no more info. Any idea what this is?

this will show up if you have SSDP Discovery running; it's your NAT
router. Don't worry about it. [If you're SURE you don't need it, you can
turn off SSDP, both the XP service and your router's support of it].

As for fixing WMI, whenever I have this sort of issue I run this command
file:

----cut----
cd /d %windir%\system32
regsvr32 /n /I userenv.dll
cd wbem
mofcomp scersop.mof
gpupdate /force
-----cut----

cut-paste to notepad, save as xxx.CMD, then right click the saved file and
choose OPEN to run the cmd. A pop-up will appear that says "regsrv done"
(or something like that), click ok and the rest of the lines will run.
after that WMI should be fixed. [this seq rebuilds the wmi repository].

if this does not fix things completely, I noticed one of the reported
errros had to do w/ .Net. You might want to reinstall it.
 
J

J Lunis

Thanks for the quick response.
Network Neighborhood/Residential Gateway - disappeared on reboot.
-----------
----cut----
cd /d %windir%\system32
regsvr32 /n /I userenv.dll
cd wbem
mofcomp scersop.mof
gpupdate /force
-----cut----
On running the file, I get
'DLLInstall in userenv.dll failed.
Return code was: 0x80040154'

J Lunis said:
BONUS: Just rebooted again.
On reboot, XP found a new device - Residential Gateway. First time I
have ever seen this. But once I closed it I can't find it again so I
can give no more info. Any idea what this is?

this will show up if you have SSDP Discovery running; it's your NAT
router. Don't worry about it. [If you're SURE you don't need it, you can
turn off SSDP, both the XP service and your router's support of it].

As for fixing WMI, whenever I have this sort of issue I run this command
file:

----cut----
cd /d %windir%\system32
regsvr32 /n /I userenv.dll
cd wbem
mofcomp scersop.mof
gpupdate /force
-----cut----

cut-paste to notepad, save as xxx.CMD, then right click the saved file and
choose OPEN to run the cmd. A pop-up will appear that says "regsrv done"
(or something like that), click ok and the rest of the lines will run.
after that WMI should be fixed. [this seq rebuilds the wmi repository].

if this does not fix things completely, I noticed one of the reported
errros had to do w/ .Net. You might want to reinstall it.
 
R

Ramesh, MS-MVP

Lunis,

Did not notice it. To start the service use "net start winmgmt" or simply restart Windows after rebuilding the repository.

Again here is a mistake in the link. He really meant this branch:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


Ramesh,
thanks for the reply.
--------------------------
Went to the 'Nunn' link and followed the cmd prompt. Rebooted.
I see no where the winmgmt is restarted. Normal?
Event Viewer - I get an error ASPNET.MOF failed to load.
---------------------------
Went to the 'Ivan' link.
I am directed to
HKLM\System\Software\Microsoft\WBEM\CIMOM\AutoRecover MOFs.
I have no such folder as 'HKLM\System\Software.' Is this a bad sign to
have no 'Software' folder?
The article states I should have 'about 40' MOFs. I have 37. Close enough?
---------------------------
Finally, Event Viewer. I have 3 errors.
All are 'The server did not register' with 3 different servers(?)
03DC0FA4F493
0060081ED811
00AA005FF586
Related?

=============================
Ramesh said:
Hi Lunis,

It could be a DCOM issue, as the log suggests. However, try the method here from Philip Nunn [MSFT]

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/50730a873f3454d0?hl=en&
(Rebuilding the WMI repository)

and this from Ivan Brugiolo [MSFT] :

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/739aad70dd09e173?hl=en&
(Read the caveats mentioned)

<quote>
Some legacy application from the Win9x era are known to create
those key that impair many DCOM functionality on the machine.
</quote>
 
J

J Lunis

Ramesh said:
Hi Lunis,

It could be a DCOM issue, as the log suggests. However, try the method here from Philip Nunn [MSFT]

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/50730a873f3454d0?hl=en&
(Rebuilding the WMI repository)

and this from Ivan Brugiolo [MSFT] :

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/739aad70dd09e173?hl=en&
(Read the caveats mentioned)

<quote>
Some legacy application from the Win9x era are known to create
those key that impair many DCOM functionality on the machine.
</quote>
Went to Ivan's site. A few questions.
The list contains 38 MOFs. I have only 33 in my WBEM folder. Normal?
I have no such IFM folder
wbemoc.inf exists only in I386 folder.COntains a list of 28 MOFs.
 
R

Ramesh, MS-MVP

It's actually %windir%\INF folder.

And if some of the .mof files are missing, you could rebuild them using the "Comprehensive rebuild method" listed in this article:

Repairing and re-registering the WMI:
http://windowsxp.mvps.org/repairwmi.htm

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


J Lunis said:
Hi Lunis,

It could be a DCOM issue, as the log suggests. However, try the method here from Philip Nunn [MSFT]

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/50730a873f3454d0?hl=en&
(Rebuilding the WMI repository)

and this from Ivan Brugiolo [MSFT] :

http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/739aad70dd09e173?hl=en&
(Read the caveats mentioned)

<quote>
Some legacy application from the Win9x era are known to create
those key that impair many DCOM functionality on the machine.
</quote>
Went to Ivan's site. A few questions.
The list contains 38 MOFs. I have only 33 in my WBEM folder. Normal?
I have no such IFM folder
wbemoc.inf exists only in I386 folder.COntains a list of 28 MOFs.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top