-
Bug
-
Resolution: Won't Fix
-
Minor
-
Jenkins 2.32.2 on Windows 2012 R2
Slaves machines Windows 10 x64 and Windows 8.1 x64
Windows slaves plugin 1.1 and 1.2
Updated Jenkins from 2.7.4 to 2.32.2 and now my agent machines wont connect using Launch method "Let Jenkins control this Windows slave as Windows service". They were working fine on the older version.
I uninstalled and installed agent services on the machines but that didnt help.
Looked into https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM and that didnt help either.
Tried windows slaves version 1.2 and 1.1 still nothing changed.
Here is the error message I get
ERROR: Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this.
org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x00000005
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:542)
at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:458)
at org.jinterop.dcom.core.JIComServer.<init>(JIComServer.java:427)
at org.jvnet.hudson.wmi.WMI.connect(WMI.java:59)
at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:206)
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: rpc.FaultException: Received fault. (unknown)
at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:142)
at rpc.Stub.call(Stub.java:112)
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538)
... 10 more
[JENKINS-41892] Let Jenkins Control this Windows agent as a windows service does not work after updating to 2.32.2
ahmed daniel
created issue -
Some diagnostics:
- JInterop dependency comes from https://github.com/kohsuke/j-interop, no updates since Windows Slaves plugin decoupling in 2014. https://github.com/jenkinsci/jenkins/commit/2669e4a86d72f2d8b67417812db8f52aa487f3de
- WMI class is located in https://github.com/jenkinsci/extras-jinterop-wmi , no changes since 2011 (have never seen this repo before...)
- ManagedWindowsServiceConnector is located in Windows Agents plugin, no changes since 2014: https://github.com/jenkinsci/windows-slaves-plugin/blob/5a2040a959b17253eced765da1177ae0dcd3957f/src/main/java/hudson/os/windows/ManagedWindowsServiceConnector.java
I have no idea what could cause the regression in the Jenkins 2.32.2. But I will put it to the core queue and unassigned kohsuke since he does not triage incoming issues anyway
| Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: Oleg Nenashev [ oleg_nenashev ] |
| Component/s | New: core [ 15593 ] | |
| Component/s | New: windows-slave-installer-module [ 21834 ] |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
| Labels | Original: service slaves, windows, | New: service slaves windows |
Having the same issues here on my end. Looking at the guide did not help as well.
Encountering this issue when trying to let Jenkins control this window slave as a window service.
ERROR: Message not found for errorCode: 0x8001FFFF org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x8001FFFF at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:876) at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:825) at org.jinterop.dcom.core.JIComServer.addRef_ReleaseRef(JIComServer.java:909) at org.jinterop.dcom.core.JISession.releaseRef(JISession.java:730) at org.jinterop.dcom.core.JIComServer.createInstance(JIComServer.java:746) at org.jvnet.hudson.wmi.WMI.connect(WMI.java:61) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:208) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:285) 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.net.ConnectException: Operation timed out at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Net.java:454) at sun.nio.ch.Net.connect(Net.java:446) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648) at java.nio.channels.SocketChannel.open(SocketChannel.java:189) at org.jinterop.dcom.transport.JIComTransport.attach(JIComTransport.java:98) at rpc.Stub.attach(Stub.java:104) at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:860) ... 12 more
| Summary | Original: Let Jenkins Control this Windows Slave as a windows service does not work after updating to 2.32.2 | New: Let Jenkins Control this Windows agent as a windows service does not work after updating to 2.32.2 |
Just an update downgraded back to 2.7.4 and things are back to normal with slaves being controlled by Jenkins using windows services