Jump to content

dial a fix error?


richrd

Recommended Posts

I could use some help. I have a dell with 2003 standard on it - trying to fix the wmi/wbem, when I run "reset wmi/wbem" it crashes at "registering wbem\fastprox.dll..." with the error message "Access violation at address 77B914CD in module'version.dll. Read of address 00000004."

I am using the current version downloaded tonight from the lunarsoft site.

Can anybody help. my server is essentially down.

Thanks

Rich

post-1633-127510132197_thumb.png

Link to comment
Share on other sites

Welcome to Lunarsoft richrd.

You may wish to refer to this post.

So your saying to perform the following for my "windows 2003 server";

1. Log in as a local administrator on the machine.

2. If possible, configure antivirus so it does not scan any of the files of subfolders of "%windir%\system32\wbem\repository".

3. Execute the following batch file to clear out the existing repository and autorecovery cache"

%systemdrive%

cd %windir%\system32\wbem

sc config winmgmt start= disabled

net stop winmgmt /y

if exist repository.old rmdir /s/q repository.old

rename repository repository.old

if exist autorecover.old rmdir /s/q autorecover.old

rename autorecover autorecover.old

md autorecover

4. Export the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM" to a REG file for backup (i.e. WBEM_org.REG). Then Import the following REG file to set the WBEM logging level to verbose, increase the maximum log size to 5 MB, and clear out the autorecovery list:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM]

"Logging"="2"

"Log File Max Size"="5000000"

"Autorecover MOFs"=hex(7):00,00

"Autorecover MOFs timestamp"=""

5. Execute the following batch file to rebuild the repository and autorecovery list. The duplicate lines are intentional. This batch file can take several minutes to complete:

%systemdrive%

cd %windir%\system32\wbem

sc config winmgmt start= auto

for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s

for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s

for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s

WINMGMT.EXE /REGSERVER

WINMGMT.EXE /CLEARADAP

WINMGMT.EXE /RESYNCPERF

6. Wait approx 15 minutes after running the above batch file to allow the performance counter resynchronization to complete. Then run WMIDIAG (cscript wmidiag.vbs) to establish a baseline report. The latest public version of WMIDIAG can be obtained from the following URL:

http://www.microsoft...;displaylang=en

7. Execute the following batch file to clear out the WBEM logs:

%systemdrive%

cd %windir%\system32\wbem\logs

del /Q *.*

Link to comment
Share on other sites

Welcome to Lunarsoft richrd.

You may wish to refer to this post.

I followed the instructions to the letter and got the following from wmidiag...

.1648 14:31:40 (0) ** WMIDiag v2.0 started on Monday, May 31, 2010 at 14:31.

.1649 14:31:40 (0) **

.1650 14:31:40 (0) ** Copyright © Microsoft Corporation. All rights reserved - January 2007.

.1651 14:31:40 (0) **

.1652 14:31:40 (0) ** This script is not supported under any Microsoft standard support program or service.

.1653 14:31:40 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all

.1654 14:31:40 (0) ** implied warranties including, without limitation, any implied warranties of merchantability

.1655 14:31:40 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance

.1656 14:31:40 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,

.1657 14:31:40 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for

.1658 14:31:40 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,

.1659 14:31:40 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of

.1660 14:31:40 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised

.1661 14:31:40 (0) ** of the possibility of such damages.

.1662 14:31:40 (0) **

.1663 14:31:40 (0) **

.1664 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1665 14:31:40 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------

.1666 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1667 14:31:40 (0) **

.1668 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1669 14:31:40 (0) ** Windows Server 2003 - Service pack 1 - 32-bit (3790) - User 'ADMINISTRATOR' on computer 'DELLSRV'.

.1670 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1671 14:31:40 (0) ** Environment: ........................................................................................................ OK..

.1672 14:31:40 (0) ** There are no missing WMI system files: .............................................................................. OK.

.1673 14:31:40 (0) ** There are no missing WMI repository files: .......................................................................... OK.

.1674 14:31:40 (1) !! ERROR: WMI repository state: ........................................................................................ ERROR (INCONSISTENT)!

.1675 14:31:40 (0) ** => To fix this issue and if you do not want WMI to rebuild

.1676 14:31:40 (0) ** the WMI repository, then you must restore the WMI repository from a previous backup.

.1677 14:31:40 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of

