FAQWindows-Expert.com Forum Index  •   FAQFAQ  •  SearchSearch
Windows-Expert.com
Find Windows Problems and Solutions
 
Windows Management Instrumentation: wmic' is not recognized.
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    Windows-Expert.com Forum Index -> Windows XP General
View previous topic :: View next topic  
Author Message
Tsunhin John Wong
Guest





PostPosted: Thu Sep 11, 2008 12:47 am    Post subject: Windows Management Instrumentation: wmic' is not recognized. Reply with quote

Hi all,

I am using Windows XP Pro Version 2002 SP2.
When I type "wmic" in command prompt, I get the following error
message:

'wmic' is not recognized as an internal or external command,
operable program or batch file.


After doing a search, I found wmic.exe in:
1.
C:\WINDOWS\ServicePackFiles\i386
2.
C:\WINDOWS\system32\dllcache

And when I try to run "C:\WINDOWS\ServicePackFiles\i386\wmic"
or
"C:\WINDOWS\system32\dllcache\wmic"
I get the following error message:

Please wait while WMIC compiles updated MOF files.
Parsing Mof File: C:\WINDOWS\system32\wbem\Cli.mof(Phase Error - 2)
Compiler returned error 0x8004401e

Please help me to get my WMI Tools back to service, thanks a lot!

- J
Back to top
Tsunhin John Wong
Guest





PostPosted: Thu Sep 11, 2008 1:04 am    Post subject: Re: Windows Management Instrumentation: wmic' is not recogni Reply with quote

WMI service is running, and below is the report of WMI Diagnostic
script.
In summary, there are a few errors (but the wmic.exe is simply not in
the wbem directory as I have written in the above post).
20062 19:52:09 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE'
DOES NOT match corresponding expected trustee rights (Actual->Default)
20088 19:52:09 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES
NOT match corresponding expected trustee rights (Actual->Default)
20114 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
20137 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
20156 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
20198 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
20179 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
20221 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
20245 19:52:09 (1) !! ERROR: Overall DCOM security
status: ................................................................................
ERROR!
20246 19:52:09 (1) !! ERROR: Overall WMI security
status: .................................................................................
ERROR!
20288 19:52:09 (1) !! ERROR: Unexpected registry key value:
20289 19:52:09 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM
\WMISetup (REG_SZ) -> 1
20290 19:52:09 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM
\WMISetup (REG_SZ) -> 0
20291 19:52:09 (0) ** From the command line, the registry
configuration can be corrected with the following command:
20292 19:52:09 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft
\WBEM\CIMOM" /v "WMISetup" /t "REG_SZ" /d "0" /f'

Full output of the report is below
Please suggest the way to get wmic.exe working, thanks a lot!



