January 14, 2013 at 12:05 pm
I am running SSMS on my local machine (win7). I am trying to use acivity monitor on a server on our domain. I can veiw all other tabs, but not the Overview. I get the following error below:
I don't know if it is related or a seperate issue, but I also don't get the green arrow icon on the sql server in object explorer. The Stop, Start, Restart, etc is all grayed out.
Both of these issues happen on this server only.
sql server 2008 R2 10.50.400 Standard
windows server 2008 sp 2
I have tried serveral things:
If i use ssms on the local server, with my same domain account, i have no issues
My user is a member of local admin group
My user has SysAdmin permissions
It is very similar to this issue:
I can remotely connect to the Services and WMI control console
I have tried with SSMS 2012 and SSMS 2008 R2
I have also tried this with DCOM
Error:
The Activity Monitor is unable to execute queries against server <Servername>.
Activity Monitor for this instance will be placed into a paused state.
Use the context menu in the overview pane to resume the Activity Monitor.
===================================
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) (mscorlib)
------------------------------
Program Location:
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at Microsoft.SqlServer.Management.ResourceMonitoring.SqlPerfmonProcessReader.get_LogicalCpuCount()
at Microsoft.SqlServer.Management.ResourceMonitoring.SqlPerfmonProcessReader.GetSqlProcessCpuUtilization()
at Microsoft.SqlServer.Management.ResourceMonitoring.BackgroundSqlCpuTask.Execute()
at Microsoft.SqlServer.Management.ResourceMonitoring.BackgroundWorkRequest.Execute()
at Microsoft.SqlServer.Management.ResourceMonitoring.BackgroundWorkRequestQueue.BackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
January 14, 2013 at 1:19 pm
We found the issue. It was a firewall issue. We needed to enable WMI traffic for remote Windows Management Instrumentation.
November 4, 2016 at 2:42 am
i am facing the same issue, tried all DCOM permissions.no luck.
Do we have any specific port for WMI traffic.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply