Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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

ServiceNow incident reopens after being closed or resolved

Updated June 23, 2017

Overview

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

Environment

All Orion Platform versions with ServiceNow integration

Cause

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.

Resolution

  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

Tags

Classifications

Public