Network Management

The job scheduler database file is corrupt in the Orion Platform

This article provides brief information and steps to resolve the following error: The job scheduler database file is corrupt. The SWJobSchedulerSvc service has been shutdown until the database is fixed.

First published date

10/9/2018 8:30 PM

Last published date

2/17/2022 4:28 PM

Overview

This article describes how to resolve the following error message: 
 
The job scheduler database file is corrupt. The SWJobSchedulerSvc service has been shutdown until the database is fixed.

This error indicates a corrupted JobEngine.sdf file in your SolarWinds Network Performance Monitor (NPM) installation. 

For log review, you may check the Job Engine V2 or Collector logs.

Product section

Network Performance Monitor

Cause

The JobEngine35.sdf file is corrupt, or damaged and needs to be replaced.

Resolution

Your Orion NPM installation includes a blank database file titled JobEngine35 - Blank.sdf. Create a copy of this file to replace your corrupted JobEngine.sdf file. 
 
  1. Log in to your Orion server using an account with administrative rights.
  2. Click Start and select All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager.
  3. Click Shutdown Everything (this process may take several minutes to complete).
  4. Locate the JobEngine35.sdf and JobEngine35 - Blank.sdf files, the default location is:

    c:\ProgramData\SolarWinds\JobEngine.v2\Data\

  5. Make a backup copy of your current JobEngine35.sdf file and rename it JobEngine35.old.
  6. Make a backup copy of your JobEngine35 - Blank.sdf file and rename it JobEngine35.sdf, overwriting your corrupted file.
  7. Right-click your new JobEngine35.sdf file and select Properties. 
  8. In the General tab, verify that the Read-only check box is cleared, and click OK.
  9. Close the file directory. 
  10. On your Orion server, click Start and select All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager.
  11. Click Start Everything (this process may take several minutes to complete).
If the issue still persists, try to repair the Microsoft SQL Server Compact 3.5 ENU (both x86 and x64) through Programs and Features.