SSMS activity monitor paused – How we tackle it

The ‘SSMS activity monitor paused’ error message occurs when we try to open Activity Monitor in SQL Server Management Studio.

The SSMS activity monitor paused message appears when SQL Server Management Studio cannot load live performance data in Activity Monitor. This makes it difficult to monitor active sessions, resource usage, and server performance.

Although this issue often results from missing permissions, it can also occur because of remote access settings, WMI configuration, or an outdated SQL Server Management Studio version. In this article, we look at the common causes and the fixes that help restore Activity Monitor.

Why Does SSMS Activity Monitor Show Paused?

Activity Monitor displays information about what is going on with SQL Server at any given point in time, and such activity needs “high-level insight” into the Operating System and SQL Server. Such “high-level” permissions are not enabled by default for user accounts.

When SSMS activity monitor keeps pausing, SQL Server Management Studio cannot refresh this information. As a result, administrators cannot view the latest server activity until the underlying issue is resolved.

For instance, the error appears as follows.

Common Causes and Fixes for SSMS Activity Monitor Paused

Now, let’s take a look at the different causes and fixes of this error message.

1. The high-level permissions are not enabled while connecting remotely.

Solution:

Here are the steps to enable elevated permissions when logged in remotely. Thus, we need to enable Remote Launch & Remote Activation permissions on the remote Operating System.

1. First, connect to the remote machine using a Remote Desktop.

2. Then open the Component Services (DCOMCNFG) from the Start menu

3. Now, in the left-hand tree, under Console Root, expand Component Services, expand Computers, right-click on My Computer and go to Properties

4. Under the Properties window, go to the COM Security tab.

5. Then, in the Launch and Activation Permissions section, click on the Edit Limits button.

• Under the Security Limits tab, see if your user/group name exists. If it doesn’t exist, then add it to the list by clicking on the Add button.
• After you add the user, highlight the user, and make sure it has both Remote Launch & Remote Activation permissions checked.

6. Click on the Edit Limits button in the Access Permissions section.

• Under the Security Limits tab, see if your user/group name exists. In case it doesn’t exist, then add to the list by clicking on the Add button.
• After you add the user, highlight the user, and make sure it has Remote Access permissions checked.

7. Hit Okay to save changes.

8. Now expand the My Computer in the left-hand tree and go to DCOM Config.

• Here, find the Windows Management and Instrumentation and click on Properties.
• Click on the Security tab and under the Launch and Activation Permissions section, click on the Edit button
• Under the Security tab, see if your user/group name exists. In case it doesn’t exist, then add to the list by clicking on the Add button.
• After you add the user, highlight the user, and make sure it has both Remote Launch & Remote Activation permissions checked.

9. Finally, save all the changes and then re-open Activity Monitor

2. You are using an outdated version of SSMS

Solution:

Older versions of SQL Server Management Studio may experience Activity Monitor issues. Update to the latest supported version of SSMS, reconnect to the server, and check whether the problem is resolved.

3. In WMI, the Remote Enable is not activated

Solution:

• First, run the wmimgmt.msc on the DB-server
• Then open the properties of WMI-Control (RM-click)
• Now open the Security tab.
• Under the Security tab, select CIMv2 and click the Security button below
• Now, add or locate the account or group
• Finally, in the permissions list, check Remote enable.

4. By default, the permissions are not enabled for user accounts.

Solution:

To solve this, grant the user the “View server state” permission. Here are the steps to do the same:

• First, open the Security and Login folders for the relevant server instance.
• Now, right-click a login and choose properties.
• Then choose Securables, and you should see all Permissions listed in the bottom pane.
• Finally, put a tick in the grant column next to the View server state.

5. Windows performance counters are unavailable

Solution:

Activity Monitor also relies on Windows performance counters. If the counters are unavailable or corrupted, the monitoring panels may not refresh correctly. Verify the performance counters and rebuild them if necessary before reopening Activity Monitor.

[Need any assistance in fixing SQL errors? – We’ll help you]

Conclusion

The SSMS activity monitor paused error usually occurs because of permission, configuration, or monitoring issues. Checking SQL Server permissions, DCOM settings, WMI configuration, your SSMS version, and Windows performance counters resolves the issue in most environments.