Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Unable to start an Orion agent service that monitors a node running Windows 2012 R2 after stopping it with the Service Control Manager

Unable to start an Orion agent service that monitors a node running Windows 2012 R2 after stopping it with the Service Control Manager

Updated July 19, 2017


After using the Service Control Manager to stop an Orion agent service that monitors a node running Windows 2012 R2, that Agent service cannot be restarted.



  • All SAM versions
  • Windows 2012 R2



A job stored in the JobEngine plugin database is normally deleted from the database after it’s executed. In this situation, the job to stop the Orion agent service (created when the Orion agent service was stopped with the Service Control Manager) was executed, which stopped the Orion agent and polling. Because polling was stopped, the job was not deleted from the JobEngine plugin database. 

Note: The JobEngine plug-in database is located on the agent machine.


When attempting to start, the Orion agent automatically checks the JobEngine plug-in database for missed jobs. In this case, the Orion agent finds the same job that wasn’t deleted and executes it again, which stops the Orion agent and polling, and the job is not deleted from the JobEngine plugin database. This results in an endless cycle where the Orion agent cannot be completely started.



Reinstall the affected Orion agent and delete the JobEngine plugin database, which will remove any jobs that are instructing the Orion agent to stop.



  1. Uninstall the Orion agent that won’t start.
  2. Delete the JobEngine plug-in database: %ProgramData%\Solarwinds\JobEngine.v2.agent\Data\JobEngine35.sdf
  3. Re-install the affected Orion agent.
  4. Start the Orion agent. 
  5. Restart Orion Poller to restart polling.


Do not use the Service Control Manager to start or stop the affected Orion agent. Start and stop it manually.

For example, using the command prompt:
net stop "SolarWinds Agent"
net start "SolarWinds Agent"



Last modified