Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ServiceControl won't start #1670

markgould opened this issue Jun 5, 2019 · 3 comments


None yet
2 participants
Copy link

commented Jun 5, 2019

Upgraded two instances of SC to 3.8.1 and neither will start (both on same server). Appears to start and then after 30 secs or so, goes back to stopped.

Seeing some raven error about "Failed to execute transaction"

I've attached the log files. Let me know if I can do anything to further diagnose.



This comment has been minimized.

Copy link

commented Jun 6, 2019

@markgould I get slightly different symptoms but I'm pretty sure I am getting the same issue. I believe it is being caused by ServiceControl and the transport using different versions of Json.NET. As a temporary fix, you can put the right version into the folder and try to start the instances like this:

  • Find the installation of ServiceControl Management. By default this is C:\Program Files (x86)\Particular Software\ServiceControl Management
  • Open the zip file named Particular.ServiceControl-3.8.0
  • In the ServiceControl subdirectory, take a copy of Newtonsoft.Json.dll
  • Copy that file into the ServiceControl instance installation folder (linked in the Management Utility)
  • Restart the instance

That should get you going again. I'll start working on an official fix and get it into 3.8.2.

Thanks for reporting this.


This comment has been minimized.

Copy link

commented Jun 6, 2019

@mikeminutillo thanks for the quick response. That did indeed resolve it! The instance had version 10.x and the zip file had 12.x.

@mikeminutillo mikeminutillo added the Bug label Jun 6, 2019

@mikeminutillo mikeminutillo added this to the 3.8.2 milestone Jun 6, 2019


This comment has been minimized.

Copy link

commented Jun 7, 2019

@markgould 3.8.2 has now been released with this fix in place. Please upgrade your endpoints when you have an opportunity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.