From: Andrew P. <at...@pi...> - 2014-10-20 20:07:17
|
Is anyone running Naviserver as a Windows service? That always worked fine for me with AOLserver. With Naviserver, installing the service works fine. (Just make sure your Command Prompt has Administrator privileges when you do the service install with -I). But when I actually start the service, it IMMEDIATELY fails with: Error 1053: The service did not respond to the start or control request in timely fashion. A timeout was reached (30000 milliseconds) while waiting for the NaviServer service to connect. Note, it does NOT try for 30 seconds first. When I click "Start", I id immediately gives me the "Error 1053" pop-up box, and posts the "timeout was reached" error to the Windows Event Log. Nothing at all gets written to the log file, so I'm not sure how to debug this. But presumably that means something is dying very early, perhaps in NsConnectService()? -- Andrew Piskorski <at...@pi...> |