19965 19:52:09 (0) ** WMIDiag v2.0 started on Wednesday, September 10,
2008 at 19:49.
19966 19:52:09 (0) **
19967 19:52:09 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
19968 19:52:09 (0) **
19969 19:52:09 (0) ** This script is not supported under any Microsoft
standard support program or service.
19970 19:52:09 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
19971 19:52:09 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
19972 19:52:09 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
19973 19:52:09 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
19974 19:52:09 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
19975 19:52:09 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
19976 19:52:09 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
19977 19:52:09 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
19978 19:52:09 (0) ** of the possibility of such damages.
19979 19:52:09 (0) **
19980 19:52:09 (0) **
19981 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
19982 19:52:09 (0) **
----------------------------------------------------- WMI REPORT:
BEGIN ----------------------------------------------------------
19983 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
19984 19:52:09 (0) **
19985 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
19986 19:52:09 (0) ** Windows XP - Service pack 2 - 32-bit (2600) -
User '_MYWINUSERNAMEW\_MYWINUSERNAME' on computer '_MYWINUSERNAMEW'.
19987 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
19988 19:52:09 (0) ** INFO:
Environment: ..................................................................................................
1 ITEM(S)!
19989 19:52:09 (0) ** INFO: => 4 incorrect shutdown(s) detected on:
19990 19:52:09 (0) ** - Shutdown on 04 September 2008
11:06:32 (GMT+4).
19991 19:52:09 (0) ** - Shutdown on 06 September 2008
04:15:43 (GMT+4).
19992 19:52:09 (0) ** - Shutdown on 06 September 2008
22:51:24 (GMT+4).
19993 19:52:09 (0) ** - Shutdown on 08 September 2008
16:13:35 (GMT+4).
19994 19:52:09 (0) **
19995 19:52:09 (0) ** System
drive: .......................................................................................................
C: (Disk #1 Partition #0).
19996 19:52:09 (0) ** Drive
type: .........................................................................................................
IDE (HTS721010G9SA00).
19997 19:52:09 (0) ** There are no missing WMI system
files: ..............................................................................
OK.
19998 19:52:09 (0) ** There are no missing WMI repository
files: ..........................................................................
OK.
19999 19:52:09 (0) ** WMI repository
state: ...............................................................................................
NOT TESTED.
20000 19:52:09 (0) ** BEFORE running WMIDiag:
20001 19:52:09 (0) ** The WMI repository has a size
of: ...................................................................................
7 MB.
20002 19:52:09 (0) ** - Disk free space on
'C:': ..........................................................................................
19024 MB.
20003 19:52:09 (0) ** - INDEX.BTR, 1261568
bytes, 9/10/2008 4:54:57 PM
20004 19:52:09 (0) ** - INDEX.MAP, 660
bytes, 9/10/2008 7:38:49 PM
20005 19:52:09 (0) ** - MAPPING.VER, 4
bytes, 9/10/2008 7:38:49 PM
20006 19:52:09 (0) ** - MAPPING1.MAP, 3616
bytes, 9/10/2008 7:38:49 PM
20007 19:52:09 (0) ** - MAPPING2.MAP, 3616
bytes, 9/10/2008 7:32:14 PM
20008 19:52:09 (0) ** - OBJECTS.DATA, 5980160
bytes, 9/10/2008 4:54:57 PM
20009 19:52:09 (0) ** - OBJECTS.MAP, 2964
bytes, 9/10/2008 7:38:49 PM
20010 19:52:09 (0) ** AFTER running WMIDiag:
20011 19:52:09 (0) ** The WMI repository has a size
of: ...................................................................................
7 MB.
20012 19:52:09 (0) ** - Disk free space on
'C:': ..........................................................................................
19024 MB.
20013 19:52:09 (0) ** - INDEX.BTR, 1261568
bytes, 9/10/2008 4:54:57 PM
20014 19:52:09 (0) ** - INDEX.MAP, 660
bytes, 9/10/2008 7:38:49 PM
20015 19:52:09 (0) ** - MAPPING.VER, 4
bytes, 9/10/2008 7:38:49 PM
20016 19:52:09 (0) ** - MAPPING1.MAP, 3616
bytes, 9/10/2008 7:38:49 PM
20017 19:52:09 (0) ** - MAPPING2.MAP, 3616
bytes, 9/10/2008 7:32:14 PM
20018 19:52:09 (0) ** - OBJECTS.DATA, 5980160
bytes, 9/10/2008 4:54:57 PM
20019 19:52:09 (0) ** - OBJECTS.MAP, 2964
bytes, 9/10/2008 7:38:49 PM
20020 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20021 19:52:09 (0) ** INFO: Windows Firewall
status: ......................................................................................
ENABLED.
20022 19:52:09 (0) ** Windows Firewall
Profile: ...........................................................................................
STANDARD.
20023 19:52:09 (0) ** Windows Firewall 'RemoteAdmin'
status: ..............................................................................
DISABLED.
20024 19:52:09 (0) ** => This will prevent any WMI remote connectivity
to this machine.
20025 19:52:09 (0) ** - You can adjust the configuration by
executing the following command:
20026 19:52:09 (0) ** i.e. 'NETSH.EXE FIREWALL SET SERVICE
REMOTEADMIN ENABLE SUBNET'
20027 19:52:09 (0) **
20028 19:52:09 (0) ** Windows Firewall application exception for
'UNSECAPP.EXE': ..........................................................
MISSING.
20029 19:52:09 (0) ** => This will prevent any script and MMC
application asynchronous callbacks to this machine.
20030 19:52:09 (0) ** - You can adjust the configuration by
executing the following command:
20031 19:52:09 (0) ** i.e. 'NETSH.EXE FIREWALL SET ALLOWEDPROGRAM C:
\WINDOWS\SYSTEM32\WBEM\UNSECAPP.EXE WMICALLBACKS ENABLE'
20032 19:52:09 (0) **
20033 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20034 19:52:09 (0) ** DCOM
Status: ........................................................................................................
OK.
20035 19:52:09 (0) ** WMI registry
setup: .................................................................................................
OK.
20036 19:52:09 (0) ** INFO: WMI service has
dependents: ...................................................................................
2 SERVICE(S)!
20037 19:52:09 (0) ** - Security Center (WSCSVC,
StartMode='Automatic')
20038 19:52:09 (0) ** - Windows Firewall/Internet Connection Sharing
(ICS) (SHAREDACCESS, StartMode='Automatic')
20039 19:52:09 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
20040 19:52:09 (0) ** Note: If the service is marked with (*), it
means that the service/application uses WMI but
20041 19:52:09 (0) ** there is no hard dependency on WMI.
However, if the WMI service is stopped,
20042 19:52:09 (0) ** this can prevent the service/
application to work as expected.
20043 19:52:09 (0) **
20044 19:52:09 (0) ** RPCSS
service: ......................................................................................................
OK (Already started).
20045 19:52:09 (0) ** WINMGMT
service: ....................................................................................................
OK (Already started).
20046 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20047 19:52:09 (0) ** WMI service DCOM
setup: .............................................................................................
OK.
20048 19:52:09 (2) !! WARNING: WMI DCOM components registration is
missing for the following EXE/
DLLs: .................................... 2 WARNING(S)!
20049 19:52:09 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIDCPRV.DLL (\CLSID
\{4CFC7932-0F9D-4BEF-9C32-8EA2A6B56FCB}\InProcServer32)
20050 19:52:09 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIDCPRV.DLL (\CLSID\
{F5F75737-2843-4F22-933D-C76A97CDA62F}\InProcServer32)
20051 19:52:09 (0) ** => WMI System components are not properly
registered as COM objects, which could make WMI to
20052 19:52:09 (0) ** fail depending on the operation requested.
20053 19:52:09 (0) ** => For a .DLL, you can correct the DCOM
configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
20054 19:52:09 (0) **
20055 19:52:09 (0) ** WMI ProgID
registrations: ...........................................................................................
OK.
20056 19:52:09 (0) ** WMI provider DCOM
registrations: ....................................................................................
OK.
20057 19:52:09 (0) ** WMI provider CIM
registrations: .....................................................................................
OK.
20058 19:52:09 (0) ** WMI provider
CLSIDs: ................................................................................................
OK.
20059 19:52:09 (0) ** WMI providers EXE/DLL
availability: .................................................................................
OK.
20060 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20061 19:52:09 (0) ** DCOM security for 'My Computer' (Launch &
Activation Permissions/Edit
Default): ..................................... MODIFIED.
20062 19:52:09 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE'
DOES NOT match corresponding expected trustee rights (Actual->Default)
20063 19:52:09 (0) ** - ACTUAL ACE:
20064 19:52:09 (0) ** ACEType: &h0
20065 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20066 19:52:09 (0) ** ACEFlags: &h0
20067 19:52:09 (0) ** ACEMask: &hB
20068 19:52:09 (0) ** DCOM_RIGHT_EXECUTE
20069 19:52:09 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
20070 19:52:09 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
20071 19:52:09 (0) ** - EXPECTED ACE:
20072 19:52:09 (0) ** ACEType: &h0
20073 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20074 19:52:09 (0) ** ACEFlags: &h0
20075 19:52:09 (0) ** ACEMask: &h1F
20076 19:52:09 (0) ** DCOM_RIGHT_EXECUTE
20077 19:52:09 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
20078 19:52:09 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
20079 19:52:09 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
20080 19:52:09 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
20081 19:52:09 (0) **
20082 19:52:09 (0) ** => The actual ACE has the right(s) '&h14
DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
20083 19:52:09 (0) ** This will cause some operations to fail!
20084 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the removed right.
20085 19:52:09 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
20086 19:52:09 (0) **
20087 19:52:09 (0) ** DCOM security for 'My Computer' (Launch &
Activation Permissions/Edit
Default): ..................................... MODIFIED.
20088 19:52:09 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES
NOT match corresponding expected trustee rights (Actual->Default)
20089 19:52:09 (0) ** - ACTUAL ACE:
20090 19:52:09 (0) ** ACEType: &h0
20091 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20092 19:52:09 (0) ** ACEFlags: &h0
20093 19:52:09 (0) ** ACEMask: &hB
20094 19:52:09 (0) ** DCOM_RIGHT_EXECUTE
20095 19:52:09 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
20096 19:52:09 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
20097 19:52:09 (0) ** - EXPECTED ACE:
20098 19:52:09 (0) ** ACEType: &h0
20099 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20100 19:52:09 (0) ** ACEFlags: &h0
20101 19:52:09 (0) ** ACEMask: &h1F
20102 19:52:09 (0) ** DCOM_RIGHT_EXECUTE
20103 19:52:09 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
20104 19:52:09 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
20105 19:52:09 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
20106 19:52:09 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
20107 19:52:09 (0) **
20108 19:52:09 (0) ** => The actual ACE has the right(s) '&h14
DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
20109 19:52:09 (0) ** This will cause some operations to fail!
20110 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the removed right.
20111 19:52:09 (0) ** For DCOM objects, this can be done with
'DCOMCNFG.EXE'.
20112 19:52:09 (0) **
20113 19:52:09 (0) ** WMI namespace security for 'ROOT/
RSOP': .............................................................................
MODIFIED.
20114 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
20115 19:52:09 (0) ** - REMOVED ACE:
20116 19:52:09 (0) ** ACEType: &h0
20117 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20118 19:52:09 (0) ** ACEFlags: &h12
20119 19:52:09 (0) ** CONTAINER_INHERIT_ACE
20120 19:52:09 (0) ** INHERITED_ACE
20121 19:52:09 (0) ** ACEMask: &h6003F
20122 19:52:09 (0) ** WBEM_ENABLE
20123 19:52:09 (0) ** WBEM_METHOD_EXECUTE
20124 19:52:09 (0) ** WBEM_FULL_WRITE_REP
20125 19:52:09 (0) ** WBEM_PARTIAL_WRITE_REP
20126 19:52:09 (0) ** WBEM_WRITE_PROVIDER
20127 19:52:09 (0) ** WBEM_REMOTE_ACCESS
20128 19:52:09 (0) ** WBEM_WRITE_DAC
20129 19:52:09 (0) ** WBEM_READ_CONTROL
20130 19:52:09 (0) **
20131 19:52:09 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
20132 19:52:09 (0) ** Removing default security will cause some
operations to fail!
20133 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the ACE.
20134 19:52:09 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
20135 19:52:09 (0) **
20136 19:52:09 (0) ** WMI namespace security for 'ROOT/
RSOP': .............................................................................
MODIFIED.
20137 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
20138 19:52:09 (0) ** - REMOVED ACE:
20139 19:52:09 (0) ** ACEType: &h0
20140 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20141 19:52:09 (0) ** ACEFlags: &h12
20142 19:52:09 (0) ** CONTAINER_INHERIT_ACE
20143 19:52:09 (0) ** INHERITED_ACE
20144 19:52:09 (0) ** ACEMask: &h20023
20145 19:52:09 (0) ** WBEM_ENABLE
20146 19:52:09 (0) ** WBEM_METHOD_EXECUTE
20147 19:52:09 (0) ** WBEM_REMOTE_ACCESS
20148 19:52:09 (0) ** WBEM_READ_CONTROL
20149 19:52:09 (0) **
20150 19:52:09 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
20151 19:52:09 (0) ** Removing default security will cause some
operations to fail!
20152 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the ACE.
20153 19:52:09 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
20154 19:52:09 (0) **
20155 19:52:09 (0) ** WMI namespace security for 'ROOT/RSOP/
USER': ........................................................................
MODIFIED.
20156 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
20157 19:52:09 (0) ** - REMOVED ACE:
20158 19:52:09 (0) ** ACEType: &h0
20159 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20160 19:52:09 (0) ** ACEFlags: &h12
20161 19:52:09 (0) ** CONTAINER_INHERIT_ACE
20162 19:52:09 (0) ** INHERITED_ACE
20163 19:52:09 (0) ** ACEMask: &h6003F
20164 19:52:09 (0) ** WBEM_ENABLE
20165 19:52:09 (0) ** WBEM_METHOD_EXECUTE
20166 19:52:09 (0) ** WBEM_FULL_WRITE_REP
20167 19:52:09 (0) ** WBEM_PARTIAL_WRITE_REP
20168 19:52:09 (0) ** WBEM_WRITE_PROVIDER
20169 19:52:09 (0) ** WBEM_REMOTE_ACCESS
20170 19:52:09 (0) ** WBEM_WRITE_DAC
20171 19:52:09 (0) ** WBEM_READ_CONTROL
20172 19:52:09 (0) **
20173 19:52:09 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
20174 19:52:09 (0) ** Removing default security will cause some
operations to fail!
20175 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the ACE.
20176 19:52:09 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
20177 19:52:09 (0) **
20178 19:52:09 (0) ** WMI namespace security for 'ROOT/RSOP/
USER': ........................................................................
MODIFIED.
20179 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
20180 19:52:09 (0) ** - REMOVED ACE:
20181 19:52:09 (0) ** ACEType: &h0
20182 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20183 19:52:09 (0) ** ACEFlags: &h12
20184 19:52:09 (0) ** CONTAINER_INHERIT_ACE
20185 19:52:09 (0) ** INHERITED_ACE
20186 19:52:09 (0) ** ACEMask: &h20023
20187 19:52:09 (0) ** WBEM_ENABLE
20188 19:52:09 (0) ** WBEM_METHOD_EXECUTE
20189 19:52:09 (0) ** WBEM_REMOTE_ACCESS
20190 19:52:09 (0) ** WBEM_READ_CONTROL
20191 19:52:09 (0) **
20192 19:52:09 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
20193 19:52:09 (0) ** Removing default security will cause some
operations to fail!
20194 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the ACE.
20195 19:52:09 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
20196 19:52:09 (0) **
20197 19:52:09 (0) ** WMI namespace security for 'ROOT/RSOP/
COMPUTER': ....................................................................
MODIFIED.
20198 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has
been REMOVED!
20199 19:52:09 (0) ** - REMOVED ACE:
20200 19:52:09 (0) ** ACEType: &h0
20201 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20202 19:52:09 (0) ** ACEFlags: &h12
20203 19:52:09 (0) ** CONTAINER_INHERIT_ACE
20204 19:52:09 (0) ** INHERITED_ACE
20205 19:52:09 (0) ** ACEMask: &h6003F
20206 19:52:09 (0) ** WBEM_ENABLE
20207 19:52:09 (0) ** WBEM_METHOD_EXECUTE
20208 19:52:09 (0) ** WBEM_FULL_WRITE_REP
20209 19:52:09 (0) ** WBEM_PARTIAL_WRITE_REP
20210 19:52:09 (0) ** WBEM_WRITE_PROVIDER
20211 19:52:09 (0) ** WBEM_REMOTE_ACCESS
20212 19:52:09 (0) ** WBEM_WRITE_DAC
20213 19:52:09 (0) ** WBEM_READ_CONTROL
20214 19:52:09 (0) **
20215 19:52:09 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
20216 19:52:09 (0) ** Removing default security will cause some
operations to fail!
20217 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the ACE.
20218 19:52:09 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
20219 19:52:09 (0) **
20220 19:52:09 (0) ** WMI namespace security for 'ROOT/RSOP/
COMPUTER': ....................................................................
MODIFIED.
20221 19:52:09 (1) !! ERROR: Default trustee 'NT AUTHORITY
\AUTHENTICATED USERS' has been REMOVED!
20222 19:52:09 (0) ** - REMOVED ACE:
20223 19:52:09 (0) ** ACEType: &h0
20224 19:52:09 (0) ** ACCESS_ALLOWED_ACE_TYPE
20225 19:52:09 (0) ** ACEFlags: &h12
20226 19:52:09 (0) ** CONTAINER_INHERIT_ACE
20227 19:52:09 (0) ** INHERITED_ACE
20228 19:52:09 (0) ** ACEMask: &h20023
20229 19:52:09 (0) ** WBEM_ENABLE
20230 19:52:09 (0) ** WBEM_METHOD_EXECUTE
20231 19:52:09 (0) ** WBEM_REMOTE_ACCESS
20232 19:52:09 (0) ** WBEM_READ_CONTROL
20233 19:52:09 (0) **
20234 19:52:09 (0) ** => The REMOVED ACE was part of the DEFAULT setup
for the trustee.
20235 19:52:09 (0) ** Removing default security will cause some
operations to fail!
20236 19:52:09 (0) ** It is possible to fix this issue by editing
the security descriptor and adding the ACE.
20237 19:52:09 (0) ** For WMI namespaces, this can be done with
'WMIMGMT.MSC'.
20238 19:52:09 (0) **
20239 19:52:09 (0) **
20240 19:52:09 (0) ** DCOM security warning(s)
detected: ..................................................................................
0.
20241 19:52:09 (0) ** DCOM security error(s)
detected: ....................................................................................
2.
20242 19:52:09 (0) ** WMI security warning(s)
detected: ...................................................................................
0.
20243 19:52:09 (0) ** WMI security error(s)
detected: .....................................................................................
6.
20244 19:52:09 (0) **
20245 19:52:09 (1) !! ERROR: Overall DCOM security
status: ................................................................................
ERROR!
20246 19:52:09 (1) !! ERROR: Overall WMI security
status: .................................................................................
ERROR!
20247 19:52:09 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------------------------------------
20248 19:52:09 (0) ** INFO: WMI permanent
SUBSCRIPTION(S): ................................................................................
2.
20249 19:52:09 (0) ** - ROOT/SUBSCRIPTION,
MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario
Control".
20250 19:52:09 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE
TargetInstance ISA 'MSFT_UCScenario''
20251 19:52:09 (0) ** - ROOT/SUBSCRIPTION,
NTEventLogEventConsumer.Name="SCM Event Log Consumer".
20252 19:52:09 (0) ** 'select * from MSFT_SCMEventLogEvent'
20253 19:52:09 (0) **
20254 19:52:09 (0) ** WMI TIMER
instruction(s): ...........................................................................................
NONE.
20255 19:52:09 (0) ** WMI ADAP
status: ....................................................................................................
OK.
20256 19:52:09 (0) ** WMI MONIKER
CONNECTIONS: ............................................................................................
OK.
20257 19:52:09 (0) ** WMI
CONNECTIONS: ....................................................................................................
OK.
20258 19:52:09 (0) ** WMI GET
operations: .................................................................................................
OK.
20259 19:52:09 (0) ** WMI MOF
representations: ............................................................................................
OK.
20260 19:52:09 (0) ** WMI QUALIFIER access
operations: ....................................................................................
OK.
20261 19:52:09 (2) !! WARNING: WMI ENUMERATION operation errors
reported: .................................................................
1 WARNING(S)!
20262 19:52:09 (0) ** - Root/Default, InstancesOf, 'SystemRestore' did
not return any instance while AT LEAST 1 instance is expected.
20263 19:52:09 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\SR.MOF'
20264 19:52:09 (0) **
20265 19:52:09 (2) !! WARNING: WMI EXECQUERY operation errors
reported: ...................................................................
1 WARNING(S)!
20266 19:52:09 (0) ** - Root/Default, 'SELECT * FROM SystemRestore'
did not return any instance while AT LEAST 1 instance is expected.
20267 19:52:09 (0) **
20268 19:52:09 (0) ** WMI GET VALUE
operations: ...........................................................................................
OK.
20269 19:52:09 (0) ** WMI WRITE
operations: ...............................................................................................
NOT TESTED.
20270 19:52:09 (0) ** WMI PUT
operations: .................................................................................................
NOT TESTED.
20271 19:52:09 (0) ** WMI DELETE
operations: ..............................................................................................
NOT TESTED.
20272 19:52:09 (0) ** WMI static instances
retrieved: .....................................................................................
756.
20273 19:52:09 (0) ** WMI dynamic instances
retrieved: ....................................................................................
0.
20274 19:52:09 (0) ** WMI instance request cancellations (to limit
performance
impact): ................................................... 0.
20275 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20276 19:52:09 (0) ** # of Event Log events BEFORE WMIDiag execution
since the last 20 day(s):
20277 19:52:09 (0) **
DCOM: .............................................................................................................
1.
20278 19:52:09 (0) **
WINMGMT: ..........................................................................................................
0.
20279 19:52:09 (0) **
WMIADAPTER: .......................................................................................................
0.
20280 19:52:09 (0) ** => Verify the WMIDiag LOG at line #19513 for
more details.
20281 19:52:09 (0) **
20282 19:52:09 (0) ** # of additional Event Log events AFTER WMIDiag
execution:
20283 19:52:09 (0) **
DCOM: .............................................................................................................
0.
20284 19:52:09 (0) **
WINMGMT: ..........................................................................................................
0.
20285 19:52:09 (0) **
WMIADAPTER: .......................................................................................................
0.
20286 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20287 19:52:09 (0) ** Unexpected, wrong or missing registry key
values: ...................................................................
1 KEY(S)!
20288 19:52:09 (1) !! ERROR: Unexpected registry key value:
20289 19:52:09 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM
\WMISetup (REG_SZ) -> 1
20290 19:52:09 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM
\WMISetup (REG_SZ) -> 0
20291 19:52:09 (0) ** From the command line, the registry
configuration can be corrected with the following command:
20292 19:52:09 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft
\WBEM\CIMOM" /v "WMISetup" /t "REG_SZ" /d "0" /f'
20293 19:52:09 (0) **
20294 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20295 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20296 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20297 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20298 19:52:09 (0) **
20299 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20300 19:52:09 (0) **
------------------------------------------------------ WMI REPORT: END
-----------------------------------------------------------
20301 19:52:09 (0) **
----------------------------------------------------------------------------------------------------------------------------------
20302 19:52:09 (0) **
20303 19:52:09 (0) ** ERROR: WMIDiag detected issues that could
prevent WMI to work properly!. Check 'D:\USERS\_MYWINUSERNAME\LOCAL
SETTINGS\TEMP\WMIDIAG-
V2.0_XP___.CLI.SP2.32__MYWINUSERNAMEW_2008.09.10_19.48.58.LOG' for
details.
20304 19:52:09 (0) **
20305 19:52:09 (0) ** WMIDiag v2.0 ended on Wednesday, September 10,
2008 at 19:52 (W:89 E:19 S:1).
Back to top
Guest
Guest



Posts
Location

PostPosted: Thu Sep 11, 2008 1:04 am    Post subject: Google Ads Reply with quote

Back to top
sherrylkissinger@gmail.co
Guest





PostPosted: Thu Sep 11, 2008 2:13 pm    Post subject: Re: Windows Management Instrumentation: wmic' is not recogni Reply with quote

On Sep 10, 7:47 pm, Tsunhin John Wong <thjw...@gmail.com> wrote:
Quote:
Hi all,

I am using Windows XP Pro Version 2002 SP2.
When I type "wmic" in command prompt, I get the following error
message:

'wmic' is not recognized as an internal or external command,
operable program or batch file.

After doing a search, I found wmic.exe in:
1.
C:\WINDOWS\ServicePackFiles\i386
2.
C:\WINDOWS\system32\dllcache

And when I try to run "C:\WINDOWS\ServicePackFiles\i386\wmic"
or
"C:\WINDOWS\system32\dllcache\wmic"
I get the following error message:

Please wait while WMIC compiles updatedMOFfiles.
ParsingMofFile: C:\WINDOWS\system32\wbem\Cli.mof(Phase Error - 2)
Compiler returned error 0x8004401e

Please help me to get my WMI Tools back to service, thanks a lot!

- J

You might want to try the WMI Diags:
http://www.microsoft.com/DownLoads/details.aspx?familyid=D7BA3CD6-18D1-4D05-B11E-4C64192AE97D&displaylang=en
Back to top
Display posts from previous:   
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    Windows-Expert.com Forum Index -> Windows XP General All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Topic Links: syslog
Powered by phpBB © 2001, 2005 phpBB Group