Agreed. I've used FireDaemon in the past to manage 4D Servers running as a service but I don't think that works on WS2016 either.
> On Jul 25, 2018, at 9:36 AM, Uist Macdonald via 4D_Tech > <[email protected]> wrote: > > I agree in normal circumstances the OPEN ADMINISTRATION WINDOW view is fine. > It is in the case where something unexpected has gone wrong, although you > might think you have covered every error scenario with an ON ERROR proc. > With V16 if you don't use Interactive Services Detection then your 4D > procedure running on the server will just abort quietly as soon as it tries > to put up a dialog, or have I read the docs incorrectly. > > If 4D Server would at least write the dialog message to the system event log > then you would get a clue what was wrong. ********************************************************************** 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] **********************************************************************

