[
https://issues.apache.org/jira/browse/DAEMON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979414#comment-16979414
]
Mark Thomas commented on DAEMON-411:
------------------------------------
OK. I've figured out why this is. You have to be running as LocalSystem to be
interactive and the default user changed to LocalService. This requirement is
documented but even with the correct --ServiceUser this won't work.
The error handling needs some improvement and I'll fix the start-up so you can
use --Type=interactive if you specify the correct user. I'll also look at the
Manager app to ensure it enforces the same requirement.
> Services can't be installed as Type=Interactive anymore
> -------------------------------------------------------
>
> Key: DAEMON-411
> URL: https://issues.apache.org/jira/browse/DAEMON-411
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.2.0
> Environment: openjdk version "1.8.0_222"
> OpenJDK Runtime Environment (Zulu 8.40.0.25-CA-win64) (build 1.8.0_222-b10)
> OpenJDK 64-Bit Server VM (Zulu 8.40.0.25-CA-win64) (build 25.222-b10, mixed
> mode)
> Tested on Windows 10 1607 and Windows 7 7601.
> Reporter: Markus Adelsberger
> Priority: Major
> Labels: windows
> Attachments: prunsrv.png
>
>
> Installing a service with the parameter --Type=interactive no longer works.
> prunsrv.exe outputs:
> {code:java}
> prunsrv.exe //IS//MyService
> --Install="C:\service\commons-daemon-1.2.2-bin\windows\amd64\prunsrv.exe"
> --Type=interactive --ServiceUser="LocalSystem"
> The parameter is incorrect.
> Failed to install service.{code}
> No other log is output, even with Debug level. As a workaround the service
> can be installed without the type interactive and then updated to use the
> flag.
> The same call still worked in 1.1.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
