The "Full Access" monitoring mode in SQL Sentry is the mode that allows SQL Sentry to monitor not just metrics from your SQL Server instance, but also from the underlying Windows operating system. Metrics such as CPU utilization, network utilization, memory usage, disk activity, and more.
Sometimes there could be various issues that prevent SQL Sentry from successfully activating the "Full Access" monitoring mode. That would cause SQL Sentry to work in the "Limited Access" mode, where only the right-hand side is visible in the performance analysis dashboard.
This article describes a methodology for how to resolve such issues.
In this page:
We can use the tools below before we even begin working with SQL Sentry, in order to verify the minimum requirements needed for the Full Access monitoring mode.
Once you perform the tests successfully using all 3 tools, then SQL Sentry should also be able to work in Full Access monitoring mode.
Note that tests performed using these tools must be done from within the monitoring service machine, while logged on as the monitoring service account:
Click Start > Run > wbemtest
Click on "Connect..."
In the "Namespace" field, add \\yourTargetName\ at the start of the namespace address, replacing "yourTargetName" with the relevant SQL Server target hostname. The final value should look like this: \\yourTargetName\root\cimv2
Click on "Connect".
If this works, it means you have WMI connectivity.
Click Start > Run > perfmon
Click on Action > Connect to another computer...
Select "Remote computer" and enter the relevant SQL Server target hostname in the text box.
Click on OK.
If this works, it means you have RPC connectivity and access to Performance Counters.
Click Start > Run > regedit
Click on File > Connect Network Registry...
Enter the relevant SQL Server target hostname in the text box.
Click on "Check Names" to make sure that the computer is found in the directory.
Click on OK.
If this works, it means you have WMI connectivity and access to the Windows Registry.
Whenever you perform a test using either of the tools above, and you encounter an error, you should google for the name of the tool + the error that you received, in order to find details online about how to resolve the issue.
For example: "wbemtest access is denied"
There are many possible issues and problems that could prevent any of these tests to work... From missing permissions on different components, to Windows Firewall rules, to missing Windows Services, and even missing Windows updates.
Furthermore, new issues are potentially added with every new Windows version and patch.
Therefore, it's impractical to maintain a single troubleshooting guide for all possible issues that could happen.
However, using the simple methodology described above, you should be able to find a solution fairly easily, simply using information that's available online.
The main reason for this methodology is that it's by far easier to find solutions online for a "Windows-related" issue, rather than a "SQL Sentry-related" issue... And if you're able to narrow down the issue to a specific Windows tool and error message, then that makes it even easier.
With that being said, below is a list of resources published by SQL Sentry, which address several common issues with Full Access monitoring.
This is by no means an exhaustive list. It does not cover all possible issues. But it should cover the most common ones: