WMI and msconfig32 problems

[Guest]

Hi all

I am having problems viewing systems informatio

Symptoms:

When I run msconfig32 I get in the right hand pain “Can’t Collect information – Access denied to WMI server on this computer. Have an administrator change your accessâ€. In the left pain the sub-items “hardware resources, components, software environment†all fields are blank. The sub-item “Internet Settings all the fields show “unknownâ€. However the sub-item “office 10 applications†(which are office xp stuff) all the fields are OK

Similarly when I try using “help and support tools†all fields are either blank or “unknownâ€

When I run WMI as a console and right click properties I get the following message:-

Failed to initialize all required WMI classe
Win32_Processor: WMI: Access denie
Win32_WMISettings: Successfu
Security information Successfu
Win32_OperatingSystem: WMI: Access denie

At this point I don’t have access to any tool bar directories and can only acticate the “cancel†tab

I have tried (among many other things) the following

Flushed the “repository†directory
Made sure I have administrative rights to all services and that all relevant services are running
Checked to make sure the “WMI console†is in the “author†mode
I have searched the knowledge base and the only thing that I can find that maybe an issue is hardware problems or problems with non-plug and play stuff

I have a stand alone computer (PIII 1ghz 526 ram) running win xp pro sp1 with all the latest downloads

Can anyone suggest something or point me in the right directio

Thank

 

[Wesley Vogel]

Go here:
http://www.kellys-korner-xp.com/xp_abc.htm

Click the "M"
Scroll down to:
Msinfo32 - System Information (Error or Missing)

 

[Guest]

Hi Wesley
Thanks for that - its a good site - however all the things they suggest i have tried - all i can figure out it is that my security configuration must be wrong or there is a problem with my hardware or software config which doesn't agree with winxp

Anyother suggestion would be appreciate

regards
peter

 

[Wesley Vogel]

peter,

More suggestions. ;-)

Windows XP reports that Windows Management Instrumentation (WMI) might be
corrupted?
http://www.jsifaq.com/SUBK/tip5200/rh5281.htm

[[You may receive any of the following error messages in Windows XP:
Unable to view network properties.
Windows cannot display the properties of connection. Windows Management
Instrumentation (WMI) might be corrupted.
Unable to view System Information (MSinfo32).

If you run Windows Management Instrumentation (WMI), wmimgmt.msc, you
receive:
Failed to connect to local computer due to WMI:Generic failure.

These errors will occur if the %SystemRoot%\System32\Wbem\Repository folder
is damaged.
To fix this problem:
1. Use the Start menu to right-click My Computer.
2. Press the Manage item.
3. Double-click Services and Applications in the left-hand pane.
4. Press Services to expand it.
5. Scroll to Windows Management Instrumentation in the right-hand pane and
right-click it.
6. Press Stop.
7. Use Windows Explorer to delete all the files in the
%SystemRoot%\System32\Wbem\Repository folder.
8. Shutdown and restart your computer. The Windows Management
Instrumentation service will start and the files will be re-created.]]
======================================

I had a problem with WMI, I also had a problem deleting
%SystemRoot%\System32\Wbem\Repository. I had to run Error Checking
(Chkdsk).
And then try to delete the file. C:\WINDOWS\System32\Wbem\Repository\FS.
------------------

Courtesy of Kelly T. @ http://www.kellys-korner.com/
[Windows Management Instrumentation - WinMgmt could not initialize the core
parts
Go to Start/Run/CMD and then run each of these hitting enter after each:

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

This may or may not repair the repository but will re-install wmi into the
registry.]
=====================

From http://www.kellys-korner-xp.com/xp_abc.htm

WMI

[[WMIPRVSE hosts the provider that sends your events on WinXP. On WinXP
providers are out of process from the actual WMI service. You can specify
the wbemConnectFlagUseMaxWait which will cause the timeout to be 2 minutes
instead of the default DCOM one which is up to 20 minutes. What may help is
to ping the remote machine first before attempting a ConnectServer.

WMI relies on DCOM for remoting which in turn uses RPC which then uses
TCP/IP, so there could be several reasons why it isn't connecting initially.
This is a known issue. Basically, when the provider calls MSI, it doesn't
necessarily cancel the initial request and attempts to finish it so
wmiprvse.exe will still show cpu usage.

To correct permission issues:

1 - In the Management Console\Services STOP WMI and set to manual.
2 - Go to the WMI repository %Windows%system32%wbem and delete the
repository.
3 -Set the WMI service back to Automatic
4 - From %Windows%system32%wbem run "wbemtest" and connect to your
namespace.
5 - Start/Run/Regedit and navigate to: Locate current
HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class. Open the class
key and right click on the sub key 0000 and select permissions and make sure
that the permissions for you [administrator] are "Full".]]
===========

 

