Resolved

Thank you for checking- we will work on an update before a future release. Would you be able to update the folks on the 
thread you quoted, and either point them to this report, or tell them about the solution? 

I would recommend they not do what they were talking about- messing with the database files and re-installing like that 
is likely to lead to corrupt data or unexpected behavior. They should follow the below workaround for now.

Thanks~

We unfortunately don't have time to investigate this at the moment, but have something we would like you to try if 
you're willing:
There's no Estop flag in the database, so it's not recommended that you try to make any database edits. Instead, if 
someone is estopped and the flag won't clear, open the "Windows Services" panel on your machine and look for the two 
services that start with "FMS" (Base and SignalR are the names). After closing the FMS Software, right clock on each of 
those and select "Stop". Once they finish, wait a moment, then right click and "Start" those services again. You should 
be able to re-open the software and the estop flag will be cleared. Thanks