Re: WMI and msconfig32 problems
From: Aussie Pete (Pete_at_discussions.microsoft.com)
Date: 06/12/04
- Next message: louis: "MVPS Tip on Blocking Unwanted Popups"
- Previous message: sfactor_at_pcfactor.com: "No login user icons at startup"
- In reply to: Wesley Vogel: "Re: WMI and msconfig32 problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 12 Jun 2004 04:46:01 -0700
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
"Wesley Vogel" wrote:
> 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 news:F88832AE-9D37-42CE-B258-8F4A66F08416@microsoft.com,
> aussie pete <anonymous@discussions.microsoft.com> hunted and pecked:
> > 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
>
>
- Next message: louis: "MVPS Tip on Blocking Unwanted Popups"
- Previous message: sfactor_at_pcfactor.com: "No login user icons at startup"
- In reply to: Wesley Vogel: "Re: WMI and msconfig32 problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
