Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11856

Jenkins Slave fail to start on Windows 2008 R2 64-bit as windows service

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Blocker Blocker
    • windows-slaves-plugin
    • Master : Windows 2008 R2 64 bit
      Slave Launch : Windows 2008 R2 64 bit

      Connecting to WINSERVER2008R2
      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

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

          Dan Slinky added a comment -

          Jeebitesh, any update on this? Just got bitten by this.

          Dan Slinky added a comment - Jeebitesh, any update on this? Just got bitten by this.

          Garen Parham added a comment -

          Garen Parham added a comment - Sounds like it may be https://issues.jenkins-ci.org/browse/JENKINS-6957 Root cause likely https://issues.jenkins-ci.org/browse/JENKINS-8957

          Does anyone have an update on this? I don't think it is related to the Java installation but something to do with windows security. Unfortunately, I don't know that much about WMI security.

          Walter Kacynski added a comment - Does anyone have an update on this? I don't think it is related to the Java installation but something to do with windows security. Unfortunately, I don't know that much about WMI security.

          I also face the same issue with windows 2008 R2 64 bit.

          What other option can be used to workaround this?

          I tried starting using cygwin, but the system is detected as 32 bit which doesn't work for me.
          I can provide some additional data if needed.

          Are there success stories?

          Thanks in advance!

          Dimitar Sakarov added a comment - I also face the same issue with windows 2008 R2 64 bit. What other option can be used to workaround this? I tried starting using cygwin, but the system is detected as 32 bit which doesn't work for me. I can provide some additional data if needed. Are there success stories? Thanks in advance!

          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

          Jeebitesh Kalantri added a comment - 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

          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.

          Denis Blanchette added a comment - 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.

          Linards L added a comment -

          Can you do it in normal way ( no hacking etc. ) in v1.494?

          I finally managed to do that. See comment here: https://issues.jenkins-ci.org/browse/JENKINS-6604

          Linards L added a comment - Can you do it in normal way ( no hacking etc. ) in v1.494? I finally managed to do that. See comment here: https://issues.jenkins-ci.org/browse/JENKINS-6604

          Facing same issue with following configuration:

          Java Version: 1.7.0-25
          Slave : Windows 2008 R2-64Bit

          But the approach ".\Username" is not solving problem in my case.

          In system events found error saying logon failure due to incorrect username or password even though provided correct credentials.

          JNLP agent connected from /10.192.60.191
          <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.22
          This is a Windows slave
          Copied maven-agent.jar
          Copied maven3-agent.jar
          Copied maven3-interceptor.jar
          Copied maven-interceptor.jar
          Copied maven2.1-interceptor.jar
          Copied plexus-classworld.jar
          Copied classworlds.jar
          Slave successfully connected and online
          ERROR: Connection terminated
          java.net.SocketException: Connection reset
          	at java.net.SocketInputStream.read(SocketInputStream.java:185)
          	at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
          	at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
          	at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2265)
          	at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2558)
          	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2568)
          	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314)
          	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
          	at hudson.remoting.Command.readFrom(Command.java:92)
          	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
          	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
          

          Kurri Nagarjuna Reddy added a comment - Facing same issue with following configuration: Java Version: 1.7.0-25 Slave : Windows 2008 R2-64Bit But the approach ".\Username" is not solving problem in my case. In system events found error saying logon failure due to incorrect username or password even though provided correct credentials. JNLP agent connected from /10.192.60.191 <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.22 This is a Windows slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online ERROR: Connection terminated java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:185) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2265) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2558) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2568) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

          Oleg Nenashev added a comment -

          Now this codebase is located within the Windows Slaves Plugin

          Oleg Nenashev added a comment - Now this codebase is located within the Windows Slaves Plugin

          Mark Waite added a comment -

          Won't be fixed. See JENKINS-67604 for the details of the deprecation of agents started by WMI calls using DCOM.

          Mark Waite added a comment - Won't be fixed. See JENKINS-67604 for the details of the deprecation of agents started by WMI calls using DCOM.

            kohsuke Kohsuke Kawaguchi
            jeebitesh Jeebitesh Kalantri
            Votes:
            9 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: