[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
08/05/2009 at 04:27PM PDT, ID: 24629899
[x]
Attachment Details
[x]
The Solution Rating System

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

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

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

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

Thank you!
7.0

WMI problem

Asked by ryan80 in Windows Management Instrumentation (WMI), Windows 2003 Server, Windows Installer

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? 
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:

.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).
[+][-]08/05/09 05:22 PM, ID: 25029170

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]08/05/09 08:44 PM, ID: 25029986

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]08/05/09 09:16 PM, ID: 25030088

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/05/09 09:23 PM, ID: 25030114

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]08/06/09 04:52 AM, ID: 25032171

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/06/09 07:57 AM, ID: 25034149

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/06/09 02:19 PM, ID: 25038183

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]08/06/09 02:36 PM, ID: 25038328

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/13/09 12:00 AM, ID: 25085925

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Windows Management Instrumentation (WMI), Windows 2003 Server, Windows Installer
Sign Up Now!
Solution Provided By: debuggerau
Participating Experts: 2
Solution Grade: B
 
 
[+][-]08/14/09 09:46 AM, ID: 25100026

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/17/09 08:40 AM, ID: 25115531

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/17/09 01:56 PM, ID: 25118336

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 30-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]08/17/09 02:47 PM, ID: 25118706

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]08/19/09 12:50 PM, ID: 25136620

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-91 - Hierarchy / EE_QW_3_20080625