Hi, Even when initiated from the 4D-end, it might not always be a graceful exit because the service times out when trying to stop. Had encountered this on more than a few occasions with a client, end up we had to rebuild the “damaged” data file and indices. The error message at end of repair is something to the effect that data flushing did not complete (the database application has a 24/7 listener that receives incoming messages from other systems).
Sent: Thursday, August 8, 2019 1:20 PM To: [email protected] <mailto:[email protected]>; 4D iNug Technical <[email protected] <mailto:[email protected]>> Subject: Re: Windows shutdown with 4D Server running as a service I am assuming that your Administrative function runs on a client? Sounds like a good idea, but wondering if it might be a bit over kill for me. Bottom line is that at some point the server is quit without regard to who is logged in at the time whether done with a quit command or issued by the Windows service. The admin can see who is logged by firing up a client on the server and opening the Administration window before shutting down the computer or shutting down the service. If after hours the admin may have no choice but to let 4D server boot the clients off. > From what I gather from the responses, it really does not matter as for as 4D > is concerned, it will “gracefully" quit any 4D client hanger ons before > quitting no matter how it is told to quit. There should never be any damage > to the data. Thanks to those who responded. John ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