.1678 14:31:40 (0) ** of the WMI repository.

.1679 14:31:40 (0) ** => If no backup is available, you must rebuild the repository.

.1680 14:31:40 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,

.1681 14:31:40 (0) ** otherwise some applications may fail after the reconstruction.

.1682 14:31:40 (0) ** This can be achieved with the following command:

.1683 14:31:40 (0) ** i.e. 'WMIDiag ShowMOFErrors'

.1684 14:31:40 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery

.1685 14:31:40 (0) ** registry key will be excluded from the WMI repository reconstruction.

.1686 14:31:40 (0) ** This may imply the lost of WMI registration information.

.1687 14:31:40 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing

.1688 14:31:40 (0) ** ALL fixes previously mentioned.

.1689 14:31:40 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)

.1690 14:31:40 (0) ** => To rebuild the WMI repository, you must:

.1691 14:31:40 (0) ** - Stop the WMI Service.

.1692 14:31:40 (0) ** i.e. 'NET.EXE STOP WINMGMT'

.1693 14:31:40 (0) ** - Move the existing WMI repository files to another location.

.1694 14:31:40 (0) ** i.e. MOVE C:\WINDOWS\SYSTEM32\WBEM\Repository\FS\*.* %TEMP%

.1695 14:31:40 (0) ** - Start the WMI Service.

.1696 14:31:40 (0) ** i.e. 'NET.EXE START WINMGMT'

.1697 14:31:40 (0) ** WMI will rebuild the WMI repository based the auto-recovery mechanism.

.1698 14:31:40 (0) **

.1699 14:31:40 (0) ** BEFORE running WMIDiag:

.1700 14:31:40 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.

.1701 14:31:40 (0) ** - Disk free space on 'C:': .......................................................................................... 10924 MB.

.1702 14:31:40 (0) ** - INDEX.BTR, 16384 bytes, 5/31/2010 2:06:54 PM

.1703 14:31:40 (0) ** - MAPPING.VER, 4 bytes, 5/31/2010 2:06:54 PM

.1704 14:31:40 (0) ** - MAPPING1.MAP, 0 bytes, 5/31/2010 2:06:54 PM

.1705 14:31:40 (0) ** - MAPPING2.MAP, 60 bytes, 5/31/2010 2:06:54 PM

.1706 14:31:40 (0) ** - OBJECTS.DATA, 8192 bytes, 5/31/2010 2:06:54 PM

.1707 14:31:40 (0) ** AFTER running WMIDiag:

.1708 14:31:40 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.

.1709 14:31:40 (0) ** - Disk free space on 'C:': .......................................................................................... 10924 MB.

.1710 14:31:40 (0) ** - INDEX.BTR, 16384 bytes, 5/31/2010 2:06:54 PM

.1711 14:31:40 (0) ** - MAPPING.VER, 4 bytes, 5/31/2010 2:31:40 PM

.1712 14:31:40 (0) ** - MAPPING1.MAP, 60 bytes, 5/31/2010 2:31:40 PM

.1713 14:31:40 (0) ** - MAPPING2.MAP, 60 bytes, 5/31/2010 2:06:54 PM

.1714 14:31:40 (0) ** - OBJECTS.DATA, 8192 bytes, 5/31/2010 2:06:54 PM

.1715 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1716 14:31:40 (2) !! WARNING: Windows Firewall Service: .................................................................................. STOPPED.

.1717 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1718 14:31:40 (0) ** DCOM Status: ........................................................................................................ OK.

.1719 14:31:40 (0) ** WMI registry setup: ................................................................................................. OK.

.1720 14:31:40 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!

.1721 14:31:40 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Automatic')

.1722 14:31:40 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.

.1723 14:31:40 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but

.1724 14:31:40 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,

.1725 14:31:40 (0) ** this can prevent the service/application to work as expected.

.1726 14:31:40 (0) **

.1727 14:31:40 (0) ** RPCSS service: ...................................................................................................... OK (Already started).

.1728 14:31:40 (0) ** WINMGMT service: .................................................................................................... OK (Already started).

.1729 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1730 14:31:40 (0) ** WMI service DCOM setup: ............................................................................................. OK.

.1731 14:31:40 (0) ** WMI components DCOM registrations: .................................................................................. OK.

.1732 14:31:40 (0) ** WMI ProgID registrations: ........................................................................................... OK.

.1733 14:31:40 (0) ** WMI provider DCOM registrations: .................................................................................... OK.

.1734 14:31:40 (0) ** WMI provider CIM registrations: ..................................................................................... OK.

.1735 14:31:40 (0) ** WMI provider CLSIDs: ................................................................................................ OK.

.1736 14:31:40 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.

.1737 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1738 14:31:40 (0) ** Overall DCOM security status: ....................................................................................... OK.

.1739 14:31:40 (0) ** Overall WMI security status: ........................................................................................ OK.

.1740 14:31:40 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------

.1741 14:31:40 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.

.1742 14:31:40 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.

.1743 14:31:40 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.

.1744 14:31:40 (0) ** You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize

.1745 14:31:40 (0) ** the performance counters with the WMI performance classes with the following commands:

.1746 14:31:40 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'

.1747 14:31:40 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF'

.1748 14:31:40 (0) ** The ADAP process logs informative events in the Windows NT event log.

.1749 14:31:40 (0) ** More information can be found on MSDN at:

.1750 14:31:40 (0) ** http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp

.1751 14:31:40 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!

.1752 14:31:40 (0) ** - Root, 0x80041006 - (WBEM_E_OUT_OF_MEMORY) Not enough memory for the operation.

.1753 14:31:40 (0) **

.1754 14:31:40 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!

.1755 14:31:40 (0) ** - Root, 0x80041006 - (WBEM_E_OUT_OF_MEMORY) Not enough memory for the operation.

.1756 14:31:40 (0) ** - Root, 0x80041006 - (WBEM_E_OUT_OF_MEMORY) Not enough memory for the operation.

.1757 14:31:40 (0) ** - Root/Default, 0x80041006 - (WBEM_E_OUT_OF_MEMORY) Not enough memory for the operation.

.1758 14:31:40 (0) ** - Root/CIMv2, 0x80041006 - (WBEM_E_OUT_OF_MEMORY) Not enough memory for the operation.

.1759 14:31:40 (0) ** - Root/WMI, 0x80041006 - (WBEM_E_OUT_OF_MEMORY) Not enough memory for the operation.

.1760 14:31:40 (0) **

.1761 14:31:40 (0) ** WMI GET operations: ................................................................................................. OK.

.1762 14:31:40 (0) ** WMI MOF representations: ............................................................................................ OK.

.1763 14:31:40 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.

.1764 14:31:40 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.

.1765 14:31:40 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.

.1766 14:31:40 (0) ** WMI GET VALUE operations: ........................................................................................... OK.

.1767 14:31:40 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.

.1768 14:31:40 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.

.1769 14:31:40 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.

.1770 14:31:40 (0) ** WMI static instances retrieved: ..................................................................................... 0.

.1771 14:31:40 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.

.1772 14:31:40 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.

.1773 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1774 14:31:40 (0) **

.1775 14:31:40 (0) ** 6 error(s) 0x80041006 - (WBEM_E_OUT_OF_MEMORY) Not enough memory for the operation

.1776 14:31:40 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:

.1777 14:31:40 (0) ** - Failing WMI system components (see any missing WMI system files or DCOM registration

.1778 14:31:40 (0) ** issues previously mentioned).

.1779 14:31:40 (0) ** - Failing WMI providers (see any DCOM registration issues previously mentioned).

.1780 14:31:40 (0) ** - a WMI repository corruption.

.1781 14:31:40 (0) ** Under Windows XP 64-bit SP1, Windows 2003 SP1 and Windows Vista, the

.1782 14:31:40 (0) ** repository consistency is ALWAYS verified.

.1783 14:31:40 (0) ** Under Windows XP SP2, the repository consistency must be explicitly requested:

.1784 14:31:40 (0) ** i.e. 'WMIDiag CheckConsistency''

.1785 14:31:40 (0) ** Check the state of the repository above in the WMIDiag report.

.1786 14:31:40 (0) ** If the repository is inconsistent, it must be reconstructed.

.1787 14:31:40 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,

.1788 14:31:40 (0) ** otherwise some applications may fail after the reconstruction.

.1789 14:31:40 (0) ** This can be achieved with the following command:

.1790 14:31:40 (0) ** i.e. 'WMIDiag ShowMOFErrors'

.1791 14:31:40 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing

