Question

WMI problem

Asked by: ryan80

I am having issues installing my backup software on my server. I have narrowed it down to a WMI error, but do not know what to do with the log file that was created and how to solve it.

Here is the log file. Any ideas?

.1583 19:21:18 (0) ** WMIDiag v2.0 started on Wednesday, August 05, 2009 at 19:21.
.1584 19:21:18 (0) ** 
.1585 19:21:18 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1586 19:21:18 (0) ** 
.1587 19:21:18 (0) ** This script is not supported under any Microsoft standard support program or service.
.1588 19:21:18 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1589 19:21:18 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1590 19:21:18 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1591 19:21:18 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1592 19:21:18 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1593 19:21:18 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1594 19:21:18 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1595 19:21:18 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1596 19:21:18 (0) ** of the possibility of such damages.
.1597 19:21:18 (0) ** 
.1598 19:21:18 (0) ** 
.1599 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1600 19:21:18 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1601 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1602 19:21:18 (0) ** 
.1603 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1604 19:21:18 (0) ** Windows Server 2003 - Service pack 1 - 32-bit (3790) - User 'PALADINRPNJ\ADMIN' on computer 'APPS'.
.1605 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1606 19:21:18 (0) ** Environment: ........................................................................................................ OK..
.1607 19:21:18 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1608 19:21:18 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1609 19:21:18 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
.1610 19:21:18 (0) ** BEFORE running WMIDiag:
.1611 19:21:18 (0) ** The WMI repository has a size of: ................................................................................... 9 MB.
.1612 19:21:18 (0) ** - Disk free space on 'C:': .......................................................................................... 26606 MB.
.1613 19:21:18 (0) **   - INDEX.BTR,                     1712128 bytes,      9/26/2008 7:01:42 PM
.1614 19:21:18 (0) **   - MAPPING.VER,                   4 bytes,            9/26/2008 7:01:42 PM
.1615 19:21:18 (0) **   - MAPPING1.MAP,                  4572 bytes,         9/26/2008 6:26:43 PM
.1616 19:21:18 (0) **   - MAPPING2.MAP,                  4572 bytes,         8/5/2009 7:15:34 PM
.1617 19:21:18 (0) **   - OBJECTS.DATA,                  7495680 bytes,      9/26/2008 7:01:42 PM
.1618 19:21:18 (0) ** AFTER running WMIDiag:
.1619 19:21:18 (0) ** The WMI repository has a size of: ................................................................................... 9 MB.
.1620 19:21:18 (0) ** - Disk free space on 'C:': .......................................................................................... 26606 MB.
.1621 19:21:18 (0) **   - INDEX.BTR,                     1712128 bytes,      9/26/2008 7:01:42 PM
.1622 19:21:18 (0) **   - MAPPING.VER,                   4 bytes,            9/26/2008 7:01:42 PM
.1623 19:21:18 (0) **   - MAPPING1.MAP,                  4572 bytes,         9/26/2008 6:26:43 PM
.1624 19:21:18 (0) **   - MAPPING2.MAP,                  4572 bytes,         8/5/2009 7:15:34 PM
.1625 19:21:18 (0) **   - OBJECTS.DATA,                  7495680 bytes,      9/26/2008 7:01:42 PM
.1626 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1627 19:21:18 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
.1628 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1629 19:21:18 (0) ** DCOM Status: ........................................................................................................ OK.
.1630 19:21:18 (0) ** WMI registry setup: ................................................................................................. OK.
.1631 19:21:18 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
.1632 19:21:18 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Automatic')
.1633 19:21:18 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1634 19:21:18 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1635 19:21:18 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1636 19:21:18 (0) **          this can prevent the service/application to work as expected.
.1637 19:21:18 (0) ** 
.1638 19:21:18 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1639 19:21:18 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1640 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1641 19:21:18 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1642 19:21:18 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1643 19:21:18 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1644 19:21:18 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1645 19:21:18 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1646 19:21:18 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1647 19:21:18 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1648 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1649 19:21:18 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1650 19:21:18 (0) ** Overall WMI security status: ........................................................................................ OK.
.1651 19:21:18 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1652 19:21:18 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1653 19:21:18 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1654 19:21:18 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1655 19:21:18 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1656 19:21:18 (0) **    the performance counters with the WMI performance classes with the following commands:
.1657 19:21:18 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1658 19:21:18 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1659 19:21:18 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1660 19:21:18 (0) **    More information can be found on MSDN at:
.1661 19:21:18 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1662 19:21:18 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1663 19:21:18 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1664 19:21:18 (0) ** 
.1665 19:21:18 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1666 19:21:18 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1667 19:21:18 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1668 19:21:18 (0) ** - Root/Default, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1669 19:21:18 (0) ** - Root/CIMv2, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1670 19:21:18 (0) ** - Root/WMI, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1671 19:21:18 (0) ** 
.1672 19:21:18 (0) ** WMI GET operations: ................................................................................................. OK.
.1673 19:21:18 (0) ** WMI MOF representations: ............................................................................................ OK.
.1674 19:21:18 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1675 19:21:18 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1676 19:21:18 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1677 19:21:18 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1678 19:21:18 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1679 19:21:18 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1680 19:21:18 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1681 19:21:18 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1682 19:21:18 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1683 19:21:18 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1684 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1685 19:21:18 (0) ** 
.1686 19:21:18 (0) ** 6 error(s) 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons
.1687 19:21:18 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:
.1688 19:21:18 (0) **    - Failing WMI system components (see any missing WMI system files or DCOM registration
.1689 19:21:18 (0) **      issues previously mentioned).
.1690 19:21:18 (0) **    - Failing WMI providers (see any DCOM registration issues previously mentioned).
.1691 19:21:18 (0) **    - a WMI repository corruption.
.1692 19:21:18 (0) **      Under Windows XP 64-bit SP1, Windows 2003 SP1 and Windows Vista, the
.1693 19:21:18 (0) **      repository consistency is ALWAYS verified.
.1694 19:21:18 (0) **      Under Windows XP SP2, the repository consistency must be explicitly requested:
.1695 19:21:18 (0) **      i.e. 'WMIDiag CheckConsistency''
.1696 19:21:18 (0) **      Check the state of the repository above in the WMIDiag report.
.1697 19:21:18 (0) **      If the repository is inconsistent, it must be reconstructed.
.1698 19:21:18 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1699 19:21:18 (0) **          otherwise some applications may fail after the reconstruction.
.1700 19:21:18 (0) **          This can be achieved with the following command:
.1701 19:21:18 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1702 19:21:18 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1703 19:21:18 (0) **          ALL fixes previously mentioned.
.1704 19:21:18 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1705 19:21:18 (0) ** 
.1706 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1707 19:21:18 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1708 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1709 19:21:18 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 20 ERROR(S)!
.1710 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MFL (*)
.1711 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MOF (*)
.1712 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF
.1713 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (*)
.1714 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (*)
.1715 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLBASE.MOF
.1716 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPRO.MOF
.1717 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPROC.MOF
.1718 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPROCL.MFL
.1719 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPROCL.MOF
.1720 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPROU.MOF
.1721 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL (*)
.1722 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF (*)
.1723 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL (*)
.1724 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF (*)
.1725 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDSHBAAPI.MOF
.1726 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDSHBAREM.MOF
.1727 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL (*)
.1728 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF (*)
.1729 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WLBSPROV.MFL
.1730 19:21:18 (0) ** => After fixing all other issues previously mentioned, if the WMI repository is rebuilt,
.1731 19:21:18 (0) **    the listed MOF file(s) will not be recompiled, and therefore the definition they contain
.1732 19:21:18 (0) **    will not be available in the WMI repository.
.1733 19:21:18 (0) ** => You must manually recompile the MOF file(s) with the 'MOFCOMP.EXE <FileName.MOF>' command.
.1734 19:21:18 (0) ** => If you want the MOF file(s) to be part of the Auto-Recovery list, make sure the
.1735 19:21:18 (0) **    statement '#PRAGMA AUTORECOVER' is included.
.1736 19:21:18 (0) **    Note: MOF file(s) marked with (*) are NEVER included AT SETUP in the auto-recovery process.
.1737 19:21:18 (0) **          MOF file(s) containing UNINSTALL statements (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery process.
.1738 19:21:18 (0) **          Refer to the list of MOF files below NOT containing the '#PRAGMA AUTORECOVER' statement' for more information.
.1739 19:21:18 (0) ** 
.1740 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1741 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1742 19:21:18 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 21 FILE(S)!
.1743 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF
.1744 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (DELETE)
.1745 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (DELETE)
.1746 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLBASE.MOF
.1747 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPRO.MOF
.1748 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPROC.MOF
.1749 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLPROU.MOF
.1750 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL
.1751 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF
.1752 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL
.1753 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF
.1754 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDSHBAREM.MOF (DELETE)
.1755 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL
.1756 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF
.1757 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCM.MOF (DELETE) (*)
.1758 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MOF (*)
.1759 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MFL (*)
.1760 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLUSWMI.MOF (*)
.1761 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NLBMPROV.MOF (*)
.1762 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CMDEVTGPROV.MOF (*)
.1763 19:21:18 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WHQLPROV.MOF (*)
.1764 19:21:18 (0) ** => MOF file(s) marked with (*) are INCLUDED in the AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER' statement.
.1765 19:21:18 (0) **    If the WMI repository is rebuilt, the listed MOF files not included in the AUTO-RECOVERY LIST and
.1766 19:21:18 (0) **    missing the '#PRAGMA AUTORECOVERY' statement when they are compiled the first time will NOT
.1767 19:21:18 (0) **    be recompiled during the repository reconstruction.
.1768 19:21:18 (0) **    Note: If you want the MOF file to be part of the AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'
.1769 19:21:18 (0) **          is included and recompile the MOF/MFL with the following command:
.1770 19:21:18 (0) **          i.e. 'MOFCOMP.EXE <FileName.MOF>'
.1771 19:21:18 (0) ** 
.1772 19:21:18 (0) ** => MOF file(s) marked with (DELETE) contains class and instance DELETE statements.
.1773 19:21:18 (0) **    Usually, MOF with DELETE statements are used to UNinstall components and they should NOT be listed in the AUTORECOVERY LIST
.1774 19:21:18 (0) **    and therefore they should NOT specify the '#PRAGMA AUTORECOVER' statement.
.1775 19:21:18 (0) **    Note: It happens that some MOF files do contain DELETE statements for installation purposes to delete
.1776 19:21:18 (0) **          existing information before it is recreated.
.1777 19:21:18 (0) ** 
.1778 19:21:18 (0) **    Note: It is also possible that the application implemented its own recovery mechanism.
.1779 19:21:18 (0) **          In that case, no action is required. You must verify with the application vendor
.1780 19:21:18 (0) **          if the application has this capability (i.e. Microsoft SMS)
.1781 19:21:18 (0) ** 
.1782 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1783 19:21:18 (0) ** 
.1784 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1785 19:21:18 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1786 19:21:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1787 19:21:18 (0) ** 
.1788 19:21:18 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ADMIN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.SP1.32_APPS_2009.08.05_19.20.53.LOG' for details.
.1789 19:21:18 (0) ** 
.1790 19:21:18 (0) ** WMIDiag v2.0 ended on Wednesday, August 05, 2009 at 19:21 (W:38 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:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:

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-08-05 at 16:27:34ID24629899
Topics

Windows Management Instrumentation (WMI)

,

Windows 2003 Server

,

Windows Installer

Participating Experts
2
Points
500
Comments
15

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 problem
    I got a problem that I have researched quite a bit on the web and found many others with the same problem but no fix has been found. When I open System Information it says "Can't Collect Information Cannot access the Windows Management Instrumentation software. Window...
  2. WMI - generic failure - cannot backup repo
    we have windows 2000 sp4 + veritas backupexec. one day, we got an alert that the backup crashed with the message: Backup - C: SYSTEMAn error occurred retrieving the WMI Repository data directory. The WMI Repository could not be backed up. checked on veritas support, but not ...
  3. WMI Problems
    I am having WMI problems. This originally came up while trying to install SMS Client. When trying to install the log shows the following errors: MSI: Setup was unable to create the WMI namespace CCM The error code is 8007007F ccmsetup MSI: Warning 25101. Setup was unable to ...
  4. How to reset the WMI writer without restarting the computer
    After completing a successfull backup in Backup exec 12 the next backup fails with AOFO not enough disk space on the device running the AOFO to create an increment file. Most times this is an error. Other times it is an exception. I have been able to narrow it down to the ...
  5. WMI: Initialization failure
    Hi I have a SBS 2003 server running which has had several hiccups and is now running with no service packs except SBS 2003 SP1, it has not got Windows Server 2003 SP1 on it. I've tried to re-install SP 1 but it always fails. I've narrowed it down I believe to a WMI probl...
  6. WMI issue
    Hi, we have 2 2003 servers which are in workgroup and in the same network. We have a monitoring tool wich uses WMI to retrieve data, but this is not working for one server. When I run wbemtest.exe on the locla machines it works.But the problem is when I run wbemtest on the lo...

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: debuggerauPosted on 2009-08-05 at 17:22:30ID: 25029170

ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1655 19:21:18 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1656 19:21:18 (0) **    the performance counters with the WMI performance classes with the following commands:
.1657 19:21:18 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1658 19:21:18 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'

did you try this?

 

by: JonLambertPosted on 2009-08-05 at 20:44:52ID: 25029986

More often than not, WMI is not functioning because of a corrupted repository, you can try to rebuild the corrupted WMI repository on Windows Server 2003 with the following command.

rundll32 wbemupgd, RepairWMISetup

The following site has a good content on repairing WMI

http://rexcrisostomo.blogspot.com/2008/02/how-to-repair-wmi.html



 

by: ryan80Posted on 2009-08-05 at 21:16:55ID: 25030088

gave that a shot and it didnt work.

I am looking into it being a problem with a +com component. there is an acronig snapin to vss that seems to be giving errors. Not sure if I am looking in the right direction.

 

by: JonLambertPosted on 2009-08-05 at 21:23:25ID: 25030114

What sort of errors are you getting?

 

by: ryan80Posted on 2009-08-06 at 04:52:47ID: 25032171

Sorry John,

I have not tried repairing the repository yet. I had hit reply before you had posted. I will try the reposiroty shortly

 

by: ryan80Posted on 2009-08-06 at 07:57:10ID: 25034149

Ok I tried running that command to rebuild the repository. It took the command, but it did not seem to do anything. it finish in a fraction of a second. I would think that it would take a few second to rebuild a 9 MB file, but I really dont know.

However there are still the same errors in the WMI Diagnostics.

 

by: JonLambertPosted on 2009-08-06 at 14:19:02ID: 25038183

OK .. there are a couple of options.

You can retry completly rebuilding the repository by stoppint the WMI service, renaming the folder c:\Windows\System32\WBEM\Repository, and restarting the WMI service.  (I've seen plenty of situations with 'bad' Windows XP SP2 sysprep'd images, where we've needed to do this)

You can also try re-installing WMI by running rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

When I asked what sort of errors are you getting, I asked that in reference to the backup software?

 

by: ryan80Posted on 2009-08-06 at 14:36:42ID: 25038328

yes it was installing Acronis. however I believe that this was caused by another error. This error was most likely caused by the WMI problem. the VSS COM+  plugin for Acronis 9 never fully uninstalled. When I tried upgrading to Acronis 10 I was getting problems. I went through and deleted the registry keys that referenced the component causing the issues and deleted the component and it installed properly.

However there are still WMI errors, which could be what caused the problem in the first place. I am going to try to reinstall it tonight or tomorrow night. I got a full backup today, and will work on the WMI as soon as possible.

 

by: debuggerauPosted on 2009-08-13 at 00:00:10ID: 25085925

how'd you go?

 

by: ryan80Posted on 2009-08-14 at 09:46:36ID: 25100026

I ran the install and am waiting to restart it tonight to see if this resolved the issue.

 

by: ryan80Posted on 2009-08-17 at 08:40:21ID: 25115531

Sorry for the long delay. I restarted the server and still have errors coming up. Here is the error report. Looks like there are a lot of complaints about permissions users.

22829 11:34:33 (0) ** WMIDiag v2.0 started on Monday, August 17, 2009 at 11:31.
22830 11:34:33 (0) ** 
22831 11:34:33 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
22832 11:34:33 (0) ** 
22833 11:34:33 (0) ** This script is not supported under any Microsoft standard support program or service.
22834 11:34:33 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
22835 11:34:33 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
22836 11:34:33 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
22837 11:34:33 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
22838 11:34:33 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
22839 11:34:33 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
22840 11:34:33 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
22841 11:34:33 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
22842 11:34:33 (0) ** of the possibility of such damages.
22843 11:34:33 (0) ** 
22844 11:34:33 (0) ** 
22845 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22846 11:34:33 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
22847 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22848 11:34:33 (0) ** 
22849 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22850 11:34:33 (0) ** Windows Server 2003 - No service pack - 32-bit (3790) - User 'PALADINRPNJ\ADMIN' on computer 'APPS'.
22851 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22852 11:34:33 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
22853 11:34:33 (0) ** INFO: => 14 incorrect shutdown(s) detected on:
22854 11:34:33 (0) **          - Shutdown on 12 November 2007 12:08:05 (GMT+5).
22855 11:34:33 (0) **          - Shutdown on 12 November 2007 12:22:25 (GMT+5).
22856 11:34:33 (0) **          - Shutdown on 12 November 2007 12:31:00 (GMT+5).
22857 11:34:33 (0) **          - Shutdown on 12 November 2007 13:56:20 (GMT+5).
22858 11:34:33 (0) **          - Shutdown on 12 December 2007 13:10:04 (GMT+5).
22859 11:34:33 (0) **          - Shutdown on 25 March 2008 05:49:27 (GMT+4).
22860 11:34:33 (0) **          - Shutdown on 06 April 2008 09:13:18 (GMT+4).
22861 11:34:33 (0) **          - Shutdown on 09 May 2008 13:28:55 (GMT+4).
22862 11:34:33 (0) **          - Shutdown on 10 May 2008 12:27:55 (GMT+4).
22863 11:34:33 (0) **          - Shutdown on 06 July 2008 22:40:08 (GMT+4).
22864 11:34:33 (0) **          - Shutdown on 23 July 2008 20:29:44 (GMT+4).
22865 11:34:33 (0) **          - Shutdown on 28 September 2008 16:49:59 (GMT+4).
22866 11:34:33 (0) **          - Shutdown on 05 October 2008 18:12:34 (GMT+4).
22867 11:34:33 (0) **          - Shutdown on 28 January 2009 22:57:37 (GMT+5).
22868 11:34:33 (0) ** 
22869 11:34:33 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
22870 11:34:33 (0) ** Drive type: ......................................................................................................... SCSI (DELL PERC 5/i SCSI Disk Device).
22871 11:34:33 (0) ** There are no missing WMI system files: .............................................................................. OK.
22872 11:34:33 (0) ** There are no missing WMI repository files: .......................................................................... OK.
22873 11:34:33 (0) ** WMI repository state: ............................................................................................... N/A.
22874 11:34:33 (0) ** BEFORE running WMIDiag:
22875 11:34:33 (0) ** The WMI repository has a size of: ................................................................................... 9 MB.
22876 11:34:33 (0) ** - Disk free space on 'C:': .......................................................................................... 25641 MB.
22877 11:34:33 (0) **   - INDEX.BTR,                     1916928 bytes,      8/17/2009 4:39:28 AM
22878 11:34:33 (0) **   - MAPPING.VER,                   4 bytes,            8/17/2009 11:09:00 AM
22879 11:34:33 (0) **   - MAPPING1.MAP,                  4692 bytes,         8/17/2009 10:41:18 AM
22880 11:34:33 (0) **   - MAPPING2.MAP,                  4692 bytes,         8/17/2009 11:09:00 AM
22881 11:34:33 (0) **   - OBJECTS.DATA,                  7553024 bytes,      8/17/2009 4:39:28 AM
22882 11:34:33 (0) ** AFTER running WMIDiag:
22883 11:34:33 (0) ** The WMI repository has a size of: ................................................................................... 9 MB.
22884 11:34:33 (0) ** - Disk free space on 'C:': .......................................................................................... 25638 MB.
22885 11:34:33 (0) **   - INDEX.BTR,                     1916928 bytes,      8/17/2009 4:39:28 AM
22886 11:34:33 (0) **   - MAPPING.VER,                   4 bytes,            8/17/2009 11:09:00 AM
22887 11:34:33 (0) **   - MAPPING1.MAP,                  4692 bytes,         8/17/2009 10:41:18 AM
22888 11:34:33 (0) **   - MAPPING2.MAP,                  4692 bytes,         8/17/2009 11:09:00 AM
22889 11:34:33 (0) **   - OBJECTS.DATA,                  7553024 bytes,      8/17/2009 4:39:28 AM
22890 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22891 11:34:33 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
22892 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22893 11:34:33 (0) ** DCOM Status: ........................................................................................................ OK.
22894 11:34:33 (0) ** WMI registry setup: ................................................................................................. OK.
22895 11:34:33 (0) ** WMI Service has no dependents: ...................................................................................... OK.
22896 11:34:33 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
22897 11:34:33 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
22898 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22899 11:34:33 (0) ** WMI service DCOM setup: ............................................................................................. OK.
22900 11:34:33 (0) ** WMI components DCOM registrations: .................................................................................. OK.
22901 11:34:33 (0) ** WMI ProgID registrations: ........................................................................................... OK.
22902 11:34:33 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
22903 11:34:33 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
22904 11:34:33 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
22905 11:34:33 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
22906 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
22907 11:34:33 (0) ** WMI namespace security for 'ROOT/PERFMON': .......................................................................... MODIFIED.
22908 11:34:33 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
22909 11:34:33 (0) **        - REMOVED ACE:
22910 11:34:33 (0) **          ACEType:  &h0
22911 11:34:33 (0) **                    ACCESS_ALLOWED_ACE_TYPE
22912 11:34:33 (0) **          ACEFlags: &h12
22913 11:34:33 (0) **                    CONTAINER_INHERIT_ACE
22914 11:34:33 (0) **                    INHERITED_ACE
22915 11:34:33 (0) **          ACEMask:  &h23
22916 11:34:33 (0) **                    WBEM_ENABLE
22917 11:34:33 (0) **                    WBEM_METHOD_EXECUTE
22918 11:34:33 (0) **                    WBEM_REMOTE_ACCESS
22919 11:34:33 (0) ** 
22920 11:34:33 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
22921 11:34:33 (0) **    Removing default security will cause some operations to fail!
22922 11:34:33 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
22923 11:34:33 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
22924 11:34:33 (0) ** 
22925 11:34:33 (0) ** WMI namespace security for 'ROOT/ASPNET': ........................................................................... MODIFIED.
22926 11:34:33 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
22927 11:34:33 (0) **        - ACTUAL ACE:
22928 11:34:33 (0) **          ACEType:  &h0
22929 11:34:33 (0) **                    ACCESS_ALLOWED_ACE_TYPE
22930 11:34:33 (0) **          ACEFlags: &h12
22931 11:34:33 (0) **                    CONTAINER_INHERIT_ACE
22932 11:34:33 (0) **                    INHERITED_ACE
22933 11:34:33 (0) **          ACEMask:  &h13
22934 11:34:33 (0) **                    WBEM_ENABLE
22935 11:34:33 (0) **                    WBEM_METHOD_EXECUTE
22936 11:34:33 (0) **                    WBEM_WRITE_PROVIDER
22937 11:34:33 (0) **        - EXPECTED ACE:
22938 11:34:33 (0) **          ACEType:  &h0
22939 11:34:33 (0) **                    ACCESS_ALLOWED_ACE_TYPE
22940 11:34:33 (0) **          ACEFlags: &h12
22941 11:34:33 (0) **                    CONTAINER_INHERIT_ACE
22942 11:34:33 (0) **                    INHERITED_ACE
22943 11:34:33 (0) **          ACEMask:  &h33
22944 11:34:33 (0) **                    WBEM_ENABLE
22945 11:34:33 (0) **                    WBEM_METHOD_EXECUTE
22946 11:34:33 (0) **                    WBEM_WRITE_PROVIDER
22947 11:34:33 (0) **                    WBEM_REMOTE_ACCESS
22948 11:34:33 (0) ** 
22949 11:34:33 (0) ** => The actual ACE has the right(s) '&h20 WBEM_REMOTE_ACCESS' removed!
22950 11:34:33 (0) **    This will cause some operations to fail!
22951 11:34:33 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
22952 11:34:33 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
22953 11:34:33 (0) ** 
22954 11:34:33 (0) ** WMI namespace security for 'ROOT/ASPNET': ........................................................................... MODIFIED.
22955 11:34:33 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
22956 11:34:33 (0) **        - ACTUAL ACE:
22957 11:34:33 (0) **          ACEType:  &h0
22958 11:34:33 (0) **                    ACCESS_ALLOWED_ACE_TYPE
22959 11:34:33 (0) **          ACEFlags: &h12
22960 11:34:33 (0) **                    CONTAINER_INHERIT_ACE
22961 11:34:33 (0) **                    INHERITED_ACE
22962 11:34:33 (0) **          ACEMask:  &h13
22963 11:34:33 (0) **                    WBEM_ENABLE
22964 11:34:33 (0) **                    WBEM_METHOD_EXECUTE
22965 11:34:33 (0) **                    WBEM_WRITE_PROVIDER
22966 11:34:33 (0) **        - EXPECTED ACE:
22967 11:34:33 (0) **          ACEType:  &h0
22968 11:34:33 (0) **                    ACCESS_ALLOWED_ACE_TYPE
22969 11:34:33 (0) **          ACEFlags: &h12
22970 11:34:33 (0) **                    CONTAINER_INHERIT_ACE
22971 11:34:33 (0) **                    INHERITED_ACE
22972 11:34:33 (0) **          ACEMask:  &h33
22973 11:34:33 (0) **                    WBEM_ENABLE
22974 11:34:33 (0) **                    WBEM_METHOD_EXECUTE
22975 11:34:33 (0) **                    WBEM_WRITE_PROVIDER
22976 11:34:33 (0) **                    WBEM_REMOTE_ACCESS
22977 11:34:33 (0) ** 
22978 11:34:33 (0) ** => The actual ACE has the right(s) '&h20 WBEM_REMOTE_ACCESS' removed!
22979 11:34:33 (0) **    This will cause some operations to fail!
22980 11:34:33 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
22981 11:34:33 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
22982 11:34:33 (0) ** 
22983 11:34:33 (0) ** 
22984 11:34:33 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
22985 11:34:33 (0) ** DCOM security error(s) detected: .................................................................................... 0.
22986 11:34:33 (0) ** WMI security warning(s) detected: ................................................................................... 0.
22987 11:34:33 (0) ** WMI security error(s) detected: ..................................................................................... 3.
22988 11:34:33 (0) ** 
22989 11:34:33 (0) ** Overall DCOM security status: ....................................................................................... OK.
22990 11:34:33 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
22991 11:34:33 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
22992 11:34:33 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 54.
22993 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA44".
22994 11:34:33 (0) **   'select * from MSMCAEvent_InvalidError where (type = 2147811432) and (LogToEventlog <> 0)'
22995 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA23".
22996 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553235) and (LogToEventlog <> 0)'
22997 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA32".
22998 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811420) and (LogToEventlog <> 0)'
22999 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA14".
23000 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 2147811402) and (LogToEventlog <> 0)'
23001 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA37".
23002 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553249) and (LogToEventlog <> 0)'
23003 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
23004 11:34:33 (0) **   'select * from MSFT_SCMEventLogEvent'
23005 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA5".
23006 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 3221553217) and (LogToEventlog <> 0)'
23007 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA18".
23008 11:34:33 (0) **   'select * from MSMCAEvent_SystemEventError where (type = 2147811406) and (LogToEventlog <> 0)'
23009 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA3".
23010 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 3221553215) and (LogToEventlog <> 0)'
23011 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA41".
23012 11:34:33 (0) **   'select * from MSMCAEvent_SMBIOSError where (type = 3221553253) and (LogToEventlog <> 0)'
23013 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA26".
23014 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811414) and (LogToEventlog <> 0)'
23015 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA36".
23016 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811424) and (LogToEventlog <> 0)'
23017 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA9".
23018 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 3221553221) and (LogToEventlog <> 0) and not ((MSSid = 0) and ((MsOp <> 3) or (MSOp <> 4)))'
23019 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA10".
23020 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 2147811398) and (LogToEventlog <> 0)'
23021 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA17".
23022 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 3221553229) and (LogToEventlog <> 0)'
23023 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA1".
23024 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 3221553213) and (LogToEventlog <> 0)'
23025 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA42".
23026 11:34:33 (0) **   'select * from MSMCAEvent_PlatformSpecificError where (type = 2147811430) and (LogToEventlog <> 0)'
23027 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA4".
23028 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 2147811392) and (LogToEventlog <> 0)'
23029 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA25".
23030 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553237) and (LogToEventlog <> 0)'
23031 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA49".
23032 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (MajorErrorType = 4) and (MSSid = 0) and (MSOp = 4) and (LogToEventlog <> 0)'
23033 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA27".
23034 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553239) and (LogToEventlog <> 0)'
23035 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA45".
23036 11:34:33 (0) **   'select * from MSMCAEvent_InvalidError where (type = 3221553257) and (LogToEventlog <> 0)'
23037 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA8".
23038 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 2147811396) and (LogToEventlog <> 0) and not ((MSSid = 0) and ((MsOp <> 3) or (MSOp <> 4)))'
23039 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA40".
23040 11:34:33 (0) **   'select * from MSMCAEvent_SMBIOSError where (type = 2147811428) and (LogToEventlog <> 0)'
23041 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA39".
23042 11:34:33 (0) **   'select * from MSMCAEvent_PCIComponentError where (type = 3221553251) and (LogToEventlog <> 0)'
23043 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA29".
23044 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553241) and (LogToEventlog <> 0)'
23045 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA20".
23046 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811408) and (LogToEventlog <> 0)'
23047 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA48".
23048 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (MajorErrorType = 4) and (MSSid = 0) and (MSOp = 3) and (LogToEventlog <> 0)'
23049 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA28".
23050 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811416) and (LogToEventlog <> 0)'
23051 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA33".
23052 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553245) and (LogToEventlog <> 0)'
23053 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA7".
23054 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 3221553219) and (LogToEventlog <> 0)'
23055 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA16".
23056 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 2147811404) and (LogToEventlog <> 0)'
23057 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA43".
23058 11:34:33 (0) **   'select * from MSMCAEvent_PlatformSpecificError where (type = 3221553255) and (LogToEventlog <> 0)'
23059 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA21".
23060 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553233) and (LogToEventlog <> 0)'
23061 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA6".
23062 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 2147811394) and (LogToEventlog <> 0)'
23063 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA31".
23064 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553243) and (LogToEventlog <> 0)'
23065 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA12".
23066 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 2147811400) and (LogToEventlog <> 0)'
23067 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA46".
23068 11:34:33 (0) **   'select * from MSMCAEvent_InvalidError where (type = 2147811434) and (LogToEventlog <> 0)'
23069 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA47".
23070 11:34:33 (0) **   'select * from MSMCAEvent_InvalidError where (type = 3221553259) and (LogToEventlog <> 0)'
23071 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA35".
23072 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 3221553247) and (LogToEventlog <> 0)'
23073 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA0".
23074 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 2147811388) and (LogToEventlog <> 0)'
23075 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA19".
23076 11:34:33 (0) **   'select * from MSMCAEvent_SystemEventError where (type = 3221553231) and (LogToEventlog <> 0)'
23077 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA11".
23078 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 3221553223) and (LogToEventlog <> 0)'
23079 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA52".
23080 11:34:33 (0) **   'select * from MSMCAEvent_MemoryPageRemoved'
23081 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA30".
23082 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811418) and (LogToEventlog <> 0)'
23083 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA15".
23084 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 3221553227) and (LogToEventlog <> 0)'
23085 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA38".
23086 11:34:33 (0) **   'select * from MSMCAEvent_PCIComponentError where (type = 2147811426) and (LogToEventlog <> 0)'
23087 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA34".
23088 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811422) and (LogToEventlog <> 0)'
23089 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA2".
23090 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 2147811390) and (LogToEventlog <> 0)'
23091 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA22".
23092 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811410) and (LogToEventlog <> 0)'
23093 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA13".
23094 11:34:33 (0) **   'select * from MSMCAEvent_MemoryError where (type = 3221553225) and (LogToEventlog <> 0)'
23095 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA50".
23096 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 2147811441) and (LogToEventlog <> 0)'
23097 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA51".
23098 11:34:33 (0) **   'select * from MSMCAEvent_CPUError where (type = 3221553266) and (LogToEventlog <> 0)'
23099 11:34:33 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="MCA24".
23100 11:34:33 (0) **   'select * from MSMCAEvent_PCIBusError where (type = 2147811412) and (LogToEventlog <> 0)'
23101 11:34:33 (0) ** 
23102 11:34:33 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
23103 11:34:33 (0) ** WMI ADAP status: .................................................................................................... OK.
23104 11:34:33 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
23105 11:34:33 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
23106 11:34:33 (0) ** WMI GET operations: ................................................................................................. OK.
23107 11:34:33 (0) ** WMI MOF representations: ............................................................................................ OK.
23108 11:34:33 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
23109 11:34:33 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
23110 11:34:33 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
23111 11:34:33 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
23112 11:34:33 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
23113 11:34:33 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
23114 11:34:33 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
23115 11:34:33 (0) ** WMI static instances retrieved: ..................................................................................... 1255.
23116 11:34:33 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
23117 11:34:33 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
23118 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23119 11:34:33 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
23120 11:34:33 (0) **   DCOM: ............................................................................................................. 52.
23121 11:34:33 (0) **   WINMGMT: .......................................................................................................... 44.
23122 11:34:33 (0) **   WMIADAPTER: ....................................................................................................... 0.
23123 11:34:33 (0) ** => Verify the WMIDiag LOG at line #21920 for more details.
23124 11:34:33 (0) ** 
23125 11:34:33 (0) ** # of additional Event Log events AFTER WMIDiag execution:
23126 11:34:33 (0) **   DCOM: ............................................................................................................. 0.
23127 11:34:33 (0) **   WINMGMT: .......................................................................................................... 0.
23128 11:34:33 (0) **   WMIADAPTER: ....................................................................................................... 0.
23129 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23130 11:34:33 (0) ** WMI Registry key setup: ............................................................................................. OK.
23131 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23132 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23133 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23134 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23135 11:34:33 (0) ** 
23136 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23137 11:34:33 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
23138 11:34:33 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
23139 11:34:33 (0) ** 
23140 11:34:33 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ADMIN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_APPS_2009.08.17_11.31.21.LOG' for details.
23141 11:34:33 (0) ** 
23142 11:34:33 (0) ** WMIDiag v2.0 ended on Monday, August 17, 2009 at 11:34 (W:67 E:4 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:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:
209:
210:
211:
212:
213:
214:
215:
216:
217:
218:
219:
220:
221:
222:
223:
224:
225:
226:
227:
228:
229:
230:
231:
232:
233:
234:
235:
236:
237:
238:
239:
240:
241:
242:
243:
244:
245:
246:
247:
248:
249:
250:
251:
252:
253:
254:
255:
256:
257:
258:
259:
260:
261:
262:
263:
264:
265:
266:
267:
268:
269:
270:
271:
272:
273:
274:
275:
276:
277:
278:
279:
280:
281:
282:
283:
284:
285:
286:
287:
288:
289:
290:
291:
292:
293:
294:
295:
296:
297:
298:
299:
300:
301:
302:
303:
304:
305:
306:
307:
308:
309:
310:
311:
312:
313:
314:

Select allOpen in new window

 

by: JonLambertPosted on 2009-08-17 at 13:56:50ID: 25118336

Have you tried adding the missing  security rights back using WinMgmt.msc?

 

by: ryan80Posted on 2009-08-17 at 14:47:52ID: 25118706

havnt yet, was planning on it tonight, but a clients server just went down so I may not be able to today. however I will do that in the next day or two.

 

by: ryan80Posted on 2009-08-19 at 12:50:36ID: 25136620

Ok, so I went into wmimgmt.msc and went to add the entry for the listed WMI namespaces. However I was not able to add the security groups that it said were missing.

I am thinking that maybe there is a security policy that is causing problems with adding these groups.  I looked in a local security policy about allowing those users to DCOM control, but I am not sure that is what I need to do. This is what I changed:

I enabled:
windows settings -> security settings -> local policies -> security options ->
DCOM: Machine access restrictions -> policy setting -> check Define this policy setting and took defaults plus added the security groups

 

by: ryan80Posted on 2009-09-09 at 11:50:49ID: 31612196

eliminated some of the issues, but others still there.

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