01-02-2021, 01:10 PM
(01-02-2021, 08:09 AM)Dean Roddey Wrote: Not sure what's going on there. Something similar has happened before, and it's always after an upgrade. Or for me locally, after a full rebuild. The only thing I can see that's common there is that all of the previously cached DLLs are going to be thrown out and all the new code has to be loaded up. Maybe that's causing some delay that's on the hairy edge and something is timing out on the server, and it fails to register the remote interface.
When you restart it, Windows already has the DLLs all cached up and in memory, so it doesn't happen presumably.
This is a common issue. Why not force a reboot or CQC services restart after an installation?