The following suggestions were made by
Microsoft to resolve the issue.
Ensure that
the WMI Repository is consistent on this computer
Ensure that
the Windows Management Instrumentation (WMI) service is running on this
computer.
Ensure that
the Remote Procedure Call (RPC) service is running on this computer.
•
|
Open a Command Prompt
|
•
|
Run the following command: “winmgmt /verifyrepository”
|
•
|
If the repository is not consistent, then run the command
“winmgmt /salvagerepository”
|
Ensure that
DCOM is enabled
•
|
Run Dcomcnfg.exe
|
|
•
|
Click the Component Services node under Console Root
|
|
•
|
Open the Computers folder
|
|
•
|
For the local computer, right-click My Computer, and then
click Properties
|
|
•
|
For a remote computer, right-click the Computers folder,
point to New and then click Computer
|
|
•
|
•
|
Type the computer name
|
•
|
Right-click the computer name, and then click Properties
|
|
•
|
Click the Default Properties tab
|
|
•
|
Click to select (or click to clear) the “Enable
Distributed COM on this Computer” check box
|
|
•
|
Set Default Authentication Level to Connect
|
|
•
|
Set Default Impersonation Level to Identify
|
If none of
these steps resolve the issue, you can download the WMI Diagnosis Utility at http://go.microsoft.com/fwlink/?LinkId=158226.The
WMI Diagnosis Utility is a VBScript script designed to help you troubleshoot
the current state of the WMI service on a computer.
No comments:
Post a Comment