Pretty much everybody who actually runs an Evolution environment has been told by Support to restart Evolution services to clear up some condition, and there are quite a bit more subtleties (and landmines) in this seemingly-simple request.
I have written a new Evo Tip that describes the process for properly restarting Evolution services via the Evo Management Console, including the danger areas, and this might be useful to avoid unhappy surprises.
Note: If you are on the SaaS platform, Asure staff handles all this for you.
Evo Tip: Best Practices for Managing Evolution Services