[JIRA] [remoting] (JENKINS-4859) Slaves cannot be started using Windows Service on Windows Server 2008 x64

[scdharma@hotmail.com (JIRA)]

Srinivasa Chary commented on JENKINS-4859

Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64 After doing all this, even if you get the error Access denied. Open the command prompt as administrator. C:\>cd jenkins C:\Jenkins>jenkins-slave.exe install C:\Jenkins> Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-4859

Slaves cannot be started using Windows Service on Windows Server 2008 x64

Change By: Daniel Beck Component/s: windows-slaves-plugin Component/s: remoting

Add Comment

[edsherwin.nonog@gmail.com (JIRA)]

Ed Sherwin Nonog commented on JENKINS-4859

Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64 Here's the error on my setup. Thanks Jenkins Master installed on Ubuntu 14.04 Jenkins Slave installed on Windows 7 32 bit Windows Slave Setup Launch Method: Let jenkins control this windows slave as a windows service Administrator username Password Host: IP Adress *Run Service as: Use Administrator account given above 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

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

[me@rustyx.org (JIRA)]

rustyx x commented on JENKINS-4859

Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64

The WBEM Scripting Locator is since 2012 only accessible by the TrustedInstaller service. An Administrator can't access it. So running Jenkins with elevated permissions is not going to help. I don't see how the DCOM-based approach can work out-of-the-box without resorting to above mentioned hacks.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[me@rustyx.org (JIRA)]

rustyx x edited a comment on JENKINS-4859

Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64

The *WBEM Scripting Locator* is since 2012 only accessible by the *TrustedInstaller* service. An Administrator can't access it. So running Jenkins with elevated permissions is not going to help. I don't see how the DCOM-based approach can work out-of-the-box without resorting to above mentioned [hacks| https://issues.jenkins-ci.org/browse/JENKINS-4859?focusedCommentId=162687&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel #comment- 158715 162687 ].

Add Comment

[me@rustyx.org (JIRA)]

rustyx x edited a comment on JENKINS-4859

Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64

The *WBEM Scripting Locator* is since 2012 only accessible by the *TrustedInstaller* service. An Administrator can't access it. So running Jenkins with elevated permissions is not going to help. I don't see how the DCOM-based approach can work out-of-the-box without resorting to above mentioned [hacks|https://issues.jenkins-ci.org/browse/JENKINS-4859?focusedCommentId= 162687 158715 &page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment- 162687 158715 ].

Add Comment

[paul.hendley@omron.com (JIRA)]

paul hendley commented on JENKINS-4859

Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64

Encountering same thing.  no upvotes so adding support of others comments.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-4859

Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64

paul hendley with Windows Server 2019 and with the most recent Windows 10 service packs Microsoft now provides the Microsoft OpenSSH Server. If you're using new enough operating systems, it is much simpler to manage the Windows agents with ssh than to fight with the DCOM approach used by the windows slaves plugin. Refer to the windows section of the ssh-slaves plugin for more information.

Add Comment