.1792 14:31:40 (0) ** ALL fixes previously mentioned.

.1793 14:31:40 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)

.1794 14:31:40 (0) **

.1795 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1796 14:31:40 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!

.1797 14:31:40 (0) ** INFO: Unexpected registry key value:

.1798 14:31:40 (0) ** - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 2

.1799 14:31:40 (0) ** - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1

.1800 14:31:40 (0) ** From the command line, the registry configuration can be corrected with the following command:

.1801 14:31:40 (0) ** i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'

.1802 14:31:40 (0) **

.1803 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1804 14:31:40 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 70 ERROR(S)!

.1805 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MFL

.1806 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF

.1807 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLI.MOF

.1808 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MFL (*)

.1809 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLIEGALIASES.MOF (*)

.1810 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLUSWMI.MOF

.1811 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CMDEVTGPROV.MOF

.1812 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF

.1813 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSPROV.MOF

.1814 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DSPROV.MFL

.1815 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DSPROV.MOF

.1816 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\EVNTRPRV.MOF

.1817 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\HNETCFG.MOF

.1818 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\IEINFO5.MOF

.1819 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\KRNLPROV.MFL

.1820 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\KRNLPROV.MOF

.1821 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\LICWMI.MFL

.1822 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\LICWMI.MOF

.1823 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\LNWMSEVENTS.MOF

.1824 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\LSWMSEVENTS.MFL

.1825 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (*)

.1826 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (*)

.1827 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NLBMPROV.MOF

.1828 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NTEVT.MFL

.1829 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NTEVT.MOF

.1830 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.MFL

.1831 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.MOF

.1832 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\REGEVENT.MFL

.1833 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\REGEVENT.MOF

.1834 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\RSOP.MFL

.1835 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\RSOP.MOF

.1836 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCERSOP.MOF

.1837 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCM.MOF

.1838 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL (*)

.1839 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF (*)

.1840 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MFL

.1841 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF

.1842 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL (*)

.1843 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF (*)

.1844 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SUBSCRPT.MOF

.1845 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SYSTEM.MOF

.1846 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TSCFGWMI.MFL

.1847 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\TSCFGWMI.MOF

.1848 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDS.MFL

.1849 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VDS.MOF

.1850 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VSS.MFL

.1851 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\VSS.MOF

.1852 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL (*)

.1853 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF (*)

.1854 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WHQLPROV.MOF

.1855 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WLBSPROV.MFL

.1856 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WLBSPROV.MOF

.1857 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMI.MFL

.1858 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMI.MOF

.1859 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPCIMA.MFL

.1860 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPCIMA.MOF

.1861 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPDFS.MFL

.1862 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPDFS.MOF

.1863 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPDSKQ.MFL

.1864 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPDSKQ.MOF

.1865 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPICMP.MFL

.1866 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPICMP.MOF

.1867 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPIPRT.MFL

.1868 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPIPRT.MOF

.1869 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPJOBJ.MFL

.1870 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPJOBJ.MOF

.1871 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPSESS.MFL

.1872 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMIPSESS.MOF

.1873 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MFL

.1874 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MOF

.1875 14:31:40 (0) ** => After fixing all other issues previously mentioned, if the WMI repository is rebuilt,

.1876 14:31:40 (0) ** the listed MOF file(s) will not be recompiled, and therefore the definition they contain

.1877 14:31:40 (0) ** will not be available in the WMI repository.

.1878 14:31:40 (0) ** => You must manually recompile the MOF file(s) with the 'MOFCOMP.EXE <FileName.MOF>' command.

.1879 14:31:40 (0) ** => If you want the MOF file(s) to be part of the Auto-Recovery list, make sure the

.1880 14:31:40 (0) ** statement '#PRAGMA AUTORECOVER' is included.

.1881 14:31:40 (0) ** Note: MOF file(s) marked with (*) are NEVER included AT SETUP in the auto-recovery process.

