Repository navigation
[JENKINS-12660] Fail to start the windows service when trying to launch agent node #12443
Description
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:
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
...
Originally reported by rico_bee, imported from: Fail to start the windows service when trying to launch agent node
- status: Resolved
- priority: Major
- component(s): core, windows-slave-installer-module
- label(s): remoting, winsw
- resolution: Fixed
- resolved: 2020-07-23T15:42:09+00:00
- votes: 5
- watchers: 13
- imported: 2025-11-24
Raw content of original issue
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:
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 ...
environment
Master : Redhat 5<br/>
Slave Node : Win7 x64
Activity
jenkins-infra-bot commentedon Feb 7, 2012
Raw content of original comment:
Had the same today installing a Windows Server 2008 R2 x64 node using the local admin account.
However, I added another node with the same OS to the same Master successfully this morning too but with a domain account.
Master is 1.444
jenkins-infra-bot commentedon Feb 8, 2012
Raw content of original comment:
Have the same issue as well as stated above, master is 1.450, slave a Windows Server 2008 R2 x64.
jenkins-infra-bot commentedon Feb 23, 2012
bhuggins:
Raw content of original comment:
I had the same issue but was able to resolve it by using \
jenkins-infra-bot commentedon Mar 6, 2012
lunatic:
Raw content of original comment:
The same issue. Master is 1.451, slave - Windows Server 2003.
jenkins-infra-bot commentedon Mar 8, 2012
ffromm:
Raw content of original comment:
changed to master/slave component as it is not related to the slave-setup plugin.
jenkins-infra-bot commentedon Mar 19, 2012
Raw content of original comment:
So what I did was add the Machine-Name part to the user names:
Launch method: Let Jenkins control this Windows slave as a Windows service
Administrator user name: .\Administrator
Password: ***
Host:
Run service as: Log on using a different account
User name: .\Builder
Password: ***
jenkins-infra-bot commentedon Mar 26, 2012
walterk82:
Raw content of original comment:
I'm getting a similar problem with Jenkins 1.451 and 2008 R2
However, I'm trying to use a managed Service Account under the domain.
jenkins-infra-bot commentedon May 4, 2012
tomfanning:
Raw content of original comment:
Prefixing the username with "computername\" resolves this issue for me.
jenkins-infra-bot commentedon May 7, 2012
Raw content of original comment:
That has worked for me as well, thanks! - added "computername\" before Administrator user name as Tom mentioned and set 'Run service as' to be "Use Administrator account given above".
jenkins-infra-bot commentedon Nov 5, 2012
da7489:
Raw content of original comment:
Adding "computername\" before the username worked for me.
jenkins-infra-bot commentedon Mar 12, 2013
Raw content of original comment:
Adding ".\" before the username worked for me. Using '.\' is the same as using the local domain. If you type in .\ before the username, that will instruct it that you are logging onto the local computer.
jenkins-infra-bot commentedon Aug 7, 2013
knagarjuna:
Raw content of original comment:
Facing same issue with following configuration:
Java Version: 1.7.0-25
Slave : Windows 2008 R2-64Bit
But the approach ".\Username" is not solving problem in my case.
In system events found error saying logon failure due to incorrect username or password even though provided correct credentials.
jenkins-infra-bot commentedon Jun 24, 2014
Raw content of original comment:
Its is mostly a documentation bug.
WinSW should explicitly mention that user name should be specified along with its domain
jenkins-infra-bot commentedon Jun 28, 2014
Raw content of original comment:
Alternatively, if the user name does not contain a backslash,prefix with .\
jenkins-infra-bot commentedon Jan 8, 2017
Raw content of original comment:
Still actual, I'd guess. Will verify it and cross-post a bug to WinSW if it still exists
jenkins-infra-bot commentedon Mar 7, 2017
rpovelik:
Raw content of original comment:
Still actual!!!
[2017-03-07 21:49:25] [windows-slaves] Starting the service ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy56.start(Unknown Source) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:340) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.jinterop.JInteropInvocationHandler.invoke(JInteropInvocationHandler.java:140) ... 8 more Caused by: org.jinterop.dcom.common.JIException: Service Logon Failure at org.jvnet.hudson.wmi.Win32Service$Implementation.start(Win32Service.java:149) ... 13 more
jenkins-infra-bot commentedon Jan 30, 2018
Raw content of original comment:
Managed to make this occur, not sure if this helps debug / resolve the issue. On a windows 10 slave that was working, I turned on auto logon so my admin user would logon automatically at boot time. Once I did this the same issue above started happening. To which .\username and hostname\username could not rectify the issue. I also disabled auto login and the problem still persists. I will likely build the slave up from scratch again.
Server: Jenkins:lts docker image, ver 2.73.2, jdk8+
Client Windows 10, jdk8+
jenkins-infra-bot commentedon Mar 4, 2018
Raw content of original comment:
phopkins101 not sure they are the same. You one looks like a bug in vSphere Cloud Plugin
jenkins-infra-bot commentedon Apr 24, 2018
1digerati:
Raw content of original comment:
Manually setting the log on credentials within the service itself directly on the Win 7 box fixed it for me. Used the same creds, but when doing it manually Windows grants the Service Logon right to the user.
jenkins-infra-bot commentedon Jul 23, 2020
Raw content of original comment:
This issue was resolved by nextturn in Windows Service Wrapper 2.7.0: https://github.com/winsw/winsw/releases/tag/v2.7.0 . This version was integrated into Jenkins 2.248.