SQL Server database can’t be taken offline when monitored via ApexSQL Monitor

Applies to
ApexSQL Monitor

Symptoms

A SQL Server instance can’t be put offline using the SSMS Take Offline command when the hosting SQL Server is monitored by ApexSQL Monitor

Affected versions:

ApexSQL Monitor 2014 R3 and earlier

Workaround

For users that run into this issue, the problem can be solved by temporarily by stopping the ApexSQL Monitor service. To do that:

  1. Run Services from the Control Panel->All Control Panel Items->Administrative Tools

  2. Locate and select the ApexSQLMonitor service

  3. Press the Stop the service on the left side and wait for the ApexSQLMonitor service to stop

  4. Once the ApexSQLMonitor service is stopped, the database will be taken offline successfully

  5. Press Start the service to start the ApexSQLMonitor service again

ApexSQL plans to fix this issue in the next immediate release and we apologize for the inconvenience

Related posts:

  1. The “Files are in use” error occurs when upgrading ApexSQL Monitor
  2. I cannot activate ApexSQL Monitor, the ‘Hardware ID’ field is empty
  3. The “Service is not located. Please try different machine name or port, or verify that the service is running” error
  4. The “The server <server_name> doesn’t exist in the database” error is encountered when disabling the monitored SQL Server
  5. The ApexSQL Monitor repository database transaction log file continues to grow even after data was deleted using the Purge data option