.1882 14:31:40 (0) ** MOF file(s) containing UNINSTALL statements (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery process.

.1883 14:31:40 (0) ** Refer to the list of MOF files below NOT containing the '#PRAGMA AUTORECOVER' statement' for more information.

.1884 14:31:40 (0) **

.1885 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1886 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1887 14:31:40 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 17 FILE(S)!

.1888 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CLUSWMI.MOF

.1889 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\CMDEVTGPROV.MOF

.1890 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSETW.MOF

.1891 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\DNSPROV.MOF

.1892 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MFL (DELETE)

.1893 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NCPROV.MOF (DELETE)

.1894 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NLBMPROV.MOF

.1895 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCM.MOF (DELETE)

.1896 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MFL

.1897 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SCRCONS.MOF

.1898 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MFL

.1899 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\SMTPCONS.MOF

.1900 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MFL

.1901 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMCONS.MOF

.1902 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WHQLPROV.MOF

.1903 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MFL

.1904 14:31:40 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WMITIMEP.MOF

.1905 14:31:40 (0) ** => MOF file(s) marked with (*) are INCLUDED in the AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER' statement.

.1906 14:31:40 (0) ** If the WMI repository is rebuilt, the listed MOF files not included in the AUTO-RECOVERY LIST and

.1907 14:31:40 (0) ** missing the '#PRAGMA AUTORECOVERY' statement when they are compiled the first time will NOT

.1908 14:31:40 (0) ** be recompiled during the repository reconstruction.

.1909 14:31:40 (0) ** Note: If you want the MOF file to be part of the AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'

.1910 14:31:40 (0) ** is included and recompile the MOF/MFL with the following command:

.1911 14:31:40 (0) ** i.e. 'MOFCOMP.EXE <FileName.MOF>'

.1912 14:31:40 (0) **

.1913 14:31:40 (0) ** => MOF file(s) marked with (DELETE) contains class and instance DELETE statements.

.1914 14:31:40 (0) ** Usually, MOF with DELETE statements are used to UNinstall components and they should NOT be listed in the AUTORECOVERY LIST

.1915 14:31:40 (0) ** and therefore they should NOT specify the '#PRAGMA AUTORECOVER' statement.

.1916 14:31:40 (0) ** Note: It happens that some MOF files do contain DELETE statements for installation purposes to delete

.1917 14:31:40 (0) ** existing information before it is recreated.

.1918 14:31:40 (0) **

.1919 14:31:40 (0) ** Note: It is also possible that the application implemented its own recovery mechanism.

.1920 14:31:40 (0) ** In that case, no action is required. You must verify with the application vendor

.1921 14:31:40 (0) ** if the application has this capability (i.e. Microsoft SMS)

.1922 14:31:40 (0) **

.1923 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1924 14:31:40 (0) **

.1925 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1926 14:31:40 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------

.1927 14:31:40 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

.1928 14:31:40 (0) **

.1929 14:31:40 (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.SP1.32_DELLSRV_2010.05.31_14.31.23.LOG' for details.

.1930 14:31:40 (0) **

.1931 14:31:40 (0) ** WMIDiag v2.0 ended on Monday, May 31, 2010 at 14:31 (W:91 E:17 S:1).

Link to comment
Share on other sites

Start > Run > rundll32 wbemupgd, RepairWMISetup

I appreciate your replies - I had done that and it still is not right - i fix one thing and then five other things change - i love how it says 70 files are missing in the wbem folder are missing and yet i can go there and see them...

your thoughts are always valued...

Link to comment
Share on other sites

- i love how it says 70 files are missing in the wbem folder are missing and yet i can go there and see them...

I'm not a WMI expert, but my reading of the posted log files doesn't say that at all.

What it says is that all the files are present in C:\WINDOWS\system32\wbem but they are missing from the Registry:

.1804 14:31:40 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 70 ERROR(S)!
The log file then lists 70 files (probably the entire folder contents of .MOF and .MFL files). On a healthy system, about 50 of those should be listed in the Registry, along with a pile of others. In the procedure given by cluberti the "Autorecover MOFs" registry entry is zapped, ready for a rebuild. If that registry key is still empty, it looks to me as if the rebuild (step 5) failed, presumably because the MOFComp command failed:
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
(NB: %s at the command prompt but %%s in a batch file) What do you have in the "Autorecover MOFs" value, which may be found at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM

?? There should be somewhere between 50 and 85 files listed. It's a REG_MULTI_SZ value, so a bit difficult for humans to read it accurately!

Also, since we are dealing with a server, did you log-in locally or remotely?

I seem to recall that remote login to Server 2003 has a problem with having to be in "install" mode.

.

Link to comment
Share on other sites

  • 3 months later...

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...