Re: Windows XP WMI Reinstall

From: Ivan Brugiolo [MSFT] (ivanbrug_at_online.microsoft.com)
Date: 04/23/04 

Date: Fri, 23 Apr 2004 10:58:09 -0700

if the service has at least started, you should have its PID from
c:\>tlist -s | findstr /i winmgmt

The error below means pretty much that the server did not register with SCM,
or it crashed while servicing request for exposed CLSID.

If the procedure below did not fix it,
you must have compromised your machine pretty badly.
Re-Install the OS, since there has been too much alteration
of the default state to suggest meaningful recovery steps. 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Paul Jenkins" <citpaj@don't_want_spam.yahoo.ca> wrote in message
news:ey5JhwTKEHA.3728@TK2MSFTNGP12.phx.gbl...
> Scares me too :^)
>
> Anyway, when I try to connect to root\cimv2 I get an error dialog as
> follows:
>
> Error (window title)
> Number: 0x80080005
> Facility: Windows
> Description: Server execution failed
> DISMISS (button)
>
> Some of the errors or anomalies I referred to are:
>
> Please wait while WMIC is being installed.
> Parsing Mof File: C:\WINDOWS\System32\wbem\Cli.mof(Phase Error - 3)
> Compiler returned error 0x80080005
>
> Also, I couldn't get a PID for the winmgmts process because it's not
running
> (is it linked to the WMI server, that won't start?).
>
> Thanks.
>
> PJ
>
>
> "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
> news:OnD5XFNKEHA.2580@TK2MSFTNGP12.phx.gbl...
> > It scares me that you had "multiple errors".
> > The procedure below was refined after many individuals
> > had reported single problems in small areas.
> >
> > At the end of the steps, can you use wbemtest.exe to connect to
> > "root\default" ?
> >
> > -- 
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > Use of any included script samples are subject to the terms specified at
> > http://www.microsoft.com/info/cpyright.htm
> >
> >
> > "Paul Jenkins" <citpaj@don't_want_spam.yahoo.ca> wrote in message
> > news:O22yquMKEHA.3016@tk2msftngp13.phx.gbl...
> > > Ivan.
> > >
> > > I've completed the series of steps as outlined below and have a number
> of
> > > errors to report.  To make any sense of this for you I'd need to post
> > quite
> > > a large amount detail back here ... would you rather I do that or take
> > this
> > > off-line to e-mail and simply post the fix back to the group?  Thanks.
> > >
> > > PJ
> > >
> > >
> > > "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in
message
> > > news:eg4cXS3JEHA.2380@TK2MSFTNGP09.phx.gbl...
> > > > From a very  old post of mine in this same forum,
> > > > how to check why WinMmgt became un-usable and how to repair it.
> > > >
> > > > /////////////////////////////////////////////
> > > >
> > > > Try to remove, if they are there
> > > >
> > > >  HKLM\Software\Microsoft\OLE
> > > >    "EnableRemoteConnect"="Y"
> > > >    "LegacyAuthenticationLevel"=dword:00000001
> > > >   "LegacyImpersonationLevel"=dword:00000001
> > > >
> > > > Some legacy application from the Win9x era are known to create
> > > > those key that impair many DCOM functionality on the machine.
> > > >
> > > > check the following registry key
> > > > HKLM\System\Software\Microsoft\WBEM\CIMOM\AutoRecover MOFs
> > > > it is supposed to have a list of *.MOF and *.MFL files, and it MUST
> > begin
> > > > with cimwin32.mof
> > > > There are ISP connection kits and .NET Framework setups known to
> corrupt
> > > > this key.
> > > > Please delete it content if it appears to have few files or if it
> > appears
> > > > corrupt.
> > > >
> > > > check if in %windir%\system32\wbem there are about 40 MOF files.
> > > > There are certain applications known to delete them.
> > > > If you don't have them, please recover them from the CD of WinXP.
> > > > The complete list is found in %windir%\IFM\wbemoc.inf
> > > >
> > > >
> > > > Please check the following:
> > > > -1- that you system path has still %windir%\system32\wbem in it.
> > > > -2- that there are no wmiutils.dll and wbemcomn.dll in the system
path
> > > that
> > > > comes before the one in system32\wbem.
> > > >
> > > > c:\>for %i in ("wbemcomn.dll") do (echo %~$PATH:i)
> > > > c:\>for %i in ("wmiutils.dll") do (echo %~$PATH:i)
> > > >
> > > > check if the wbemutils.dll registered as a COM component comes from
> the
> > OS
> > > > or from Visual Studio and/or other development tools.
> > > > Make sure the OS Supplied one is used.
> > > >
> > > > enable versbose logging
> > > > HKLM\Software\Microsoft\WBEM\CIMOM:Logging(REG_SZ) = "2"
> > > > HKLM\Software\Microsoft\WBEM\CIMOM:Logging File Max Size (REG_SZ) =
> > > > "4000000"
> > > >
> > > > find the PID of the svchost.exe process running WinMgmt
> > > > HKLM\Software\Microsoft\WBEM\CIMOM:ProcessID (REG_DWORD) = XXX
> > > >
> > > > crosss check the pid
> > > > c:\>tlist -s | findstr /i winmgmt
> > > > it must be the same as above, if not, trust tlist.exe more than the
> > > registry
> > > > for the steps below.
> > > >
> > > > you can get "tlist .exe" and "kill.exe" (needed later)
> > > > from http://www.microsoft.com/ddk/debugging/installx86.asp
> > > >
> > > > c:\>sc config winmgmt start= disabled
> > > > c:\>kill -f XXX <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< pid obtained before
> > > > c:\>cd /D %windir%\system32\wbem
> > > > c:\WIN\system32\wbem>rmdir /s /q repository
> > > > c:\WIN\system32\wbem>rmdir /s /q Logs
> > > > c:\WIN\system32\wbem>mkdir Logs
> > > > c:\WIN\system32\wbem>for /R %i in (*.dll) do (regsvr32 /s %i)
> > > > c:\WIN\system32\wbem>regsvr32 /s fastprox.dll
> > > > c:\WIN\system32\wbem>for /R %i in (*.exe) do (%i -regserver)
> > <<<<<<<<<<<<<
> > > > this will open wbemtest and/or wmic.exe. Just close it
> > > > c:\WIN\system32\wbem>sc config winmgmt start= auto
> > > > c:\WIN\system32\wbem>regsvr32 wbemupgd.dll  <<<<<<<<<<<<<< this can
> take
> > > 30
> > > > seconds to 2 minutes
> > > > c:\WIN\system32\wbem>net start server && net start workstation &&
net
> > > start
> > > > AudioSrv && net start termservice
> > > >
> > > > after this, please start %windir%\system32\wbem\wbemtest.exe,
> > > > and connect to the root\cimv2 namespace.
> > > >
> > > > If something goes wrong, please read the logs under
> > > > %windir%\system32\wbem\Logs, just to see if there is something
> > obviousely
> > > > wrong there.
> > > >
> > > > After all of this is done, there might be misconfiguration problems
> > > > that have changed access permission to registry key and files for
the
> > > > NetworkService account.
> > > > The NetworkService account is the one running one of the Provider
> Host.
> > > > To test if this can be the problem, you ca add NetworkService to the
> > > > administrators group
> > > > c:\>net localgroup administrators NetworkService /ADD
> > > > Please remember to remove it as soon as the misconfiguration problem
> > have
> > > > been identified
> > > >
> > > >
> > > >
> > > > -- 
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > Use of any included script samples are subject to the terms
specified
> at
> > > > http://www.microsoft.com/info/cpyright.htm
> > > >
> > > >
> > > > "Paul Jenkins" <citpaj@don't_want_spam.yahoo.ca> wrote in message
> > > > news:OYf71z0JEHA.2604@tk2msftngp13.phx.gbl...
> > > > > Also F.Y.I., the Event Log Service is started cleanly (I've seen
> other
> > > > info
> > > > > on the web referring to WMI problems if Event Log Service isn't
> > > started).
> > > > >
> > > > > PJ
> > > > >
> > > > > "Paul Jenkins" <citpaj@don't_want_spam.yahoo.ca> wrote in message
> > > > > news:ucQiRw0JEHA.2776@TK2MSFTNGP12.phx.gbl...
> > > > > > WMI is set to automatic startup.  It doesn't start at boot time.
> > > Nothing
> > > > > in
> > > > > > the SYSTEM event log.
> > > > > >
> > > > > > When I try to manually start WMI I get an rather generic error
> > dialog
> > > > > > stating "The Windows Management Instrumentation service on Local
> > > > Computer
> > > > > > started and then stopped. Some services stop automatically if
they
> > > have
> > > > no
> > > > > > work to do, for example, the Performance Logs and Alerts
service."
> > > > > >
> > > > > > Also F.Y.I. I tried to install the newest WMI Tools and MSI
> > installer
> > > > > > errored leaving the following in the APPLICATION event log:
> > > > > >
> > > > > > "Product: WMI Tools -- Error 1722. There is a problem with this
> > > Windows
> > > > > > Installer package. A program run as part of the setup did not
> finish
> > > as
> > > > > > expected. Contact your support personnel or package vendor.
Action
> > > > > > CompileMof1, location: C:\Program Files\WMI Tools\DoMofcmp.exe,
> > > command:
> > > > > /s
> > > > > > "C:\Program Files\WMI Tools\EViewer.mof" "
> > > > > >
> > > > > > PJ
> > > > > >
> > > > > > "Chung-Wei Foong [MSFT]" <chungwf@online.microsoft.com> wrote in
> > > message
> > > > > > news:uUAaJXyJEHA.2464@TK2MSFTNGP10.phx.gbl...
> > > > > > > Is the WMI service being disabled on the machine? What is the
> > error
> > > > code
> > > > > > > when you try to start it?
> > > > > > >
> > > > > > > -- 
> > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > Use of any included script samples are subject to the terms
> > > specified
> > > > at
> > > > > > > http://www.microsoft.com/info/cpyright.htm
> > > > > > >
> > > > > > >
> > > > > > > "Paul Jenkins" <citpaj@don't_want_spam.yahoo.ca> wrote in
> message
> > > > > > > news:ekDcDnwJEHA.2884@TK2MSFTNGP12.phx.gbl...
> > > > > > > > Hi.
> > > > > > > >
> > > > > > > > The WMI service won't start on my XP system.  Can anyone
tell
> me
> > > iof
> > > > > > > there's
> > > > > > > > a repair or reinstall option ?  Thanks.
> > > > > > > >
> > > > > > > > PJ
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>