After just updating from prunsrv x64 1.1.0 to 1.2.0, we are finding that prunsrv will no longer start our service under the "local service account".
It is very strange, as if I launch a cmd.exe as the Administrator User, and run `prunsrv //TS/FusionDB-Server` then it starts up correctly on the console. However if we run `prunsrv //ES/FusionDB-Server` then we see the following errors in service.log: [2019-08-30 23:06:04] [info] [ 5336] Starting service 'FusionDB-Server'... [2019-08-30 23:06:08] [error] [ 5336] apxServiceControl(): dwState(4) != dwCurrentState(1); dwWin32ExitCode = 0, dwWaitHint = 0, dwServiceSpecificExitCode = 0 [2019-08-30 23:06:08] [error] [ 5336] apxServiceControl(): returning FALSE [2019-08-30 23:06:08] [error] [ 5336] Failed to start service 'FusionDB-Server'. [2019-08-30 23:06:08] [info] [ 5336] Finished starting service 'FusionDB-Server', returning 0. [2019-08-30 23:06:08] [error] [ 5336] Apache Commons Daemon procrun failed with exit value: 5 (failed to start service). If however we use the Windows Service Manager to modify the service to run under the "Local System Account" (see attached screenshot), then after that, running `prunsrv //ES/FusionDB-Server` starts the service correctly. Ideally we don't want to run under the `Local System Account` we want to use the `local service account` instead. This seemed to work well with version 1.1.0 but is not working for us with version 1.2.0. Thanks and please can you help us... We are testing on Windows 10 x64. -- Adam Retter skype: adam.retter tweet: adamretter http://www.adamretter.org.uk
--------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
