Comments
4 comments
-
Hi, sorry to hear you're running into an issue!
This problem may be due to a corrupted performance counter or wmi repository.
Can you please first try the following on the problem server:
1. From an elevated command prompt - runwinmgmt /verifyrepository
. Then stop the WMI service by runningnet stop winmgmt /y
. Once you receive confirmation that the service has stopped, runwinmgmt /resetrepository
and then try adding the server again.
2. Should that not help, please try rebuilding your WMI perf counters:
Open a command line with Elevated rights and then run the following commands:c:
Stop and restart the Performance Logs and Alerts service.
cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R
WINMGMT.EXE /RESYNCPERF
Stop and restart the Windows Management Instrumentation service.
Then try adding the server once more.
I hope that helps but please let me know if not.
Many Thanks
Eddie -
Hello,
Thanks for coming back to me. We find out that we need to give user Admin access to the server and to performance monitor. That has fixed the issue. -
Was this ever resolved? I am having the same issue on Windows Server 2016 Standard.
-
I elevated the user to have Admin access to Server Machine and SQL Servers Admin in the cluster and this has sorted the issue on that particular cluster.
Add comment
Please sign in to leave a comment.
I am trying to put SQL Monitor to localhost of a machine but I am getting this error message. Do you know the reason ?