Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM configuration backups fail intermittently

NCM configuration backups fail intermittently

Updated Aug 31, 2018 

Created by Milton Harris, last modified by Melanie Boyd on Oct 12, 2018

Views: 452 Votes: 1 Revisions: 6


In this document you will learn:


  • Which logs to examine for  NCM configuration backups fail intermittently
  • Which services are involved 
  • [Which support troubleshooting tools with they need to use, and why?]
  • What steps to take to resolve NCM configuration backup jobs failing intermittently



One of the more common SolarWinds customer support calls involve NCM configuration backups failing intermittentlyThere are many factors that come into play so it is important that you understand how to address this issue in a logical manner. 


Customers might not always provide a lot of details but it will almost certainly be described as:

  • NCM configuration backups fail intermittently
  • Nightly Config Backup Jobs fail intermittently



 Scoping the Issue 

What to Ask


Here are a few questions to ask before jumping into the problem. You don't have to stop at these questions. Different scenarios might need you to probe differently, but this is a good starting point.


  • When was this issue first observed?
    • Try to establish what happened before the onset of the problem
    • Were there any changes made before the problem started?


  • Reproduce the issue
    • If you can't reproduce the issue, you can't confirm whether it's been fixed
    • If its a once-off occurrence, the most you can do is check the log files, and try to determine what occurred at that time.
    • Can it be easily reproduced or is it intermittent? Is there any pattern?
    • What are the expected results?


  • Narrow the focus
    • How Many Nodes are in your Nightly Config Backup Jobs?
    • Do you have session Tracing turned on?
    • Which Logs do you have turned on? 


  • Other Tips
    • If you have Session Tracing turned on it will try to download configs AND on top of that it will be forced to try and write a session trace for every node in which you're Downloading Configs here to this path: The session trace files can be found here: "%ALLUSERSPROFILE%\Application Data\SolarWinds\Logs\Orion\NCM\Session-Trace"
    • If you have Scheduled Jobs Logging turned on it will try to download Configs AND on top of that it will try and write Job Logs for every node in the job for which you're downloading. The log files can be found here: "${ALLUSERSPROFILE}\Application Data\SolarWinds\Logs\Orion\NCM\Logging"Configs  Data\SolarWinds\Logs\Orion\NCM\Session-Trace"
    • If you have Session Tracing and Scheduled Job logging, Inventory Monitor logging, Database update logging, RTCN logging and Security logging on top of it this can sometimes become too burdensome and cause NCM jobs to fail.
    • Supports recommendation is to turn logging and session tracing OFF unless you're troubleshooting a specific issue, for some reason some think that is how NCM gets it information but this is simply not true


Services Involved


Add Description Here


Service Name


Software Package


Solarwinds Job Engine JobEngineV1 JEV1

Legacy polling

15-20% polling

Solarwinds Job Enginev2 JobEngineV2 JEV2 80% -85% polling

Examine the Logs

Orion produces numerous log files. These are the log files that would likely yield clues for this particular issue, in order of importance:

Log File Name

Located in:      NPM Server: C:\ProgramData\Solarwinds\Logs\Orion


  • Reproduce the issue first before looking at this log file
  • The newest entries are at the bottom
  • Handy search phrases -  take note of the time stamps so you can correlate them with Orion.Information.Service.log
This will jump to the next error in the log (you can generally ignore warnings)
  • Example errors:
2015-01-27 01:45:29,251 [19] ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - nodeId=22
2015-01-27 01:45:29,267 [19] ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - Error closing exception. System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state<snipped stack trace>

Windows Event Logs

Located in:    NPM Server: Go to Start > Run > eventvwr



•    Filter Windows Events so you can focus on Application, System and SolarWinds Events

•    Correlate errors found in Windows Events with other problems found in the other log files


Description here:





 Likely Root Causes 


Explore each of the potential root causes below to learn more about...


Root Cause 1 

Description -  Session Tracing could be turned on thus forcing the Database to Download Configs and then when its done to write a session trace to how it connected to the individual device

Root Cause 2

Description - Job Logging, Inventory Monitor logging, Database Updates logging, Real-Time Config Change Detection logging and Security logging could be turned on




Last modified



Internal Use Only