Question

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

Asked by: wrguy

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

.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).

                                  
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:

Select allOpen in new window

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-09-21 at 21:10:01ID24750496
Tags

WMI

,

Initializaion Failure

,

.mof

,

WMIDIAG

Topics

Microsoft Windows Operating Systems

,

Microsoft Applications

,

Windows 2003 Server

Participating Experts
2
Points
0
Comments
5

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. WMI ...
    Hi, I am looking for working example of WMI, can you help me ?
  2. WMI Security
    Hello Everyone, I apologize for my lack of knowledge in this area, I believe this is a problem with our WMI security. A developer at our company ran across this code on technet; strComputer = "atl-dc-01" Set objWMIService = GetObject("winmgmts:" _ & ...
  3. WMI... Remote execution
    HI, I want to execute an application on the remote machine using WMI in VC++ 6.0 ! can anybody help me please..
  4. GetObject("winmgmts:\\.\root\cimv2")
    More than one customer of mine is reporting a "Permission Denied" error number 70 when the following lines are executed: Dim objWMIService As Object Set objWMIService = GetObject("winmgmts:\\.\root\cimv2") These two lines are called within the "...
  5. WMI in VB6
    Hi, does anyone know why this vb6 code is displaying error "Automation error The specified module could not be found" when I put . (dot) in InputBox for my home PC References - Microsoft WMI Scripting V1.2 Library Sub Main() Dim strComputer Do strComputer = I...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: wrguyPosted on 2009-09-21 at 21:35:34ID: 25389508

I seemed to have solved my own problem here.  I just rebuilt the WMI repository using "rundll32 wbemupgd, RepairWMISetup", restarted the mgmt services and everything works peachy.  

 

by: AwinishPosted on 2009-09-21 at 21:36:15ID: 25389509

Create a FIXWMI.CMD batch file from the below script and run it and see if this corrects
your problem.

FIXWMI.CMD
------------------------

@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End

:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer

:SkipSrv
goto End

:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End

 

by: AwinishPosted on 2009-09-21 at 21:37:59ID: 25389514

Go to Start/Run/CMD and then run each of these hitting enter after each:

winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

This may or may not repair the repository but will re-install wmi into the
registry.]

 

by: wrguyPosted on 2009-09-21 at 21:53:34ID: 25389569

Thanks Awinish,  I didn't have a change to test your suggestion as I got it working fine by repairing (actually, rebuilding) the WMI repository.  If I run into further problems, I'll be sure to try your suggestion.

Regards,
wrguy

 

by: hasan1stPosted on 2009-10-11 at 02:15:30ID: 25545316

Worked like a charm, thanks for posting the solution.

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...