[
https://issues.jenkins-ci.org/browse/JENKINS-11856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163067#comment-163067
]
Jeebitesh Kalantri commented on JENKINS-11856:
----------------------------------------------
Resolution(Work-Around):
1) Configure Slave to use "Launch Slaves via Java Web Start"
2) Go to Slave Machine "Jenkins Dashborad" & go to the Build Extcutor Status
Where this Slave will appaear offline
3) click the Launc Button in Web Page, make sure you login from administrative
Login
4) It will laucnh the Slave
5) Now go and anable Inbound and Outbound For firewalls for all TCP/UDP Ports
like 445, 135, 5355, 5985, RPC Dynamic Ports etc. Just read the Troubleshhoting
Artical posted for Windows Slave on Jenkins Wiki
6) click on File -> Install as windows service
7) Now you can see this Slave online (if you have VM Environments, you can just
clone the machine)
Regards,
Jeebitesh Kalantri
> Jenkins Slave fail to start on Windows 2008 R2 64-bit as windows service
> ------------------------------------------------------------------------
>
> Key: JENKINS-11856
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11856
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave
> Affects Versions: current
> Environment: Master : Windows 2008 R2 64 bit
> Slave Launch : Windows 2008 R2 64 bit
> Reporter: Jeebitesh Kalantri
> Assignee: Kohsuke Kawaguchi
> Priority: Blocker
> Labels: Slave, deployment
>
> Connecting to TOROSVN03
> ERROR: Message not found for errorCode: 0x8001FFFF
> org.jinterop.dcom.common.JIException: Message not found for errorCode:
> 0x8001FFFF at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:546)
> 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:178)
> at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:199) at
> java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at
> java.util.concurrent.FutureTask.run(Unknown Source) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at
> java.lang.Thread.run(Unknown Source)
> Caused by: rpc.BindException: Unable to bind. (unknown) at
> rpc.security.ntlm.NtlmConnectionContext.accept(NtlmConnectionContext.java:137)
> at
> rpc.ConnectionOrientedEndpoint.connect(ConnectionOrientedEndpoint.java:252)
> at rpc.ConnectionOrientedEndpoint.bind(ConnectionOrientedEndpoint.java:217)
> at rpc.ConnectionOrientedEndpoint.rebind(ConnectionOrientedEndpoint.java:153)
> at
> org.jinterop.dcom.transport.JIComEndpoint.rebindEndPoint(JIComEndpoint.java:40)
> at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:529) ... 10 more
--
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
