Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December15 - Deletes > Job Engine Worker prevents switch over to happen

Job Engine Worker prevents switch over to happen

Created by Mariusz Handke, last modified by Jessica Solis on Dec 15, 2017

Views: 639 Votes: 1 Revisions: 6


This article provides a resolution to the issue where the Job Engine Worker prevents switch over to happen.


All FoE versions


This issue is caused by the fact that Job Engine Worker, either 32bit - SWJobEngineWorker2.exe or 64bit - SWJobEngineWorker2x64.exe remains running and the Job Engine process itself having lost control over it thus processes are orphaned. As they run, they are blocking access to some of libraries (DLL) and FoE keeps trying to synchronize files between nodes but fails to complete the task.


The only way of solving this issue, since FoE has to monitor Orion components, is to kill offending processes manually:

  1. Log in to the server in question.
  2. Open Windows Task Manager.
  3. Scroll to the relevant processes.
  4. Select and kill the process.
Last modified