You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mladen Turk (Commented) (JIRA)" <ji...@apache.org> on 2011/10/29 13:51:32 UTC

[jira] [Commented] (DAEMON-215) Cannot set local username and password for a Win32 service

    [ https://issues.apache.org/jira/browse/DAEMON-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139198#comment-13139198 ] 

Mladen Turk commented on DAEMON-215:
------------------------------------

According to the MSDN this seems to be the case.
Will be fixed with 1.0.8
                
> Cannot set local username and password for a Win32 service
> ----------------------------------------------------------
>
>                 Key: DAEMON-215
>                 URL: https://issues.apache.org/jira/browse/DAEMON-215
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.7
>         Environment: win32 / server 2003
>            Reporter: wessels
>            Priority: Minor
>             Fix For: 1.0.7
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> installing a new service without supplying the --ServiceUser --ServicePassword installs the service correctly but using the LocalSystem account. If you want to use a local user, which of course has at least the "log on as a service" right, and supply the credentials via the parameters you get an error. To be more specific, in service.c line 211, the CHANGE_SERVICE macro fails with error 87L ERROR_INVALID_PARAMETER. This happens at least when creating and updating a service. Setting other options via this macro work fine, just the username password fail (standalone and in combination with other parameters).
> The solution is specifying SERVICE_WIN32_OWN_PROCESS as ServiceType parameter instead of SERVICE_NO_CHANGE in ChangeServiceConfigW line 27 second parameter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira