Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

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
20:45, 22 Jun 2017