Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Network Performance Monitor (NPM) > ServiceNow incident reopens after being closed or resolved

ServiceNow incident reopens after being closed or resolved

Updated June 23, 2017


This article addresses the issue where ServiceNow incidents reopen after being closed or resolved.


All Orion Platform versions with ServiceNow integration


This issue occurs because of the following:

  • The ServiceNow incident cannot be resolved.
  • The alert that created the incident is not active.
  • A node has been removed.


  1. Establish a remote connection to the main Orion server.
  2. Open Database Manager.
  3. Locate the "SNI_AlertIncidents" table.
  4. Run the following query:
    delete from  [dbo].[SNI_AlertIncidents] where IncidentNumber =  'servicenow incident number'
    Note: The string is the full incident number in ServiceNow and must be in quotes.
  5. Resolve or close the issue in ServiceNow.




Last modified