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

Windows agents fail to start on version 2.235.5

      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

          [JENKINS-63623] Windows agents fail to start on version 2.235.5

          Mark Waite added a comment -

          You might compare the steps you are taking with the steps described in the Jenkins 2.249.1 upgrade testing blog post.

          • Jenkins controller installed from 32 bit MSI, agent with Java Web Start 8u144
          • Jenkins controller installed from 64 bit MSI, agent with IcedTea-Web
          • Jenkins controller installed from jenkins.war file, agent with IcedTea-Web

          Mark Waite added a comment - You might compare the steps you are taking with the steps described in the Jenkins 2.249.1 upgrade testing blog post . Jenkins controller installed from 32 bit MSI , agent with Java Web Start 8u144 Jenkins controller installed from 64 bit MSI , agent with IcedTea-Web Jenkins controller installed from jenkins.war file , agent with IcedTea-Web

          George Linsdell added a comment - - edited

          bump, Seeing the same response. 
          This method of launching slaves is critical as we require this method for a stable test complete integration.
          I've gone back through the process of configuring as documented in 

          I have had to upgrade my nodes from Windows10 1903 to 2004 to avoid the...
          "[2020-09-16 16:33:29] [windows-agents] Installing the Jenkins agent service
          [2020-09-16 16:33:29] [windows-agents] Copying jenkins-agent.exe
          ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
          Also: java.lang.Throwable: launched here
          at hudson.slaves.SlaveComputer._connect(SlaveComputer.java:283)
          at hudson.model.Computer.connect(Computer.java:435)
          at hudson.slaves.SlaveComputer.doLaunchSlaveAgent(SlaveComputer.java:787)
          at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)"
          Error.

          Upon completing this I have attempted to reapply the steps documented under to ensure windows update changes were did not overwrite previously configured settings. https://github.com/jenkinsci/windows-slaves-plugin/blob/master/docs/troubleshooting.adoc 

          which previous resulted in a 6 working windows nodes of this control method.

          Please can you advise on information that can help you diagnose this problem. This upgrade of jenkins master to LTS has broken out entire UI Testing Capability.

          George Linsdell added a comment - - edited bump, Seeing the same response.  This method of launching slaves is critical as we require this method for a stable test complete integration. I've gone back through the process of configuring as documented in  I have had to upgrade my nodes from Windows10 1903 to 2004 to avoid the... " [2020-09-16 16:33:29] [windows-agents] Installing the Jenkins agent service [2020-09-16 16:33:29] [windows-agents] Copying jenkins-agent.exe ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins Also: java.lang.Throwable: launched here at hudson.slaves.SlaveComputer._connect(SlaveComputer.java:283) at hudson.model.Computer.connect(Computer.java:435) at hudson.slaves.SlaveComputer.doLaunchSlaveAgent(SlaveComputer.java:787) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)" Error. Upon completing this I have attempted to reapply the steps documented under to ensure windows update changes were did not overwrite previously configured settings.  https://github.com/jenkinsci/windows-slaves-plugin/blob/master/docs/troubleshooting.adoc   which previous resulted in a 6 working windows nodes of this control method. Please can you advise on information that can help you diagnose this problem. This upgrade of jenkins master to LTS has broken out entire UI Testing Capability.

          Mark Waite added a comment -

          georgelinsdell2 I'm not able to diagnose the problem. I don't use the WMI agents plugin.

          I was trying to offer suggestions that would help you and other users with your own investigation into the issue. I use Windows inbound agents that are launched from a command prompt and I use Windows agents that connect to the Windows OpenSSH server provided by Microsoft.

          Mark Waite added a comment - georgelinsdell2 I'm not able to diagnose the problem. I don't use the WMI agents plugin. I was trying to offer suggestions that would help you and other users with your own investigation into the issue. I use Windows inbound agents that are launched from a command prompt and I use Windows agents that connect to the Windows OpenSSH server provided by Microsoft.

          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

          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

          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.

          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.

          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

           

           

           

          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      

          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.

          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.

          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

          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

          So no further investigation of progress and the facility to use "Let Jenkins Control This Windows Agent As Windows Service" Can for Version 2.235.5 onwards. Can this be highlighted in the associated plugin? 

          https://plugins.jenkins.io/windows-slaves/

          George Linsdell added a comment - So no further investigation of progress and the facility to use "Let Jenkins Control This Windows Agent As Windows Service" Can for Version 2.235.5 onwards. Can this be highlighted in the associated plugin?  https://plugins.jenkins.io/windows-slaves/

          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.

            mediss mohamed issaoui
            mediss mohamed issaoui
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: