Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 423
  • Last Modified:

WMI issues on a Windows 7 64 bit workstation

I am having a WMI problem that was discovered while trying to configure Spice-works on this Win 7 Machine. We are on an SBS2011 server configured with a domain. I have run WMIDiag 2.1 and am not sure if there is a better way to describe it than just Attaching the log from the utility. I am thinking coruption but have not tried anything yet
WMIDIAG-V2.1-VISTA.CLI.SP1.64-WK.TXT
0
akersrus101
Asked:
akersrus101
1 Solution
 
mlongohCommented:
Well I would try what the log suggests, run WINMGMT.EXE /SYNCPERF

I'd also look at this:
29526 11:12:12 (0) ** => This error is typically a WMI error. This WMI error is due to:
29527 11:12:12 (0) **    - a missing WMI class definition or object.
29528 11:12:12 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
29529 11:12:12 (0) **      You can correct the missing class definitions by:
29530 11:12:12 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
29531 11:12:12 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
29532 11:12:12 (0) **            (This list can be built on a similar and working WMI Windows installation)
29533 11:12:12 (0) **            The following command line must be used:
29534 11:12:12 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
29535 11:12:12 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
29536 11:12:12 (0) **            with WMI by starting the ADAP process.
29537 11:12:12 (0) **    - a WMI repository corruption.
29538 11:12:12 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
29539 11:12:12 (0) **      to validate the WMI repository operations.
29540 11:12:12 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
29541 11:12:12 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
29542 11:12:12 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
29543 11:12:12 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
29544 11:12:12 (0) **      the WMI repository must be reconstructed.
29545 11:12:12 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
29546 11:12:12 (0) **          otherwise some applications may fail after the reconstruction.
29547 11:12:12 (0) **          This can be achieved with the following command:
29548 11:12:12 (0) **          i.e. 'WMIDiag ShowMOFErrors'
29549 11:12:12 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
29550 11:12:12 (0) **          ALL fixes previously mentioned.
0
 
akersrus101Author Commented:
Could someone please point out the file name in this line from the WMIdiag log?

MOF Registration: ''
29355 11:12:12 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now