Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > When should Job Engine and/or Collector .sdf files be replaced?

When should Job Engine and/or Collector .sdf files be replaced?

Table of contents

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 or recommended. SolarWinds Development has provided the following information to clarify when .sdf files should be replaced.

Job Engine

Job Engine v1 and Job Engine v2 are both currently provided with all Orion installations. You can find the .sdf files in the following locations:

  • %AllUsersProfile%\Application Data\Solarwinds\JobEngine\Data (Job Engine v1)
  • %AllUsersProfile%\Application Data\Solarwinds\JobEngine.v2\Data (Job Engine v2)

To determine if an .sdf file replacement is necessary, review the following log files:
Note: Version numbers may change as newer versions are released.

  • %AllUsersProfile%\Application Data\Solarwinds\JobEngine\Logs\SolarWinds.JobSchedulingService_v1_5.txt
  • %AllUsersProfile%\Application Data\Solarwinds\JobEngine.v2\Logs\SolarWinds.JobEngineService_v2_1.txt

The relevant error message will display as follows:

SolarWinds.JobEngine.ServiceProcess.StartCanceledException: Start is canceled --->
SolarWinds.JobEngine.Data.DatabaseCorruptedException: The job scheduler database file is corrupted
    at SolarWinds.JobEngine.Data.SqlCeHelper.Verify()
    at SolarWinds.JobEngine.Scheduling.SchedulerServiceApp.Start()
    --- End of inner exception stack trace ---
    at SolarWinds.JobEngine.Scheduling.SchedulerServiceApp.Start()
    at SolarWinds.JobEngine.ServiceProcess.SolarWindsService.ServiceStart()

If you see this error in either or both log files, the corresponding .sdf file is corrupt, and it must be replaced.

Notes:

  • If only one version is reporting this error, it is not necessary to replace the .sdf files for both versions.
  • After replacing the .sdf file(s), you should also restart the Orion Module Engine to ensure that jobs are rescheduled properly.
  • If you are replacing the Job Engine v2 .sdf file on an additional poller, you must be sure to replace the .sdf file on the main poller.
  • Some data is shared between these .sdf files. If you replace an .sdf file on the main poller, you are not required to replace the same .sdf file on any additional pollers.
If you run into a case where you see this error in the Job Engine, please collect diagnostics and let SolarWinds know. We need the information so we can determine why the .sdf file is being corrupted.

Collector

The Collector has two .sdf files, found in %AllUsersProfile%\Application Data\Solarwinds\Collector\Data\.

To determine if an .sdf file replacement is necessary, review the following log files:

  • %AllUsersProfile%\Application Data\Solarwinds\Collector\Logs\DataProcessorService.log
  • %AllUsersProfile%\Application Data\Solarwinds\Collector\Logs\ManagementAgentService.log
  • %AllUsersProfile%\Application Data\Solarwinds\Collector\Logs\PollingControllerService.log

If the Collector .sdf files have been corrupted, the following error will display:

FATAL SolarWinds.Collector.Services.CollectorService - Error starting service.System.Runtime.Serialization.SerializationException: The constructor to deserialize an object of type 'System.Data.SqlServerCe.SqlCeException' was not found. --->
System.Runtime.Serialization.SerializationException: The constructor to deserialize an object of type 'System.Data.SqlServerCe.SqlCeException' was not found.

If you see this error, the .sdf file is corrupt, and it must be replaced.

Notes:

  • Unlike the Job Engine, Collector .sdf files are shared across services, so Development suggests replacing both .sdf files.
  • After replacing the .sdf file(s), you should also restart the Orion Module Engine to ensure that jobs are rescheduled properly.
If you run into a case where you see this in the Collector, please collect diagnostics and let SolarWinds know. As with the Job Engine, we need the information so we can determine why the .sdf file is being corrupted.

This article applies to all versions of all currently supported Orion products
Last modified
14:06, 13 Nov 2015

Tags

Classifications

Public