Re: System Information problem
From: libs (libs_at_discussions.microsoft.com)
Date: 01/23/05
- Next message: Mark L. Ferguson: "Re: Long pause after connecting with modem"
- Previous message: Mark L. Ferguson: "Re: ERROR_NO_SYSTEM_RESOURCES during device driver installation"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 23 Jan 2005 03:55:01 -0800
I had the same problem as all the others above, and this solution worked well
for me.
"Wesley Vogel" wrote:
> 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:200D86CD-93EF-4759-BE85-7950FB1EE637@microsoft.com,
> Trkev <Trkev@discussions.microsoft.com> hunted and pecked:
> > I am also having this problem. I can't get any info about my system,
> > and I'm trying to locate some drivers that seem to have disappeared.
> > You say that the WMI may be corrupted, what can we do to resolve
> > that? Please be more specific. Thanks.
> >
> > "kltaylor" wrote:
> >
> >> I went to the link and followed the instructions. I still get the
> >> same message. I am running Windows XP Media Center Edition, Verison
> >> 2002, Service Pack 1, if that makes any difference.
> >>
> >> "Carey Frisch [MVP]" <mrxp2004@nospamyahoo.com> wrote in message
> >> news:u2guZFmdEHA.3864@TK2MSFTNGP10.phx.gbl...
> >>> Error Message: Windows Management Instrumentation (WMI) Might Be
> >>> Corrupted
> >>>
> >>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;319101&Product=winxp
> >>>
> >>> --
> >>> Carey Frisch
> >>> Microsoft MVP
> >>> Windows XP - Shell/User
> >>>
> >>> Be Smart! Protect your PC!
> >>> http://www.microsoft.com/security/protect/
> >>>
> >>> ------------------------------------------------------------------------
> --
> >>> ----------------
> >>>
> >>> "kltaylor" <kltaylor@insightbb.com> wrote in message:
> >>> news:a5wOc.198641$JR4.103315@attbi_s54...
> >>>
> >>>> When I try to run System Information I get a message "Can't
> >>>> Collect Information
> >>>> Cannot acess the Windows Manement Instrumentation software.
> >>>> Windows Management files may be moved or missing.
> >>>> How do I correct this ?
>
>
- Next message: Mark L. Ferguson: "Re: Long pause after connecting with modem"
- Previous message: Mark L. Ferguson: "Re: ERROR_NO_SYSTEM_RESOURCES during device driver installation"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
