Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Low disk space on an Orion Server due to large diagnostics

Low disk space on an Orion Server due to large diagnostics

Created by Kevin Twomey, last modified by Magdalena.Markova on Oct 04, 2017

Views: 649 Votes: 1 Revisions: 17

Updated: October 4, 2017


This article answers how to investigate whether the SolarWinds software might be the cause of your Orion Servers running out of disk space.

Orion Platform products should not cause disk space issues except for the cases when you enable DEBUG logging or when you store NCM files on your C:\ drive. 

SolarWinds software does not control Windows Error Reporting files.


  • Any Orion Platform


Low disk space caused by Orion Platform software could have various reasons, including the following:

  • NCM Configurations stored in the SolarWinds ProgramData folder.

  • NCM Session tracing is on.

  • DEBUG Logs are not turned off.

SolarWinds file locations

Orion Platform software has 4 main folder locations: 

  • C:\Inetpub\SolarWinds
  • C:\Windows\System32\msmq\storage\
  • C:\Program Files (x86)\SolarWinds\ 

    • If this folder contains a copy of the NCM Config-Archive, move it to another location to save disk space.

  • C:\ProgramData\Solarwinds\
    • This folder can take up 2-4 GB of data. It contains the MIB Database (500 MB) and installer files (1 GB). These files should not be removed.
    • On the other hand, the folder contains rolling logs. These should grow only when extra logging is enabled.

File location recommendations

  • The Program Files & Inetpub folders should remain static and can be configured during the install to point to other disk Drives.
  • ProgramData & MSMQ locations should remain in their default locations, that is at C:\Program Files (x86)\SolarWinds\.


To save disk space, complete the following steps:

Clean up orphaned Log Files

You might have folders with thousands of log files that can be deleted without issues. Delete any files with the .LOG or .LOG.1-5 suffix.

To clean up SolarWinds logs, open the command line as an administrator, and run the following commands to clean up roll-over logs:

del /f /q /s C:\programdata\solarwinds\*.log
del /f /q /s C:\programdata\solarwinds\*.log.*


Keep Diagnostics tables small

Edit Diagnostics Config files not to pull back large tables.


Reset all logging to default

  1. Launch LogAdjuster using one of following method:
    • Run c:\Program Files (x86)\SolarWinds\Orion\LogAdjuster.exe
    • Click Start > RUN > All Programs > Solarwinds Orion > Documentation and Support > Orion Log Adjuster
  2. In the Log Adjuster, select Reset to defaults, and click Apply.


Move NCM Config files from their default location

If you do not have the NCM module, you may skip this step.
If your environment site has NCM installed, NCM might store large folders of NCM-specific data.

  • If NCM configuration files are stored in SolarWinds folder, move them to another drive, and set up a new default location using NCM web settings pages.
  • Disable NCM SESSION-TRACING and delete the files.

NCM 7.3

NCM v7.3 stores downloaded Configs in NCM_ConfigArchive Table. Users often save a copy of Config to Disk ( ..Solarwinds\Orion\NCM\Config-Archive) which results in huge folders.

To resolve this issue:

  • Set up NCM download config jobs to only store config files changed since the last download.
  • Edit the default location for storing Config-Archive files to be outside of the install folders.

Consequences of Config-Archive files being outside of the install folders:

  • Orion Business Layer might take an hour to load because it needs to read these files
  • Diagnostics might be slow to run, the zip file being large because NCM pulls back these files
  • LicenseManager\PermissionChecker might be slow or crash because it needs to read each file in Config Folder.

In NCM 7.3.1, you can set the default location for storing Configs during the Configuration wizard. Users are also informed how to resolve the issue by a popup in the Orion Web Console. See the following THWACK post for more details.

Clean up NCM Session Trace files or move them from the default location

If you do not have the NCM module, you may skip this step.
When Session Tracing is enabled, the following files are created:SwTelnetDebug.log and Session Traces files.

If you turn on Session Trace, be sure that you turn it off after you have collected the traces you need. To save disk space, delete the trace files. Do not keep session traces unless you are troubleshooting an issue.

How to setup an NCM Session Trace

  1. Open the Orion Web Console.
  2. Click Settings > All Settings, and then NCM settings.
  3. In the Advanced section, click on Advanced settings.
  4. Select Enable Session Tracing.
  5. Stop and start the NCM application on the NCM server.
  6. Once the error has been reproduced please turn off the session trace and send me a copy of the trace and debug file.

How do you change where session trace files are stored

By default, the session trace files are stored at C:\Program Files\Solarwinds\Configuration Management\Session-Trace\

To edit their location, go to NCM Web Setings.


Suggested Tags:  Diagnostics low disk space


Reason for Rework or Feedback from Technical Content Review:



Last modified