I can only guess ... We experienced something similar in the past, but always it reveals to be a problem caused by us. An example: Usually our server apps are updated automatically during the night, so the service hat to be restarted by the update script. In nearly all cases it works very well, but it happened that there were an error in the startup code of the new version and we got a problem. Not nice, but ...
If we are faced with such problems, I restart the server app as a normal application not as a service, only to look if there are some error messages thrown by the 4D server. Unfortunately all these messages are not logged into a file by 4D, so I have to go the way via application start. Theoretically it could be a problem with the interactive services if you use them. These services are more and more restricted by Microsoft. We don't use them. Finding the real cause of the problem is rather difficult or even not possible. If you restarted the service and all was going well there isn't any chance to get the cause. You can try to have a look at the Windows Eventlog but the messages by 4D are mostly not helpful. Regards Lutz ********************************************************************** 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] **********************************************************************
