Network Management

Large number of JET files in C:\Windows\Temp on the Orion Server

This article explains how JET files consume disk space in C:\Windows\Temp folder on the Orion server

First published date

10/19/2018 8:32 PM

Last published date

2/22/2025 7:27 PM

Overview

The SolarWinds Platform may have many JET files in the C:\Windows\Temp folder. This may cause warnings on the Deployment Health page of the Orion Web Console or in Active Diagnostics:
"FileCleaner: An Error has occurred during the log files clean process. The file is being used"

The following may be found in the swdebugmaintenance log at C:\Programdata\Solarwinds\Logs\Orion:

ERROR SolarWinds.Data.FileSystemMaintenance.FileCleaner - FileCleaner: An Error has occured during the log files clean proccess. The file is being used
System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\JETAD12.tmp' because it is being used by another process.

INFO  SolarWinds.Data.FileSystemMaintenance.FileCleaner - FileCleaner: Ended cleaning. Failed to delete 1 file(s). Deleted: Deleted 2 file(s), Location: C:\Windows\Temp, Pattern: JET*.tmp, Files to handle: All, Include sub-directories: False

Product section

Network Performance Monitor

Cause

The Collector service in the SolarWinds Platform creates a temporary connection file in C:\Windows\Temp with the name JETxxxx.tmp (xx is a hexadecimal number). These JET files will eventually use all possible file name combinations, consuming disk space, and the Collector will fail to create a new one.

Resolution

If the problem is occurring on the SolarWinds Platform 2024.2 and above, please open a support ticket with SolarWinds support so we can continue to investigate the root cause.  To workaround this problem, perform the following steps below:

  1. Stop all Orion services
  2. Delete C:\Windows\Temp\SolarWinds
  3. Delete all other *.tmp files starting with 'JET' in C:\Windows\Temp
  4. Start Orion services

This error does not impact the Database Maintenance procedure and can be safely ignored.

  • Part of the Database Maintenance is to remove unused JET files, and since there are files still in use, the Database Maintenance will not be able to remove and an error will be logged for it.
  • This is not a bug and can be ignored as auto or manual Database Maintenance is completed successfully.
  • The JET files are created by the Collector, and both Traps and Syslog services use the Collector as an endpoint

If database maintenance is not completed, you may look for further errors in the log or contact Solarwinds Support to investigate.