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