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

          Jeebitesh Kalantri created issue -
          Jeebitesh Kalantri made changes -
          Component/s New: master-slave [ 15489 ]
          Component/s Original: slave-setup [ 15929 ]

          Same problem here. Anything that we can do on our end? Or is it a bug that needs a new release?

          Patrick Renaud added a comment - Same problem here. Anything that we can do on our end? Or is it a bug that needs a new release?

          It seems that old slave plugin does not work with the Windows 2008 R2 64-bit OS.
          We need ti Identify the Root cause, as I think there are some issues in Windows 2008 like
          1) Some Features (service/functionality) are not activated by default as it was in Previous Releases like Windows 2003 R2
          2) Some Local Security Policy are also not enabled , which are in Windows 2003 R2
          3) Mechanism may also include WinRS/WinRm to communicate . or code may need changes.
          4) Master is not a problem , JNLP Slave also works fine in some cases (as it may need some ports to be enabled TCP/IP)

          I will check it once I compare 2 environment - > windows 2003 R2 64 bit and windows 2008 R2 64 bit
          Will get back with the results what needs to be changed

          Jeebitesh Kalantri added a comment - It seems that old slave plugin does not work with the Windows 2008 R2 64-bit OS. We need ti Identify the Root cause, as I think there are some issues in Windows 2008 like 1) Some Features (service/functionality) are not activated by default as it was in Previous Releases like Windows 2003 R2 2) Some Local Security Policy are also not enabled , which are in Windows 2003 R2 3) Mechanism may also include WinRS/WinRm to communicate . or code may need changes. 4) Master is not a problem , JNLP Slave also works fine in some cases (as it may need some ports to be enabled TCP/IP) I will check it once I compare 2 environment - > windows 2003 R2 64 bit and windows 2008 R2 64 bit Will get back with the results what needs to be changed

          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
          Garen Parham made changes -
          Link New: This issue is related to JENKINS-8957 [ JENKINS-8957 ]
          Garen Parham made changes -
          Link New: This issue is related to JENKINS-7701 [ JENKINS-7701 ]

          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!

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

              Created:
              Updated:
              Resolved: