Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > WARNING: Config change detected, aborting

WARNING: Config change detected, aborting

Table of contents
Created by Bill Corgey, last modified by Rodim Suarez_ret on Jun 29, 2016

Views: 1,149 Votes: 0 Revisions: 5



The emails for Real Time Change Detection shows the following message as part of the configuration:

WARNING: Config change detected, aborting

This may be a rare case scenario.


  • NCM 7.5


This anomaly is due to a runaway RTN event generally caused by a loop where the trigger action spawns a config download of the config, and the the command to download a config, spawns a Real Time Change detection and thus creating a loop and eventually the Cache is overwhelmed.

The message being displayed in the config is not in any NCM coding and could not come from the NCM application.

It is assumed that the message is being sent from the device, but no confirmation has been established on that side.

As for now, you need to make sure that the Real Time Change Detection trigger is based on the Syslog message: *end configuration: OK*

This message is only sent upon one exiting config mode.



Last modified