Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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

WARNING: Config change detected, aborting

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

Views: 67 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
18:57, 28 Jun 2016