[ https://issues.jenkins-ci.org/browse/JENKINS-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159902#comment-159902 ]
Sergey Titov edited comment on JENKINS-12660 at 3/6/12 11:17 AM: ----------------------------------------------------------------- The same issue. Master is 1.451, slave - Windows Server 2003. was (Author: lunatic): The same issue. Master is 1.451, slave - WinXP. > Fail to start the windows service when trying to launch slave node > ------------------------------------------------------------------ > > Key: JENKINS-12660 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12660 > Project: Jenkins > Issue Type: Bug > Components: slave-setup > Affects Versions: current > Environment: Master : Redhat 5 > Slave Node : Win7 x64 > Reporter: Rico ZHANG > Assignee: Kohsuke Kawaguchi > > We used to be able to launch the slave node successfully, but it did not work > since we upgraded the jenkins to latest version (1.449) > It doesn't dump any exception to the console, but I captured the output: > {noformat} > Connecting to 192.168.160.62 > Checking if Java exists > java full version "1.7.0-b147" > Installing the Jenkins slave service > Copying jenkins-slave.exe > Copying slave.jar > Copying jenkins-slave.xml > Registering the service > ERROR: Failed to create a service: Status Invalid Service Account > ... > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira