WMI Initialization Failed, can't connect with root\cimv2 - how do I fix it? : WMI, Initializaion Failure, .mof, WMIDIAG

Experts Exchange

	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.9

WMI Initialization Failed, can't connect with root\cimv2 - how do I fix it?

Asked by wrguy in Microsoft Windows Operating Systems, Microsoft Applications, Windows 2003 Server

Tags: WMI, Initializaion Failure, .mof, WMIDIAG

Hi all,

I've been having troubles running a particular installer which runs fine on one machine, but errors out on another. After a lot of digging through logs, I'm sure that the issue boils down to the WMI failing during Initialization. When I go to My Computer >Manage > WMI Control >Properties, the general tab displays an error stating "Failed to connect to <local computer> because WMI: Initialization failure". If I try to connect using wbemtest.exe, I get a similar error when connecting to root\cimv2 (Number: 0x80041014 Facility: WMI Description: Initialization failure).

I ran the WMIDIAG util, and have copied the resulting output. Can anyone please help me decode this output? Any ideas on how to get the WMI to initialize normally?

This is on Windows 2003

Thanks,
wrguy

Get your answer NOW

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:

           
           
             .1428 05:43:29 (0) ** WMIDiag v2.0 started on 22 September 2009 at 05:43.
.1429 05:43:29 (0) ** 
.1430 05:43:29 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1431 05:43:29 (0) ** 
.1432 05:43:29 (0) ** This script is not supported under any Microsoft standard support program or service.
.1433 05:43:29 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1434 05:43:29 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1435 05:43:29 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1436 05:43:29 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1437 05:43:29 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1438 05:43:29 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1439 05:43:29 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1440 05:43:29 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1441 05:43:29 (0) ** of the possibility of such damages.
.1442 05:43:29 (0) ** 
.1443 05:43:29 (0) ** 
.1444 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1445 05:43:29 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1446 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1447 05:43:29 (0) ** 
.1448 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1449 05:43:29 (0) ** Windows Server 2003 - No service pack - 32-bit (3790) - User 'DELLSC1420\ADMINISTRATOR' on computer 'DELLSC1420'.
.1450 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1451 05:43:29 (0) ** Environment: ........................................................................................................ OK..
.1452 05:43:29 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1453 05:43:29 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1454 05:43:29 (0) ** WMI repository state: ............................................................................................... N/A.
.1455 05:43:29 (0) ** BEFORE running WMIDiag:
.1456 05:43:29 (0) ** The WMI repository has a size of: ................................................................................... 14 MB.
.1457 05:43:29 (0) ** - Disk free space on 'C:': .......................................................................................... 7913 MB.
.1458 05:43:29 (0) **   - INDEX.BTR,                     2326528 bytes,      13/01/2008 17:41:33
.1459 05:43:29 (0) **   - MAPPING.VER,                   4 bytes,            13/01/2008 17:41:33
.1460 05:43:29 (0) **   - MAPPING1.MAP,                  7464 bytes,         22/09/2009 05:29:16
.1461 05:43:29 (0) **   - MAPPING2.MAP,                  7464 bytes,         13/01/2008 17:41:33
.1462 05:43:29 (0) **   - OBJECTS.DATA,                  12779520 bytes,     13/01/2008 17:41:32
.1463 05:43:29 (0) ** AFTER running WMIDiag:
.1464 05:43:29 (0) ** The WMI repository has a size of: ................................................................................... 14 MB.
.1465 05:43:29 (0) ** - Disk free space on 'C:': .......................................................................................... 7912 MB.
.1466 05:43:29 (0) **   - INDEX.BTR,                     2326528 bytes,      13/01/2008 17:41:33
.1467 05:43:29 (0) **   - MAPPING.VER,                   4 bytes,            13/01/2008 17:41:33
.1468 05:43:29 (0) **   - MAPPING1.MAP,                  7464 bytes,         22/09/2009 05:29:16
.1469 05:43:29 (0) **   - MAPPING2.MAP,                  7464 bytes,         13/01/2008 17:41:33
.1470 05:43:29 (0) **   - OBJECTS.DATA,                  12779520 bytes,     13/01/2008 17:41:32
.1471 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1472 05:43:29 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.1473 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1474 05:43:29 (0) ** DCOM Status: ........................................................................................................ OK.
.1475 05:43:29 (0) ** WMI registry setup: ................................................................................................. OK.
.1476 05:43:29 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.1477 05:43:29 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1478 05:43:29 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1479 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1480 05:43:29 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1481 05:43:29 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1482 05:43:29 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1483 05:43:29 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1484 05:43:29 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1485 05:43:29 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1486 05:43:29 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1487 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1488 05:43:29 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1489 05:43:29 (0) ** Overall WMI security status: ........................................................................................ OK.
.1490 05:43:29 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1491 05:43:29 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1492 05:43:29 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1493 05:43:29 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1494 05:43:29 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1495 05:43:29 (0) **    the performance counters with the WMI performance classes with the following commands:
.1496 05:43:29 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1497 05:43:29 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1498 05:43:29 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1499 05:43:29 (0) **    More information can be found on MSDN at:
.1500 05:43:29 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1501 05:43:29 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1502 05:43:29 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1503 05:43:29 (0) ** 
.1504 05:43:29 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1505 05:43:29 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1506 05:43:29 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1507 05:43:29 (0) ** - Root/Default, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1508 05:43:29 (0) ** - Root/CIMv2, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1509 05:43:29 (0) ** - Root/WMI, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1510 05:43:29 (0) ** 
.1511 05:43:29 (0) ** WMI GET operations: ................................................................................................. OK.
.1512 05:43:29 (0) ** WMI MOF representations: ............................................................................................ OK.
.1513 05:43:29 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1514 05:43:29 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1515 05:43:29 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1516 05:43:29 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1517 05:43:29 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1518 05:43:29 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1519 05:43:29 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1520 05:43:29 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1521 05:43:29 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1522 05:43:29 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1523 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1524 05:43:29 (0) ** 
.1525 05:43:29 (0) ** 6 error(s) 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons
.1526 05:43:29 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:
.1527 05:43:29 (0) **    - Failing WMI system components (see any missing WMI system files or DCOM registration
.1528 05:43:29 (0) **      issues previously mentioned).
.1529 05:43:29 (0) **    - Failing WMI providers (see any DCOM registration issues previously mentioned).
.1530 05:43:29 (0) **    - a WMI repository corruption.
.1531 05:43:29 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1532 05:43:29 (0) **      to validate the WMI repository operations.
.1533 05:43:29 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1534 05:43:29 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1535 05:43:29 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
.1536 05:43:29 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1537 05:43:29 (0) **      the WMI repository must be reconstructed.
.1538 05:43:29 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1539 05:43:29 (0) **          otherwise some applications may fail after the reconstruction.
.1540 05:43:29 (0) **          This can be achieved with the following command:
.1541 05:43:29 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1542 05:43:29 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1543 05:43:29 (0) **          ALL fixes previously mentioned.
.1544 05:43:29 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1545 05:43:29 (0) ** 
.1546 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1547 05:43:29 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1548 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1549 05:43:29 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 15 ERROR(S)!
.1550 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MFL (*)
.1551 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MOF (*)
.1552 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF
.1553 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IISWMI.MFL
.1554 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (*)
.1555 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (*)
.1556 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL (*)
.1557 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF (*)
.1558 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL (*)
.1559 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF (*)
.1560 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDSHBAAPI.MOF
.1561 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDSHBAREM.MOF
.1562 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL (*)
.1563 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF (*)
.1564 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WLBSPROV.MFL
.1565 05:43:29 (0) ** => After fixing all other issues previously mentioned, if the WMI repository is rebuilt,
.1566 05:43:29 (0) **    the listed MOF file(s) will not be recompiled, and therefore the definition they contain
.1567 05:43:29 (0) **    will not be available in the WMI repository.
.1568 05:43:29 (0) ** => You must manually recompile the MOF file(s) with the 'MOFCOMP.EXE <FileName.MOF>' command.
.1569 05:43:29 (0) ** => If you want the MOF file(s) to be part of the Auto-Recovery list, make sure the
.1570 05:43:29 (0) **    statement '#PRAGMA AUTORECOVER' is included.
.1571 05:43:29 (0) **    Note: MOF file(s) marked with (*) are NEVER included AT SETUP in the auto-recovery process.
.1572 05:43:29 (0) **          MOF file(s) containing UNINSTALL statements (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery process.
.1573 05:43:29 (0) **          Refer to the list of MOF files below NOT containing the '#PRAGMA AUTORECOVER' statement' for more information.
.1574 05:43:29 (0) ** 
.1575 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1576 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1577 05:43:29 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 17 FILE(S)!
.1578 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF
.1579 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (DELETE)
.1580 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (DELETE)
.1581 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL
.1582 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF
.1583 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL
.1584 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF
.1585 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDSHBAREM.MOF (DELETE)
.1586 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL
.1587 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF
.1588 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCM.MOF (DELETE) (*)
.1589 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MOF (*)
.1590 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MFL (*)
.1591 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLUSWMI.MOF (*)
.1592 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NLBMPROV.MOF (*)
.1593 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CMDEVTGPROV.MOF (*)
.1594 05:43:29 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WHQLPROV.MOF (*)
.1595 05:43:29 (0) ** => MOF file(s) marked with (*) are INCLUDED in the AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER' statement.
.1596 05:43:29 (0) **    If the WMI repository is rebuilt, the listed MOF files not included in the AUTO-RECOVERY LIST and
.1597 05:43:29 (0) **    missing the '#PRAGMA AUTORECOVERY' statement when they are compiled the first time will NOT
.1598 05:43:29 (0) **    be recompiled during the repository reconstruction.
.1599 05:43:29 (0) **    Note: If you want the MOF file to be part of the AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'
.1600 05:43:29 (0) **          is included and recompile the MOF/MFL with the following command:
.1601 05:43:29 (0) **          i.e. 'MOFCOMP.EXE <FileName.MOF>'
.1602 05:43:29 (0) ** ac
.1603 05:43:29 (0) ** => MOF file(s) marked with (DELETE) contains class and instance DELETE statements.
.1604 05:43:29 (0) **    Usually, MOF with DELETE statements are used to UNinstall components and they should NOT be listed in the AUTORECOVERY LIST
.1605 05:43:29 (0) **    and therefore they should NOT specify the '#PRAGMA AUTORECOVER' statement.
.1606 05:43:29 (0) **    Note: It happens that some MOF files do contain DELETE statements for installation purposes to delete
.1607 05:43:29 (0) **          existing information before it is recreated.
.1608 05:43:29 (0) ** 
.1609 05:43:29 (0) **    Note: It is also possible that the application implemented its own recovery mechanism.
.1610 05:43:29 (0) **          In that case, no action is required. You must verify with the application vendor
.1611 05:43:29 (0) **          if the application has this capability (i.e. Microsoft SMS)
.1612 05:43:29 (0) ** 
.1613 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1614 05:43:29 (0) ** 
.1615 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1616 05:43:29 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1617 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1618 05:43:29 (0) ** 
.1619 05:43:29 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_DELLSC1420_2009.09.22_05.42.52.LOG' for details.
.1620 05:43:29 (0) ** 
.1621 05:43:29 (0) ** WMIDiag v2.0 ended on 22 September 2009 at 05:43 (W:27 E:15 S:1).

           
         

20091111-EE-VQP-89 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. johnb6767178,417
2. nobus172,892
3. LeeTutor123,516
4. dstewartjr120,282
5. oBdA93,696
6. flubbster61,860
7. BillDL53,310
8. Merete52,363
9. demazter52,286
10. leew50,644
11. dbrunton48,999
12. torimar47,585
13. rindi47,245
14. Qlemo45,911
15. tigermatt44,719
16. Computer...41,190
17. andrew_...39,787
18. jcimarron39,654
19. Shift-338,602
20. thinkpads...32,739
21. arnold32,595
22. MASQUE...31,301
23. Chris-Dent31,290
24. houssam...30,625
25. SysExpert27,544

1. LeeTutor550,527
2. johnb6767525,196
3. nobus484,500
4. KCTS430,309
5. and235...298,068
6. leew236,418
7. sirbounty229,794
8. SysExpert207,041
9. oBdA204,500
10. rindi203,633
11. Sheharya...192,296
12. war1188,129
13. PUNKY174,021
14. orangutang171,954
15. tigermatt171,291
16. Merete167,609
17. Shift-3160,181
18. michko159,546
19. MrHusy154,737
20. rpggamer...145,022
21. willcomp135,888
22. dstewartjr130,592
23. jkr121,592
24. RobWill118,258
25. younghv116,163

WMI Initialization Failed, can't connect with root\cimv2 - how do I fix it?

Asked by wrguy in Microsoft Windows Operating Systems, Microsoft Applications, Windows 2003 Server

Tags: WMI, Initializaion Failure, .mof, WMIDIAG

About this solution