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

Windows agents fail to start on version 2.235.5

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I am trying to connect a windows slave (windows 10 pro) to a windows master (windows server 2019) on jenkins and I always see the error below. I have tried everything but I still see the same error.

      Any resolution for this issue?

      ERROR: Message not found for errorCode: 0x80010111
      org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x80010111
      at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:550)
      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:208)
      at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:296)
      at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
      at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
      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: org.jinterop.dcom.common.JIRuntimeException: Message not found for errorCode: 0x80010111
      at org.jinterop.dcom.core.JIRemActivation.read(JIRemActivation.java:191)
      at ndr.NdrObject.decode(NdrObject.java:19)
      at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138)
      at rpc.Stub.call(Stub.java:112)
      at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538)
      ... 11 more

       note: version java installed in server and slave : 8.261 / .net framework installed : 4.8

      thank you

        Attachments

          Activity

          Hide
          mediss mohamed issaoui added a comment -

          i can't use openssh because it always asks for a password when logging in (authentication is by domain user)


          note: I used WMI agent on a slave on windows server 2019 is working fine, but with windows 10 is not until now

          Show
          mediss mohamed issaoui added a comment - i can't use openssh because it always asks for a password when logging in (authentication is by domain user) note: I used WMI agent on a slave on windows server 2019 is working fine, but with windows 10 is not until now
          Hide
          markewaite Mark Waite added a comment -

          WMI Windows build agent plugin 1.7 has been released with a fix for Jenkins 2.249.1 based installations.

          The issue that affected Jenkins 2.249.1 should not be an issue with Jenkns 2.235.5. I don't know what issue might be affecting a Jenkins 2.235.5 or earlier installation.

          Show
          markewaite Mark Waite added a comment - WMI Windows build agent plugin 1.7 has been released with a fix for Jenkins 2.249.1 based installations. The issue that affected Jenkins 2.249.1 should not be an issue with Jenkns 2.235.5. I don't know what issue might be affecting a Jenkins 2.235.5 or earlier installation.
          Hide
          hidminds Daniel Fischer added a comment -

          I get the same error message afer upgrading a win10 jenkins slave to windows 10 version 2004. I am using jenkins LTS 2.249.1 and WMI Windows Agents Plugin v1.7.

          The DCOM error code is documented here: https://docs.microsoft.com/en-us/windows/win32/com/com-error-codes-3

          RPC_E_INVALID_HEADER 0x80010111 which means "OLE received a packet with an invalid header."

           

          It seems that in Windows OS versions >=2004 the COMVERSION needs to be changed from 5.6 to 5.7:

          https://community.tenable.com/s/article/Update-of-COMVERSION-Minor-Version-in-DCOM-Remote-Protocol-Implementation

           

          Microsoft published a compatibility table here: https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-dcom/acc42954-4073-4f05-b850-efd562022077#Appendix_A_5

           

           

           

          Show
          hidminds Daniel Fischer added a comment - I get the same error message afer upgrading a win10 jenkins slave to windows 10 version 2004. I am using jenkins LTS 2.249.1 and WMI Windows Agents Plugin v1.7. The DCOM error code is documented here: https://docs.microsoft.com/en-us/windows/win32/com/com-error-codes-3 RPC_E_INVALID_HEADER 0x80010111 which means "OLE received a packet with an invalid header."   It seems that in Windows OS versions >=2004 the COMVERSION needs to be changed from 5.6 to 5.7 : https://community.tenable.com/s/article/Update-of-COMVERSION-Minor-Version-in-DCOM-Remote-Protocol-Implementation   Microsoft published a compatibility table here: https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-dcom/acc42954-4073-4f05-b850-efd562022077#Appendix_A_5      
          Hide
          mediss mohamed issaoui added a comment - - edited

          Thank you very much guys,
          I changed the launch method, actually I use (Launch agent by connecting it to the master) and works fine.

          Show
          mediss mohamed issaoui added a comment - - edited Thank you very much guys, I changed the launch method, actually I use ( Launch agent by connecting it to the master ) and works fine.
          Hide
          georgelinsdell2 George Linsdell added a comment - - edited

          So there has been no change successful connection behavior with our dev ops manager rolling out the regular jenkins updates as and when they become available, There was a breaking change to support master controlled nodes and there has been no further investigation work. since from the activity on this ticket.

          Is it appropriate that the solution for "you broke it" is to "Change the method of control". And not investigate the scenario that you broke and fix it.
          The "Launch agent by connecting it to the master" is a much less stable mechanism that the master being able to control the node and required additional maintenance. I blanket removed "Launch agent by connecting to the master" as it was not suitable for my use case. May I ask what is required to go about getting this resolved.

          I have 6 jenkins nodes which all have the correct configuration and were working pre-jenkins update.
          I have correct fire wall instruction to permit traffic Infact I documented the entire approach from collated sources in order to allow consistent setup between the nodes Can't comment it as Jira garbles the formatting.

          Can somebody advise how I can provide more information to get this looked into?

          [2021-01-04 14:03:05] [windows-agents] Connecting to principe
          ERROR: Message not found for errorCode: 0x80080005
          org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x80080005
          at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:550)
          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:208)
          at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:294)
          at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
          at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
          at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
          at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
          at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
          at java.base/java.lang.Thread.run(Thread.java:834)
          Caused by: org.jinterop.dcom.common.JIRuntimeException: Message not found for errorCode: 0x80080005
          at org.jinterop.dcom.core.JIRemActivation.read(JIRemActivation.java:191)
          at ndr.NdrObject.decode(NdrObject.java:19)
          at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138)
          at rpc.Stub.call(Stub.java:112)
          at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538)
          ... 11 more

          Show
          georgelinsdell2 George Linsdell added a comment - - edited So there has been no change successful connection behavior with our dev ops manager rolling out the regular jenkins updates as and when they become available, There was a breaking change to support master controlled nodes and there has been no further investigation work. since from the activity on this ticket. Is it appropriate that the solution for "you broke it" is to "Change the method of control". And not investigate the scenario that you broke and fix it. The "Launch agent by connecting it to the master" is a much less stable mechanism that the master being able to control the node and required additional maintenance. I blanket removed "Launch agent by connecting to the master" as it was not suitable for my use case. May I ask what is required to go about getting this resolved. I have 6 jenkins nodes which all have the correct configuration and were working pre-jenkins update. I have correct fire wall instruction to permit traffic Infact I documented the entire approach from collated sources in order to allow consistent setup between the nodes Can't comment it as Jira garbles the formatting. Can somebody advise how I can provide more information to get this looked into? [2021-01-04 14:03:05] [windows-agents] Connecting to principe ERROR: Message not found for errorCode: 0x80080005 org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x80080005 at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:550) 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:208) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: org.jinterop.dcom.common.JIRuntimeException: Message not found for errorCode: 0x80080005 at org.jinterop.dcom.core.JIRemActivation.read(JIRemActivation.java:191) at ndr.NdrObject.decode(NdrObject.java:19) at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138) at rpc.Stub.call(Stub.java:112) at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538) ... 11 more

            People

            Assignee:
            mediss mohamed issaoui
            Reporter:
            mediss mohamed issaoui
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated: