[JIRA] (JENKINS-11856) Jenkins Slave fail to start on Windows 2008 R2 64-bit as windows service

[denisblanche...@gmail.com (JIRA)]

Denis Blanchette commented on JENKINS-11856 Jenkins Slave fail to start on Windows 2008 R2 64-bit as windows service We have the same problem. We are using Jenkins 1.472 running on Windows Server 2008 R2 master and slaves. Connecting to server.example.com 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:220) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(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 I was able to connect using Jeebitesh Kalantri workaround (launch via Java web start). I then reconfigured the slave to launch via the windows service. However, each time the slave is restarted, someone need to start the service manually, even if the service is set to start automatically.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira