Database Management

System Status stuck in SQL Sentry

After patching Windows in a SolarWinds SQL Sentry environment, multiple monitored targets came online in an inconsistent state. This resulted in widespread “Instance Offline” / unknown system status entries in the System Status tab.

First published date

1/27/2026 8:38 PM

Last published date

1/27/2026 8:38 PM

Overview

The status of the target is unknown, the Last Result in the System Status is Errors: Instance Offline, and the Last Success Time is a day or hours ago. 

Status Stuck

Product section

SQL Sentry (SQLS)

Cause

The issue can be driven by two overlapping factors:

  1. Monitoring Services are in an inconsistent state after Windows patching.
    1. If the Monitoring Services' startup type is not using Automatic (Delayed Start), the service may not be in a true running state.
  2. Stale work items in the Monitoring Services' queue (ManagementEngineWorker table).

Resolution

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

Important: This procedure modifies an internal table in the SQL Sentry repository database. It should be performed by a qualified DBA or system owner in accordance with your organization’s change‑control policies.

Reset the Monitoring Service worker queue and update the Startup Type.

  1. Stop all SQL Sentry Monitoring Services.
    1. Use the EPI command or the Services window for the Unified version to stop all Monitoring Services.
  2. Truncate the ManagementEngineWorker table in the SQL Sentry database. (This table will autofill after restarting the Monitoring Services.)
  3. On each Windows server hosting a SQL Sentry Monitoring Service, open Services. (This process helps ensure the Monitoring Services start reliably after Windows patching and related system boot delays.)
    1. Locate the SentryOne Monitoring Service.
    2. Set the Startup Type to Automatic (Delayed Start).
  4. Start all the Monitoring Services.
    1. Use the EPI command or the Services window for the Unified version to start all Monitoring Services.
  5. Ensure the ManagementEngineWorker table is repopulated, data is populated on the dashboard, the System Status of the target is current, and the "Instance Offline" messages are gone.