When attempting to launch a headless 4D Server and the server is automatically quitting, it may be indicating that a blocking dialog was encountered during start up.

When launching as headless, 4D simulates pressing "ok" for dialogs that require only an "ok" action. This closes the dialog and allows the server to continue to run. Some examples of these non-blocking dialogs are ones generated from ALERT, CONFIRM, or Request.

However, when a headless server encounters dialogs that require more than just an "ok" action, 4D will automatically quit. Some examples of these blocking dialogs include ones generated when no data file is found, no license is found, no log file is found, and anything else that requires the server administrator to intervene. 4D quits in these scenarios becuase it does not know what to do.