T
thedge000
I am running XP Pro SP2 and I got these errors after each boot up after
I installed drivers for a Best Data Modem. I tried restoring the
system before the driver install point but did not fix the problem.
Below is the WMI report from the WMIDiag . Do I have the right fixes?
Thanks
from a command-line session
1) WMIDiag Method
'winmgmt/clearadap'
'winmgmt/resyncperf'
1a) Alternate method I found to repair and syncronize
'winmgmt/clearadap'
'winmgmt/kill'
'winmgmt/unregserver'
'winmgmt/regserver'
If these don't work then,
2) WMIDiag Method to Rebuild Repository
'WMDiag ShowMOFErrors' copy all MOF files to fix later
'WMDiag CheckConsistency'
Need further explaination how to fix MOF files.
2a) suport.microsoft.com states XPP SP2 can repair a corrupted WMI
Repository with single command
rundll32 wbemupdg, UpgradeRepository
----------------------------------------------------------------------------------------------------
..1149 14:02:58 (0) ** -------------------------------------- WMI
REPORT: BEGIN -------------------------------------------
..1150 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1151 14:02:58 (0) **
..1152 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1153 14:02:58 (0) ** Windows XP - Service pack 2 - 32-bit - User
'OWNER-39E8F8119\OWNER' on computer 'OWNER-39E8F8119'.
..1154 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1155 14:02:58 (0) ** There are no missing WMI system files:
...................................................... OK.
..1156 14:02:58 (0) ** There are no missing WMI repository files:
.................................................. OK.
..1157 14:02:58 (0) ** BEFORE running WMIDiag:
..1158 14:02:58 (0) ** The WMI repository has a size of:
........................................................... 7 MB.
..1159 14:02:58 (0) ** - Disk free space on 'C:':
..................................................................
231110 MB.
..1160 14:02:58 (0) ** - INDEX.BTR, 1073152 bytes,
10/6/2006 10:06:29 AM
..1161 14:02:58 (0) ** - INDEX.MAP, 548 bytes,
11/2/2006 10:57:14 AM
..1162 14:02:58 (0) ** - MAPPING.VER, 4 bytes,
11/2/2006 10:57:14 AM
..1163 14:02:58 (0) ** - MAPPING1.MAP, 3388 bytes,
11/2/2006 10:49:34 AM
..1164 14:02:58 (0) ** - MAPPING2.MAP, 3388 bytes,
11/2/2006 10:57:14 AM
..1165 14:02:58 (0) ** - OBJECTS.DATA, 5767168 bytes,
10/6/2006 10:06:29 AM
..1166 14:02:58 (0) ** - OBJECTS.MAP, 2840 bytes,
11/2/2006 10:57:14 AM
..1167 14:02:58 (0) ** AFTER running WMIDiag:
..1168 14:02:58 (0) ** The WMI repository has a size of:
........................................................... 7 MB.
..1169 14:02:58 (0) ** - Disk free space on 'C:':
..................................................................
231110 MB.
..1170 14:02:58 (0) ** - INDEX.BTR, 1073152 bytes,
10/6/2006 10:06:29 AM
..1171 14:02:58 (0) ** - INDEX.MAP, 548 bytes,
11/2/2006 10:57:14 AM
..1172 14:02:58 (0) ** - MAPPING.VER, 4 bytes,
11/2/2006 10:57:14 AM
..1173 14:02:58 (0) ** - MAPPING1.MAP, 3388 bytes,
11/2/2006 10:49:34 AM
..1174 14:02:58 (0) ** - MAPPING2.MAP, 3388 bytes,
11/2/2006 10:57:14 AM
..1175 14:02:58 (0) ** - OBJECTS.DATA, 5767168 bytes,
10/6/2006 10:06:29 AM
..1176 14:02:58 (0) ** - OBJECTS.MAP, 2840 bytes,
11/2/2006 10:57:14 AM
..1177 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1178 14:02:58 (2) !! WARNING: Windows Firewall:
..................................................................
INACTIVE.
..1179 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1180 14:02:58 (0) ** WMI registry setup:
.........................................................................
OK.
..1181 14:02:58 (0) ** INFO: WMI service has dependents:
........................................................... 2
SERVICE(S)!
..1182 14:02:58 (0) ** - Security Center (WSCSVC, StartMode='Disabled')
..1183 14:02:58 (0) ** - Windows Firewall/Internet Connection Sharing
(ICS) (SHAREDACCESS, StartMode='Automatic')
..1184 14:02:58 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
..1185 14:02:58 (0) ** Note: If the service is marked with (*), it
means that the service/application uses WMI but
..1186 14:02:58 (0) ** there is no hard dependency on WMI.
However, if the WMI service is stopped,
..1187 14:02:58 (0) ** this can prevent the service/application
to work as expected.
..1188 14:02:58 (0) **
..1189 14:02:58 (0) ** RPCSS service:
..............................................................................
OK (Already started).
..1190 14:02:58 (0) ** WINMGMT service:
............................................................................
OK (Already started).
..1191 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1192 14:02:58 (0) ** WMI service DCOM setup:
.....................................................................
OK.
..1193 14:02:58 (0) ** WMI components DCOM registrations:
.......................................................... OK.
..1194 14:02:58 (0) ** WMI ProgID registrations:
................................................................... OK.
..1195 14:02:58 (0) ** WMI provider DCOM registrations:
............................................................ OK.
..1196 14:02:58 (0) ** WMI provider CIM registrations:
............................................................. OK.
..1197 14:02:58 (0) ** WMI provider CLSIDs:
........................................................................
OK.
..1198 14:02:58 (0) ** WMI providers EXE/DLL availability:
......................................................... OK.
..1199 14:02:58 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------
..1200 14:02:58 (1) !! ERROR: WMI ADAP status:
.....................................................................
NOT AVAILABLE
..1201 14:02:58 (0) ** You can start the WMI AutoDiscovery/AutoPurge
(ADAP) process to resynchronize
..1202 14:02:58 (0) ** the performance counters with the WMI
performance classes with the following commands:
..1203 14:02:58 (0) ** e.g. 'WINMGMT.EXE /CLEARADAP'
..1204 14:02:58 (0) ** e.g. 'WINMGMT.EXE /RESYNCPERF'
..1205 14:02:58 (0) ** The ADAP process logs informative events in
the Windows NT event log.
..1206 14:02:58 (0) ** More information can be found on MSDN at:
..1207 14:02:58 (0) **
http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp
..1208 14:02:58 (1) !! ERROR: WMI CONNECTION errors occured for the
following namespaces: ......................... 5 ERROR(S)!
..1209 14:02:58 (0) ** - Root, 0x80041001 - (WBEM_E_FAILED) Call failed.
..1210 14:02:58 (0) ** - Root, 0x80041001 - (WBEM_E_FAILED) Call failed.
..1211 14:02:58 (0) ** - Root/Default, 0x80041001 - (WBEM_E_FAILED) Call
failed.
..1212 14:02:58 (0) ** - Root/CIMv2, 0x80041001 - (WBEM_E_FAILED) Call
failed.
..1213 14:02:58 (0) ** - Root/WMI, 0x80041001 - (WBEM_E_FAILED) Call
failed.
..1214 14:02:58 (0) **
..1215 14:02:58 (0) ** WMI GET static operations:
.................................................................. OK.
..1216 14:02:58 (0) ** WMI MOF representations:
.................................................................... OK.
..1217 14:02:58 (0) ** WMI QUALIFIER access operations:
............................................................ OK.
..1218 14:02:58 (0) ** WMI ENUMERATION operations:
................................................................. OK.
..1219 14:02:58 (0) ** WMI EXECQUERY operations:
................................................................... OK.
..1220 14:02:58 (0) ** WMI PUT operations:
.........................................................................
OK.
..1221 14:02:58 (0) ** WMI DELETE operations:
......................................................................
OK.
..1222 14:02:58 (0) ** WMI GET VALUE operations:
................................................................... OK.
..1223 14:02:58 (0) ** WMI static instances retrieved:
............................................................. 0.
..1224 14:02:58 (0) ** WMI dynamic instances retrieved:
............................................................ 0.
..1225 14:02:58 (0) ** WMI instances request cancellations (to limit
performance impact): ......................... 0.
..1226 14:02:58 (0) **
..1227 14:02:58 (0) ** 5 error(s) 0x80041001 - (WBEM_E_FAILED) Call
failed
..1228 14:02:58 (0) ** => This error is typically a WMI system error.
WMI system errors can find their origins in:
..1229 14:02:58 (0) ** - Failing WMI system components (see any
missing WMI system files or DCOM registration
..1230 14:02:58 (0) ** issues previously mentioned).
..1231 14:02:58 (0) ** - Failing WMI providers (see any WMI provider
DCOM registration
..1232 14:02:58 (0) ** issues previously mentioned).
..1233 14:02:58 (0) ** - Failing operation in WMI providers because
the underlying component queried by the WMI
..1234 14:02:58 (0) ** provider is not available (e.g. not
installed, not running or not available).
..1235 14:02:58 (0) ** - Corrupted WMI repository.
..1236 14:02:58 (0) ** - Under Windows XP SP2, you can validate the
repository consistency
..1237 14:02:58 (0) ** by executing the following command:
..1238 14:02:58 (0) ** e.g. 'WMIDiag CheckConsistency'
..1239 14:02:58 (0) ** Note: Under Windows XP SP2, when the
repository is checked and detected INCONSISTENT,
..1240 14:02:58 (0) ** a new repository is automatically
re-created based on Auto-Recovery mechanism.
..1241 14:02:58 (0) ** Note that some information can be lost
during this process (e.g. static data, CIM registration).
..1242 14:02:58 (0) ** However, the original repository is
located at 'C:\WINDOWS\SYSTEM32\WBEM\Repository.001'.
..1243 14:02:58 (0) ** The machine must be rebooted for the
system to work with the re-created repository.
..1244 14:02:58 (0) ** Note: The WMI repository reconstruction
requires to locate all MOF files needed to rebuild the repository,
..1245 14:02:58 (0) ** otherwise some applications may fail
after the reconstruction.
..1246 14:02:58 (0) ** This can be achieved with the following
command:
..1247 14:02:58 (0) ** e.g. 'WMIDiag ShowMOFErrors'
..1248 14:02:58 (0) ** Note: The repository reconstruction must be a
LAST RESORT solution and ONLY after executing
..1249 14:02:58 (0) ** ALL fixes previously mentioned.
..1250 14:02:58 (2) !! WARNING: Static information stored by external
applications in the repository will be LOST! (e.g. SMS Inventory)
..1251 14:02:58 (0) **
..1252 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1253 14:02:58 (0) ** WMI Registry key setup:
.....................................................................
OK.
..1254 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1255 14:02:58 (1) !! ERROR: MOF file(s) present in the WBEM folder not
referenced in the Auto-Recovery list: .... 18 ERROR(S)!
..1256 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MFL(*)
..1257 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MOF(*)
..1258 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FCONPROV.MFL(*)
..1259 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FCONPROV.MOF(*)
..1260 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL(*)
..1261 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF(*)
..1262 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL(*)
..1263 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF(*)
..1264 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL(*)
..1265 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF(*)
..1266 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TMPLPROV.MFL(*)
..1267 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TMPLPROV.MOF(*)
..1268 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TRNSPROV.MFL(*)
..1269 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TRNSPROV.MOF(*)
..1270 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UPDPROV.MFL(*)
..1271 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UPDPROV.MOF(*)
..1272 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL(*)
..1273 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF(*)
..1274 14:02:58 (0) ** => After fixing all other issues previously
mentioned, if the WMI repository is rebuilt,
..1275 14:02:58 (0) ** the listed MOF file(s) will not be recompiled,
and therefore the definition they contain
..1276 14:02:58 (0) ** will not be available in the WMI repository.
..1277 14:02:58 (0) ** => You must manually recompile the MOF file(s)
with the 'MOFCOMP.EXE <FileName.MOF>' command.
..1278 14:02:58 (0) ** => If you want the MOF file(s) to be part of the
Auto-Recovery list, make sure the
..1279 14:02:58 (0) ** statement '#PRAGMA AUTORECOVER' is included.
..1280 14:02:58 (0) ** Note: MOF file(s) marked with a (*) are not
included BY DEFAULT in the auto-recovery process.
..1281 14:02:58 (0) **
..1282 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1283 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1284 14:02:58 (0) ** --------------------------------------- WMI
REPORT: END --------------------------------------------
..1285 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1286 14:02:58 (0) **
..1287 14:02:58 (0) ** ERROR: WMIDiag detected issues that could prevent
WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG'
for details.
..1288 14:02:58 (0) **
..1289 14:02:58 (0) ** WMIDiag executed in 45 second(s).
..1290 14:02:58 (3)
..1291 14:02:58 (3) 1.10,11/2/2006,2:02:53 PM,11/2/2006 2:02:53
PM,False,False,False,32-bit,x86 Family 6 Model 15 Stepping 6
GenuineIntel,5.1,2600,Service Pack 2,Windows XP - Service pack 2 -
32-bit,XP__.CLI.SP2.32,00000409,OWNER-39E8F8119,OWNER-39E8F8119\OWNER,False,Root,
,0,0,0,0, ,7,231110,7,231110,0, ,
,0,2,0,0,0,0,0,0,0,0,N/A,0,5,0,0,0,0,0,0,0,0,0,0,0,
,0,0,0,0,18,0,11/2/2006,2:02:58
PM,0,0,0,45,11,10,1,WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG,C:\DOCUMENTS
AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG
..1292 14:02:58 (3)
..1293 14:02:58 (0) ** WMIDiag v1.10 ended on Thursday, November 02,
2006 at 14:02 (W:11 E:10 S:1).
..1294 14:02:58 (0) ** CSV file "C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13-STATISTICS.CSV"
closed.
..1295 14:02:58 (0) ** LOG file "C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG"
closed.
I installed drivers for a Best Data Modem. I tried restoring the
system before the driver install point but did not fix the problem.
Below is the WMI report from the WMIDiag . Do I have the right fixes?
Thanks
from a command-line session
1) WMIDiag Method
'winmgmt/clearadap'
'winmgmt/resyncperf'
1a) Alternate method I found to repair and syncronize
'winmgmt/clearadap'
'winmgmt/kill'
'winmgmt/unregserver'
'winmgmt/regserver'
If these don't work then,
2) WMIDiag Method to Rebuild Repository
'WMDiag ShowMOFErrors' copy all MOF files to fix later
'WMDiag CheckConsistency'
Need further explaination how to fix MOF files.
2a) suport.microsoft.com states XPP SP2 can repair a corrupted WMI
Repository with single command
rundll32 wbemupdg, UpgradeRepository
----------------------------------------------------------------------------------------------------
..1149 14:02:58 (0) ** -------------------------------------- WMI
REPORT: BEGIN -------------------------------------------
..1150 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1151 14:02:58 (0) **
..1152 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1153 14:02:58 (0) ** Windows XP - Service pack 2 - 32-bit - User
'OWNER-39E8F8119\OWNER' on computer 'OWNER-39E8F8119'.
..1154 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1155 14:02:58 (0) ** There are no missing WMI system files:
...................................................... OK.
..1156 14:02:58 (0) ** There are no missing WMI repository files:
.................................................. OK.
..1157 14:02:58 (0) ** BEFORE running WMIDiag:
..1158 14:02:58 (0) ** The WMI repository has a size of:
........................................................... 7 MB.
..1159 14:02:58 (0) ** - Disk free space on 'C:':
..................................................................
231110 MB.
..1160 14:02:58 (0) ** - INDEX.BTR, 1073152 bytes,
10/6/2006 10:06:29 AM
..1161 14:02:58 (0) ** - INDEX.MAP, 548 bytes,
11/2/2006 10:57:14 AM
..1162 14:02:58 (0) ** - MAPPING.VER, 4 bytes,
11/2/2006 10:57:14 AM
..1163 14:02:58 (0) ** - MAPPING1.MAP, 3388 bytes,
11/2/2006 10:49:34 AM
..1164 14:02:58 (0) ** - MAPPING2.MAP, 3388 bytes,
11/2/2006 10:57:14 AM
..1165 14:02:58 (0) ** - OBJECTS.DATA, 5767168 bytes,
10/6/2006 10:06:29 AM
..1166 14:02:58 (0) ** - OBJECTS.MAP, 2840 bytes,
11/2/2006 10:57:14 AM
..1167 14:02:58 (0) ** AFTER running WMIDiag:
..1168 14:02:58 (0) ** The WMI repository has a size of:
........................................................... 7 MB.
..1169 14:02:58 (0) ** - Disk free space on 'C:':
..................................................................
231110 MB.
..1170 14:02:58 (0) ** - INDEX.BTR, 1073152 bytes,
10/6/2006 10:06:29 AM
..1171 14:02:58 (0) ** - INDEX.MAP, 548 bytes,
11/2/2006 10:57:14 AM
..1172 14:02:58 (0) ** - MAPPING.VER, 4 bytes,
11/2/2006 10:57:14 AM
..1173 14:02:58 (0) ** - MAPPING1.MAP, 3388 bytes,
11/2/2006 10:49:34 AM
..1174 14:02:58 (0) ** - MAPPING2.MAP, 3388 bytes,
11/2/2006 10:57:14 AM
..1175 14:02:58 (0) ** - OBJECTS.DATA, 5767168 bytes,
10/6/2006 10:06:29 AM
..1176 14:02:58 (0) ** - OBJECTS.MAP, 2840 bytes,
11/2/2006 10:57:14 AM
..1177 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1178 14:02:58 (2) !! WARNING: Windows Firewall:
..................................................................
INACTIVE.
..1179 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1180 14:02:58 (0) ** WMI registry setup:
.........................................................................
OK.
..1181 14:02:58 (0) ** INFO: WMI service has dependents:
........................................................... 2
SERVICE(S)!
..1182 14:02:58 (0) ** - Security Center (WSCSVC, StartMode='Disabled')
..1183 14:02:58 (0) ** - Windows Firewall/Internet Connection Sharing
(ICS) (SHAREDACCESS, StartMode='Automatic')
..1184 14:02:58 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
..1185 14:02:58 (0) ** Note: If the service is marked with (*), it
means that the service/application uses WMI but
..1186 14:02:58 (0) ** there is no hard dependency on WMI.
However, if the WMI service is stopped,
..1187 14:02:58 (0) ** this can prevent the service/application
to work as expected.
..1188 14:02:58 (0) **
..1189 14:02:58 (0) ** RPCSS service:
..............................................................................
OK (Already started).
..1190 14:02:58 (0) ** WINMGMT service:
............................................................................
OK (Already started).
..1191 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1192 14:02:58 (0) ** WMI service DCOM setup:
.....................................................................
OK.
..1193 14:02:58 (0) ** WMI components DCOM registrations:
.......................................................... OK.
..1194 14:02:58 (0) ** WMI ProgID registrations:
................................................................... OK.
..1195 14:02:58 (0) ** WMI provider DCOM registrations:
............................................................ OK.
..1196 14:02:58 (0) ** WMI provider CIM registrations:
............................................................. OK.
..1197 14:02:58 (0) ** WMI provider CLSIDs:
........................................................................
OK.
..1198 14:02:58 (0) ** WMI providers EXE/DLL availability:
......................................................... OK.
..1199 14:02:58 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------
..1200 14:02:58 (1) !! ERROR: WMI ADAP status:
.....................................................................
NOT AVAILABLE
..1201 14:02:58 (0) ** You can start the WMI AutoDiscovery/AutoPurge
(ADAP) process to resynchronize
..1202 14:02:58 (0) ** the performance counters with the WMI
performance classes with the following commands:
..1203 14:02:58 (0) ** e.g. 'WINMGMT.EXE /CLEARADAP'
..1204 14:02:58 (0) ** e.g. 'WINMGMT.EXE /RESYNCPERF'
..1205 14:02:58 (0) ** The ADAP process logs informative events in
the Windows NT event log.
..1206 14:02:58 (0) ** More information can be found on MSDN at:
..1207 14:02:58 (0) **
http://msdn.microsoft.com/library/d...n-us/wmisdk/wmi/wmi_adap_event_log_events.asp
..1208 14:02:58 (1) !! ERROR: WMI CONNECTION errors occured for the
following namespaces: ......................... 5 ERROR(S)!
..1209 14:02:58 (0) ** - Root, 0x80041001 - (WBEM_E_FAILED) Call failed.
..1210 14:02:58 (0) ** - Root, 0x80041001 - (WBEM_E_FAILED) Call failed.
..1211 14:02:58 (0) ** - Root/Default, 0x80041001 - (WBEM_E_FAILED) Call
failed.
..1212 14:02:58 (0) ** - Root/CIMv2, 0x80041001 - (WBEM_E_FAILED) Call
failed.
..1213 14:02:58 (0) ** - Root/WMI, 0x80041001 - (WBEM_E_FAILED) Call
failed.
..1214 14:02:58 (0) **
..1215 14:02:58 (0) ** WMI GET static operations:
.................................................................. OK.
..1216 14:02:58 (0) ** WMI MOF representations:
.................................................................... OK.
..1217 14:02:58 (0) ** WMI QUALIFIER access operations:
............................................................ OK.
..1218 14:02:58 (0) ** WMI ENUMERATION operations:
................................................................. OK.
..1219 14:02:58 (0) ** WMI EXECQUERY operations:
................................................................... OK.
..1220 14:02:58 (0) ** WMI PUT operations:
.........................................................................
OK.
..1221 14:02:58 (0) ** WMI DELETE operations:
......................................................................
OK.
..1222 14:02:58 (0) ** WMI GET VALUE operations:
................................................................... OK.
..1223 14:02:58 (0) ** WMI static instances retrieved:
............................................................. 0.
..1224 14:02:58 (0) ** WMI dynamic instances retrieved:
............................................................ 0.
..1225 14:02:58 (0) ** WMI instances request cancellations (to limit
performance impact): ......................... 0.
..1226 14:02:58 (0) **
..1227 14:02:58 (0) ** 5 error(s) 0x80041001 - (WBEM_E_FAILED) Call
failed
..1228 14:02:58 (0) ** => This error is typically a WMI system error.
WMI system errors can find their origins in:
..1229 14:02:58 (0) ** - Failing WMI system components (see any
missing WMI system files or DCOM registration
..1230 14:02:58 (0) ** issues previously mentioned).
..1231 14:02:58 (0) ** - Failing WMI providers (see any WMI provider
DCOM registration
..1232 14:02:58 (0) ** issues previously mentioned).
..1233 14:02:58 (0) ** - Failing operation in WMI providers because
the underlying component queried by the WMI
..1234 14:02:58 (0) ** provider is not available (e.g. not
installed, not running or not available).
..1235 14:02:58 (0) ** - Corrupted WMI repository.
..1236 14:02:58 (0) ** - Under Windows XP SP2, you can validate the
repository consistency
..1237 14:02:58 (0) ** by executing the following command:
..1238 14:02:58 (0) ** e.g. 'WMIDiag CheckConsistency'
..1239 14:02:58 (0) ** Note: Under Windows XP SP2, when the
repository is checked and detected INCONSISTENT,
..1240 14:02:58 (0) ** a new repository is automatically
re-created based on Auto-Recovery mechanism.
..1241 14:02:58 (0) ** Note that some information can be lost
during this process (e.g. static data, CIM registration).
..1242 14:02:58 (0) ** However, the original repository is
located at 'C:\WINDOWS\SYSTEM32\WBEM\Repository.001'.
..1243 14:02:58 (0) ** The machine must be rebooted for the
system to work with the re-created repository.
..1244 14:02:58 (0) ** Note: The WMI repository reconstruction
requires to locate all MOF files needed to rebuild the repository,
..1245 14:02:58 (0) ** otherwise some applications may fail
after the reconstruction.
..1246 14:02:58 (0) ** This can be achieved with the following
command:
..1247 14:02:58 (0) ** e.g. 'WMIDiag ShowMOFErrors'
..1248 14:02:58 (0) ** Note: The repository reconstruction must be a
LAST RESORT solution and ONLY after executing
..1249 14:02:58 (0) ** ALL fixes previously mentioned.
..1250 14:02:58 (2) !! WARNING: Static information stored by external
applications in the repository will be LOST! (e.g. SMS Inventory)
..1251 14:02:58 (0) **
..1252 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1253 14:02:58 (0) ** WMI Registry key setup:
.....................................................................
OK.
..1254 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1255 14:02:58 (1) !! ERROR: MOF file(s) present in the WBEM folder not
referenced in the Auto-Recovery list: .... 18 ERROR(S)!
..1256 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MFL(*)
..1257 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MOF(*)
..1258 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FCONPROV.MFL(*)
..1259 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FCONPROV.MOF(*)
..1260 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL(*)
..1261 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF(*)
..1262 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL(*)
..1263 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF(*)
..1264 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL(*)
..1265 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF(*)
..1266 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TMPLPROV.MFL(*)
..1267 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TMPLPROV.MOF(*)
..1268 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TRNSPROV.MFL(*)
..1269 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TRNSPROV.MOF(*)
..1270 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UPDPROV.MFL(*)
..1271 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\UPDPROV.MOF(*)
..1272 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL(*)
..1273 14:02:58 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF(*)
..1274 14:02:58 (0) ** => After fixing all other issues previously
mentioned, if the WMI repository is rebuilt,
..1275 14:02:58 (0) ** the listed MOF file(s) will not be recompiled,
and therefore the definition they contain
..1276 14:02:58 (0) ** will not be available in the WMI repository.
..1277 14:02:58 (0) ** => You must manually recompile the MOF file(s)
with the 'MOFCOMP.EXE <FileName.MOF>' command.
..1278 14:02:58 (0) ** => If you want the MOF file(s) to be part of the
Auto-Recovery list, make sure the
..1279 14:02:58 (0) ** statement '#PRAGMA AUTORECOVER' is included.
..1280 14:02:58 (0) ** Note: MOF file(s) marked with a (*) are not
included BY DEFAULT in the auto-recovery process.
..1281 14:02:58 (0) **
..1282 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1283 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1284 14:02:58 (0) ** --------------------------------------- WMI
REPORT: END --------------------------------------------
..1285 14:02:58 (0) **
----------------------------------------------------------------------------------------------------
..1286 14:02:58 (0) **
..1287 14:02:58 (0) ** ERROR: WMIDiag detected issues that could prevent
WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG'
for details.
..1288 14:02:58 (0) **
..1289 14:02:58 (0) ** WMIDiag executed in 45 second(s).
..1290 14:02:58 (3)
..1291 14:02:58 (3) 1.10,11/2/2006,2:02:53 PM,11/2/2006 2:02:53
PM,False,False,False,32-bit,x86 Family 6 Model 15 Stepping 6
GenuineIntel,5.1,2600,Service Pack 2,Windows XP - Service pack 2 -
32-bit,XP__.CLI.SP2.32,00000409,OWNER-39E8F8119,OWNER-39E8F8119\OWNER,False,Root,
,0,0,0,0, ,7,231110,7,231110,0, ,
,0,2,0,0,0,0,0,0,0,0,N/A,0,5,0,0,0,0,0,0,0,0,0,0,0,
,0,0,0,0,18,0,11/2/2006,2:02:58
PM,0,0,0,45,11,10,1,WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG,C:\DOCUMENTS
AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG
..1292 14:02:58 (3)
..1293 14:02:58 (0) ** WMIDiag v1.10 ended on Thursday, November 02,
2006 at 14:02 (W:11 E:10 S:1).
..1294 14:02:58 (0) ** CSV file "C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13-STATISTICS.CSV"
closed.
..1295 14:02:58 (0) ** LOG file "C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL
SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_OWNER-39E8F8119_2006.11.02_14.02.13.LOG"
closed.