Repair a failing Job Engine and Collector Components

Always make sure you have a recent backup of SQL and SolarWinds NPM.
See How to Backup the Orion SQL database.

Replacing Job Engine and/or Collector .sdf files is a commonly used step to address a number of potential issues with Orion installations, but it is not always required. For more information, see The job scheduler database file is corrupt

Potential symptoms include devices not polling: nodes, volumes, interfaces, hardware sensors, applications, component monitors, etc., and charts missing polled data. Web console showing nodes, not polling. Objects are in an unknown status.

If a node is unmanaged and then re-managed after performing maintenance work, it's possible for the related polling jobs to become stuck and the node will show as Unknown in the Web Console. 

SolarWinds Platform 2024.1  and above.

Collector:
1. RDP to the SolarWinds Platform Server.
2. Stop the SolarWinds Collector via the SolarWinds Platform Service Manager on all SolarWinds Platform servers.
3. Navigate to C:\ProgramData\Solarwinds\Collector\Data.
4. Delete the PollingController.db and PollingController.db-journal files.



5. Start the service once more via the SolarWinds Platform Service Manager.
6. The files will be rebuilt automatically. Please note that this may take 1-2 minutes after the service is restarted for the files to be created.

Job Enginev2:
1. RDP to the SolarWinds Platform Server.
2. Stop the SolarWinds Job Engine via the SolarWinds Platform Service Manager on all SolarWinds Platform servers.
3. Navigate to C:\ProgramData\Solarwinds\JobEngine.v2\Data.
4. Delete everything in this folder.



5. Start the service once more via the SolarWinds Platform Service Manager.
6. The files will be rebuilt automatically.

NOTE:

• The JobEngine.v2 no longer has db-journal file and only has the JobEngine.db file. Once the services have been stopped, the following files will disappear inside the Job Engine.v2\Data folder.
  • JobEngine.db-shm
  • JobEngine.db-wal
• Once the services have been started, the JobEngine.db-shm and JobEngine.db-wal will appear.
• For the JobEngine.v2.agent, it still has the db and db-journal files same as the Collector Service.

Job Enginev3:

1. RDP to the SolarWinds Platform Server.
2. Stop the SolarWinds Job Enginev3 via the SolarWinds Platform Service Manager on all SolarWinds Platform servers.
3. Navigate to C:\ProgramData\Solarwinds\JobEngine.v3\Data.
4. Delete everything in this folder.



5. Start the service once more via the SolarWinds Platform Service Manager.
6. The files will be rebuilt automatically.

SolarWinds Platform 2022.2 - 2023.4

Collector:
1. RDP to the SolarWinds Platform Server.
2. Stop the SolarWinds Collector via the SolarWinds Platform Service Manager on all SolarWinds Platform servers.
3. Navigate to C:\ProgramData\Solarwinds\Collector\Data.
4. Delete the PollingController.db and PollingController.db-journal files.
5. Start the service once more via the SolarWinds Platform Service Manager.
6. The files will be rebuilt automatically.

Job Engine:
1. RDP to the SolarWinds Platform Server.
2. Stop the SolarWinds Job Engine via the SolarWinds Platform Service Manager on all SolarWinds Platform servers.
3. Navigate to C:\ProgramData\Solarwinds\JobEngine.v2\Data.
4. Delete the JobEngine.db and JobEngine.db-journal files.
5. Start the service once more via the SolarWinds Platform Service Manager.
6. The files will be rebuilt automatically.

SolarWinds Platform 2020.2.6 and lower

a. Collector Service
1. RDP to the SolarWinds Platform Server using Local Administrator account.
2. Open the Orion Service Manager and shut down everything.
NOTE: You can leave the dependencies running.
3. Go to the path C:\ProgramData\SolarWinds\Collector\Data
4. Rename the PollingController.sdf to PollingController.sdf.old.



5. Copy the PollingController-Blank.sdf then paste it inside the folder.
6. Rename the PollingController-Blank.sdf to PollingController.sdf 
7. Start everything via the Orion Service Manager.

b. Job Engine
1. RDP to the SolarWinds Platform Server using Local Administrator account.
2. Open the Orion Service Manager and shut down everything.
NOTE: You can leave the dependencies running.
3. Go to the path C:\ProgramData\SolarWinds\JobEngine.v2\Data
4. Rename the JobEngine35.sdf to JobEngine35.sdf.old.

5. Copy the JobEngine35 - Blank.sdf then paste it inside the folder.
6. Rename the JobEngine35 - Blank.sdf to JobEngine35.sdf 
7. Start everything via the Orion Service Manager.

NOTE: After renaming the JobEngine35 - Blank.sdf and PollingController-Blank.sdf, right-click on the newly created files and select properties and remove the check on read-only. If read only is checked the services will not start.

or 

1. RDP to the SolarWinds Platform Server using Local Administrator account.
2. Go to the Control Panel and take note of the following services and their versions:

• SolarWinds Collector v2.XX.XXXXX
• SolarWinds JobEngine v2.XX.XXXXX

NOTE: Make sure to take note of the version.
3. Go to the path C:\ProgramData\SolarWinds\Installers and check for the following:

• SolarWinds Collector = COLLECTOR-2.XX.X.XXXX-CollectorInstaller.msi
• SolarWinds JobEngine v2 = JOBENGINE-2.XX.X.XXXXX-JobEngine.v2.msi

4. Shut down everything via the Orion Service Manager.
5. Go back to the Control Panel and uninstall the SolarWinds Collector v2 and SolarWinds Job Engine v2.
NOTE: Rebooting the server after uninstall can be optional.
6. Reinstall the SolarWinds Collector and SolarWinds Job Engine using the msi files located in C:\ProgramData\SolarWinds\Installers.
7. Start everything via the Orion Service Manager.