| Sage System Verifier fails on System Disk, Network Adapters, Computer Processors, and System Enclosures |
Cause | WMI is corrupted. How to verify: - Open Computer Management.
- Right mouse-click on WMI Control, in Services and Applications and select Properties.
Note: If you receive an access denied error, you do not have the correct permissions to access the WMI console. Either log into the machine as an Administrator or contact your System Administrator to reset your permissions. - Verify text in the box on the General tab:
- This is an example of a good result:
- This is an example of a corrupted WMI:
Note: The text may contain different variations of errors. If you see text containing Failed to connect to local computer because Interface: class not registered, Could not be found..., Failed to initialize..., or Is corrupt... then continue with the steps below. |
Resolution | [BCB:3:Network warning:ECB]
[BCB:5:Third-party support:ECB]
- Open services by pressing the Windows key + R then typing services.msc.
- Locate the Windows Management Instrumentation service.
- Right click the service and select Properties.
- Change startup type to Disabled then stop the service.
- Minimize the Services window.
- Open Windows Explorer, paste: %SystemRoot%\System32\WBEM\Repository in the address bar and press enter.
- Delete the files in that folder.
- Go back to services and open the properties of the Windows Management Instrumentation service again.
- Change the startup type back to Automatic and start the service.
- Press the Windows key + R to open the Run dialog box.
- In the Open field, type wmimgmt.msc and click OK, or hit Enter.
- Select Action, Properties.
- The message in the WMI Control box should start with Successfully connected to : local computer...
- Relaunch the Sage System Verifier and it should no longer fail on the those components.
|
|