[Guest]

Wesley Hi,
Thanks for your time u gave lots of suggestion which must have taken u sometime - so thanks a lot.

I only tried your last suggestion to change access permission (as i have tried all the others previously)

First i stopped wmi then deleted the repository then restarted wmi - i then ran "wbentest" and contect to name space "root/default" - i then ran regedit and found the following entries (as you can see there are no sub-items with "permission" - and the "class" item 4D36E96A.... is my hard disk controller):-

[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class]

[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}]

[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0000]

[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001]

[HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002]


Any more suggestions are appreciated - thanks,
Peter

peter,

More suggestions. ;-)

Windows XP reports that Windows Management Instrumentation (WMI) might be
corrupted?
http://www.jsifaq.com/SUBK/tip5200/rh5281.htm

[[You may receive any of the following error messages in Windows XP:
Unable to view network properties.
Windows cannot display the properties of connection. Windows Management
Instrumentation (WMI) might be corrupted.
Unable to view System Information (MSinfo32).

If you run Windows Management Instrumentation (WMI), wmimgmt.msc, you
receive:
Failed to connect to local computer due to WMI:Generic failure.

These errors will occur if the %SystemRoot%\System32\Wbem\Repository folder
is damaged.
To fix this problem:
1. Use the Start menu to right-click My Computer.
2. Press the Manage item.
3. Double-click Services and Applications in the left-hand pane.
4. Press Services to expand it.
5. Scroll to Windows Management Instrumentation in the right-hand pane and
right-click it.
6. Press Stop.
7. Use Windows Explorer to delete all the files in the
%SystemRoot%\System32\Wbem\Repository folder.
8. Shutdown and restart your computer. The Windows Management
Instrumentation service will start and the files will be re-created.]]
======================================

I had a problem with WMI, I also had a problem deleting
%SystemRoot%\System32\Wbem\Repository. I had to run Error Checking
(Chkdsk).
And then try to delete the file. C:\WINDOWS\System32\Wbem\Repository\FS.
------------------

Courtesy of Kelly T. @ http://www.kellys-korner.com/
[Windows Management Instrumentation - WinMgmt could not initialize the core
parts
Go to Start/Run/CMD and then run each of these hitting enter after each:

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

This may or may not repair the repository but will re-install wmi into the
registry.]
=====================

From http://www.kellys-korner-xp.com/xp_abc.htm

WMI

[[WMIPRVSE hosts the provider that sends your events on WinXP. On WinXP
providers are out of process from the actual WMI service. You can specify
the wbemConnectFlagUseMaxWait which will cause the timeout to be 2 minutes
instead of the default DCOM one which is up to 20 minutes. What may help is
to ping the remote machine first before attempting a ConnectServer.

WMI relies on DCOM for remoting which in turn uses RPC which then uses
TCP/IP, so there could be several reasons why it isn't connecting initially.
This is a known issue. Basically, when the provider calls MSI, it doesn't
necessarily cancel the initial request and attempts to finish it so
wmiprvse.exe will still show cpu usage.

To correct permission issues:

1 - In the Management Console\Services STOP WMI and set to manual.
2 - Go to the WMI repository %Windows%system32%wbem and delete the
repository.
3 -Set the WMI service back to Automatic
4 - From %Windows%system32%wbem run "wbemtest" and connect to your
namespace.
5 - Start/Run/Regedit and navigate to: Locate current
HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class. Open the class
key and right click on the sub key 0000 and select permissions and make sure
that the permissions for you [administrator] are "Full".]]
===========


--
Hope this helps. Let us know.
Wes

In

Hi Wesley,
Thanks for that - its a good site - however all the things they
suggest i have tried - all i can figure out it is that my security
configuration must be wrong or there is a problem with my hardware or
software config which doesn't agree with winxp.

Anyother suggestion would be appreciated

regards,
peter