[JIRA] (JENKINS-41892) Let Jenkins Control this Windows Slave as a windows service does not work after updating to 2.32.2

151 views
Skip to first unread message

ahmeddanielmuhammad@gmail.com (JIRA)

unread,
Feb 9, 2017, 8:01:02 AM2/9/17
to jenkinsc...@googlegroups.com
ahmed daniel created an issue
 
Jenkins / Bug JENKINS-41892
Let Jenkins Control this Windows Slave as a windows service does not work after updating to 2.32.2
Issue Type: Bug Bug
Assignee: Kohsuke Kawaguchi
Components: windows-slaves-plugin
Created: 2017/Feb/09 1:00 PM
Environment: 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
Labels: slaves, windows, service
Priority: Minor Minor
Reporter: ahmed daniel

Updated Jenkins from 2.7.4 to 2.32.2 and now my slave 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 slave 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 slave 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

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

ahmeddanielmuhammad@gmail.com (JIRA)

unread,
Feb 9, 2017, 12:46:01 PM2/9/17
to jenkinsc...@googlegroups.com
ahmed daniel commented on Bug JENKINS-41892
 
Re: Let Jenkins Control this Windows Slave 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

brian.pham@highfive.com (JIRA)

unread,
Feb 8, 2018, 2:50:03 PM2/8/18
to jenkinsc...@googlegroups.com

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

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages