![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| Premium32 Ultimate32 Pro | WMI Errors WMI Errors Are these 2 errors below plus 3 missing dll file errors from the "C:\Windows\System32\Wbem" folder a Vista bug? (framedyn.dll, provthrd.dll, wbemcomn.dll) I have the same 5 errors in Premium & Ultimate. When Googling I saw one post suggesting it was a Vista bug. Would others consider running the WMI diagnostic tool to check their results? Download, unpacks 3 files to temp- no install necessary Script runs in background After 1 minute I had to allow through firewall Runs about 10 - 15 min and then opens a report window in note pad http://www.microsoft.com/technet/scr...p/wmidiag.mspx Download details: The WMI Diagnosis Utility 28917 07:56:54 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 2 ERROR(S)! 28918 07:56:54 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found. 28919 07:56:54 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)' 28920 07:56:54 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found. 28921 07:56:54 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)' 28922 07:56:54 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to 28923 07:56:54 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters. 28924 07:56:54 (0) ** You can refresh the WMI class provider buffer with the following command: 28925 07:56:54 (0) ** 28926 07:56:54 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF' 28950 07:56:54 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found 28951 07:56:54 (0) ** => This error is typically a WMI error. This WMI error is due to: 28952 07:56:54 (0) ** - a missing WMI class definition or object. 28953 07:56:54 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures). 28954 07:56:54 (0) ** You can correct the missing class definitions by: 28955 07:56:54 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command. 28956 07:56:54 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag. 28957 07:56:54 (0) ** (This list can be built on a similar and working WMI Windows installation) 28958 07:56:54 (0) ** The following command line must be used: 28959 07:56:54 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider' 28960 07:56:54 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters 28961 07:56:54 (0) ** with WMI by starting the ADAP process. 28962 07:56:54 (0) ** - a WMI repository corruption. 28963 07:56:54 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter 28964 07:56:54 (0) ** to validate the WMI repository operations. 28965 07:56:54 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before 28966 07:56:54 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use: 28967 07:56:54 (0) ** i.e. 'WMIDiag WriteInRepository=Root' 28968 07:56:54 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces 28969 07:56:54 (0) ** the WMI repository must be reconstructed. 28970 07:56:54 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository, 28971 07:56:54 (0) ** otherwise some applications may fail after the reconstruction. 28972 07:56:54 (0) ** This can be achieved with the following command: 28973 07:56:54 (0) ** i.e. 'WMIDiag ShowMOFErrors' 28974 07:56:54 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing 28975 07:56:54 (0) ** ALL fixes previously mentioned. 28976 07:56:54 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory) |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Stop Errors - Troubleshooting Specific Stop Errors | Tutorials | |||
| Errors | Vista performance & maintenance | |||
| Errors, errors and more errors - I have Issues! | Vista performance & maintenance | |||
| SP1 - new errors? | Vista General | |||
| explorer errors, program errors, no task manager | Vista performance & maintenance | |||