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 problem as the WMI is failing with WMI: Initialization failure.
 
Tried various solutions but I'm stuck now.
 
See below for WMIdiag report. Any advice would be great as I'm lost really, step by step guide on how to rebuild the MOF files etc would be great.
 
Thanks
 
Mike
 
Report Below
 
 
.1478 19:39:28 (0) ** WMIDiag v2.0 started on 24 April 2008 at 19:39.
.1479 19:39:28 (0) **
.1480 19:39:28 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1481 19:39:28 (0) **
.1482 19:39:28 (0) ** This script is not supported under any Microsoft standard support program or service.
.1483 19:39:28 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1484 19:39:28 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1485 19:39:28 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1486 19:39:28 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1487 19:39:28 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1488 19:39:28 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1489 19:39:28 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1490 19:39:28 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1491 19:39:28 (0) ** of the possibility of such damages.
.1492 19:39:28 (0) **
.1493 19:39:28 (0) **
.1494 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1495 19:39:28 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1496 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1497 19:39:28 (0) **
.1498 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1499 19:39:28 (0) ** Windows Server 2003 - No service pack - 32-bit (3790) - User 'SPRINGFIELDMIND\ADMINISTRATOR' on computer 'SPRINGSERVER'.
.1500 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1501 19:39:28 (0) ** Environment: ........................................................................................................ OK..
.1502 19:39:28 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1503 19:39:28 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1504 19:39:28 (0) ** WMI repository state: ............................................................................................... N/A.
.1505 19:39:28 (0) ** BEFORE running WMIDiag:
.1506 19:39:28 (0) ** The WMI repository has a size of: ................................................................................... 14 MB.
.1507 19:39:28 (0) ** - Disk free space on 'C:': .......................................................................................... 129980 MB.
.1508 19:39:28 (0) **   - INDEX.BTR,                     2498560 bytes,      06/07/2006 09:05:31
.1509 19:39:28 (0) **   - MAPPING.VER,                   4 bytes,            06/07/2006 09:05:32
.1510 19:39:28 (0) **   - MAPPING1.MAP,                  7648 bytes,         06/07/2006 09:05:32
.1511 19:39:28 (0) **   - MAPPING2.MAP,                  7648 bytes,         24/04/2008 19:19:03
.1512 19:39:28 (0) **   - OBJECTS.DATA,                  12509184 bytes,     06/07/2006 09:05:30
.1513 19:39:28 (0) ** AFTER running WMIDiag:
.1514 19:39:28 (0) ** The WMI repository has a size of: ................................................................................... 14 MB.
.1515 19:39:28 (0) ** - Disk free space on 'C:': .......................................................................................... 129979 MB.
.1516 19:39:28 (0) **   - INDEX.BTR,                     2498560 bytes,      06/07/2006 09:05:31
.1517 19:39:28 (0) **   - MAPPING.VER,                   4 bytes,            06/07/2006 09:05:32
.1518 19:39:28 (0) **   - MAPPING1.MAP,                  7648 bytes,         06/07/2006 09:05:32
.1519 19:39:28 (0) **   - MAPPING2.MAP,                  7648 bytes,         24/04/2008 19:19:03
.1520 19:39:28 (0) **   - OBJECTS.DATA,                  12509184 bytes,     06/07/2006 09:05:30
.1521 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1522 19:39:28 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.1523 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1524 19:39:28 (0) ** DCOM Status: ........................................................................................................ OK.
.1525 19:39:28 (0) ** WMI registry setup: ................................................................................................. OK.
.1526 19:39:28 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
.1527 19:39:28 (0) ** - Exchange Management Service (MSEXCHANGEMGMT, StartMode='Automatic')
.1528 19:39:28 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1529 19:39:28 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1530 19:39:28 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1531 19:39:28 (0) **          this can prevent the service/application to work as expected.
.1532 19:39:28 (0) **
.1533 19:39:28 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1534 19:39:28 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1535 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1536 19:39:28 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1537 19:39:28 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1538 19:39:28 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1539 19:39:28 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1540 19:39:28 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1541 19:39:28 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1542 19:39:28 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1543 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1544 19:39:28 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1545 19:39:28 (0) ** Overall WMI security status: ........................................................................................ OK.
.1546 19:39:28 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1547 19:39:28 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1548 19:39:28 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1549 19:39:28 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1550 19:39:28 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1551 19:39:28 (0) **    the performance counters with the WMI performance classes with the following commands:
.1552 19:39:28 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1553 19:39:28 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1554 19:39:28 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1555 19:39:28 (0) **    More information can be found on MSDN at:
.1556 19:39:28 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1557 19:39:28 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1558 19:39:28 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1559 19:39:28 (0) **
.1560 19:39:28 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1561 19:39:28 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1562 19:39:28 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1563 19:39:28 (0) ** - Root/Default, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1564 19:39:28 (0) ** - Root/CIMv2, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1565 19:39:28 (0) ** - Root/WMI, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1566 19:39:28 (0) **
.1567 19:39:28 (0) ** WMI GET operations: ................................................................................................. OK.
.1568 19:39:28 (0) ** WMI MOF representations: ............................................................................................ OK.
.1569 19:39:28 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1570 19:39:28 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1571 19:39:28 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1572 19:39:28 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1573 19:39:28 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1574 19:39:28 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1575 19:39:28 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1576 19:39:28 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1577 19:39:28 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1578 19:39:28 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1579 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1580 19:39:28 (0) **
.1581 19:39:28 (0) ** 6 error(s) 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons
.1582 19:39:28 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:
.1583 19:39:28 (0) **    - Failing WMI system components (see any missing WMI system files or DCOM registration
.1584 19:39:28 (0) **      issues previously mentioned).
.1585 19:39:28 (0) **    - Failing WMI providers (see any DCOM registration issues previously mentioned).
.1586 19:39:28 (0) **    - a WMI repository corruption.
.1587 19:39:28 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1588 19:39:28 (0) **      to validate the WMI repository operations.
.1589 19:39:28 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1590 19:39:28 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1591 19:39:28 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
.1592 19:39:28 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1593 19:39:28 (0) **      the WMI repository must be reconstructed.
.1594 19:39:28 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1595 19:39:28 (0) **          otherwise some applications may fail after the reconstruction.
.1596 19:39:28 (0) **          This can be achieved with the following command:
.1597 19:39:28 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1598 19:39:28 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1599 19:39:28 (0) **          ALL fixes previously mentioned.
.1600 19:39:28 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1601 19:39:28 (0) **
.1602 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1603 19:39:28 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1604 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1605 19:39:28 (0) ** No MOF file referenced in the Auto-Recovery list is missing: ........................................................ OK.
.1606 19:39:28 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 16 ERROR(S)!
.1607 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MFL (*)
.1608 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MOF (*)
.1609 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF
.1610 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSPROV.MOF
.1611 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EXMGMT.MOF
.1612 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EXWMI.MOF
.1613 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MSGTRK.MOF
.1614 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (*)
.1615 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (*)
.1616 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL (*)
.1617 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF (*)
.1618 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL (*)
.1619 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF (*)
.1620 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL (*)
.1621 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF (*)
.1622 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WLBSPROV.MFL
.1623 19:39:28 (0) ** => After fixing all other issues previously mentioned, if the WMI repository is rebuilt,
.1624 19:39:28 (0) **    the listed MOF file(s) will not be recompiled, and therefore the definition they contain
.1625 19:39:28 (0) **    will not be available in the WMI repository.
.1626 19:39:28 (0) ** => You must manually recompile the MOF file(s) with the 'MOFCOMP.EXE ' command.
.1627 19:39:28 (0) ** => If you want the MOF file(s) to be part of the Auto-Recovery list, make sure the
.1628 19:39:28 (0) **    statement '#PRAGMA AUTORECOVER' is included.
.1629 19:39:28 (0) **    Note: MOF file(s) marked with (*) are NEVER included AT SETUP in the auto-recovery process.
.1630 19:39:28 (0) **          MOF file(s) containing UNINSTALL statements (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery process.
.1631 19:39:28 (0) **          Refer to the list of MOF files below NOT containing the '#PRAGMA AUTORECOVER' statement' for more information.
.1632 19:39:28 (0) **
.1633 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1634 19:39:28 (0) ** WMI provider MOF files are available: ............................................................................... OK.
.1635 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1636 19:39:28 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 26 FILE(S)!
.1637 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MFL
.1638 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MOF
.1639 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF
.1640 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSPROV.MOF
.1641 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EXMGMT.MOF
.1642 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EXWMI.MOF
.1643 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\MSGTRK.MOF
.1644 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (DELETE)
.1645 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (DELETE)
.1646 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL
.1647 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF
.1648 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL
.1649 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF
.1650 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL
.1651 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF
.1652 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCM.MOF (DELETE) (*)
.1653 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MOF (*)
.1654 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MFL (*)
.1655 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLI.MOF (*)
.1656 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLUSWMI.MOF (*)
.1657 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NLBMPROV.MOF (*)
.1658 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CMDEVTGPROV.MOF (*)
.1659 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WHQLPROV.MOF (*)
.1660 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\INETSRV\W3CORE.MOF (*)
.1661 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\INETSRV\W3ISAPI.MOF (*)
.1662 19:39:28 (0) ** - C:\WINDOWS\SYSTEM32\INETSRV\ASP.MOF (*)
.1663 19:39:28 (0) ** => MOF file(s) marked with (*) are INCLUDED in the AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER' statement.
.1664 19:39:28 (0) **    If the WMI repository is rebuilt, the listed MOF files not included in the AUTO-RECOVERY LIST and
.1665 19:39:28 (0) **    missing the '#PRAGMA AUTORECOVERY' statement when they are compiled the first time will NOT
.1666 19:39:28 (0) **    be recompiled during the repository reconstruction.
.1667 19:39:28 (0) **    Note: If you want the MOF file to be part of the AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'
.1668 19:39:28 (0) **          is included and recompile the MOF/MFL with the following command:
.1669 19:39:28 (0) **          i.e. 'MOFCOMP.EXE '
.1670 19:39:28 (0) **
.1671 19:39:28 (0) ** => MOF file(s) marked with (DELETE) contains class and instance DELETE statements.
.1672 19:39:28 (0) **    Usually, MOF with DELETE statements are used to UNinstall components and they should NOT be listed in the AUTORECOVERY LIST
.1673 19:39:28 (0) **    and therefore they should NOT specify the '#PRAGMA AUTORECOVER' statement.
.1674 19:39:28 (0) **    Note: It happens that some MOF files do contain DELETE statements for installation purposes to delete
.1675 19:39:28 (0) **          existing information before it is recreated.
.1676 19:39:28 (0) **
.1677 19:39:28 (0) **    Note: It is also possible that the application implemented its own recovery mechanism.
.1678 19:39:28 (0) **          In that case, no action is required. You must verify with the application vendor
.1679 19:39:28 (0) **          if the application has this capability (i.e. Microsoft SMS)
.1680 19:39:28 (0) **
.1681 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1682 19:39:28 (0) **
.1683 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1684 19:39:28 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1685 19:39:28 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1686 19:39:28 (0) **
.1687 19:39:28 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_SPRINGSERVER_2008.04.24_19.39.11.LOG' for details.
.1688 19:39:28 (0) **
.1689 19:39:28 (0) ** WMIDiag v2.0 ended on 24 April 2008 at 19:39 (W:36 E:15 S:1).Start Free Trial