Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article. The WMI Service is repaired. The folder "Repository" was recreated automatically. It is not necessary to reboot the server. Note: If you are not able to rename the folder "Repository", change the start-type of the service "Windows Management Instrumentation" to "manual" and perform steps 2.
Change the starttype back to automatic afterwards. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 Application Compatibility.
Sign in to vote. When I try to start it manually, an error message displays: "Windows could not start the windows management instrumentation service on local computer. Output of WMIdiag script is below : Tuesday, April 21, AM. Hi Domushnik, When did the issue start to occur? Have you tried to update all the machines? This setting is usually all that needs to be changed to get WMI working. Steps 2 and 3 are typically not needed, but they might be in some circumstances.
At this point go back and see if this fixes the problem. It might take a couple of minutes for the reports to re-generate. For reading WMI data on a remote server, a connection needs to be made from your management computer where our monitoring software is installed to the server that you're monitoring the target server. This can only be done at the command prompt. Run the following on the target computer if it is running a Windows firewall:.
If the account you are using to monitor the target server is NOT an administrator on the target server, you need to enable the non-administrator to interact with DCOM by following the simple steps listed here.
0コメント