Child pages
  • Windows agents fail to start via DCOM

Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

The documentation page was moved to the WMI Windows Agents plugin documentation. See the Troubleshooting WMI Windows Agents page for more information

17 Comments

  1. Unknown User (jayanthmca)

    Solution for "hudson slave service on local computer started and then stopped"

    Clear Event Log (control panel> administrator tools>event viewer)

    Now start the service

  2. Unknown User (docwhat)

    Another cause for "Message not found for errorCode: 0x00000005" is due to "TrustedInstaller" and requires editing a registry key permission: http://wiki.hudson-ci.org/display/HUDSON/Windows+slaves+fail+to+start+via+DCOM#comment-thread-5432945

  3. Unknown User (asirvinskas)

    Had Access is denied. [0x00000005] on windows 7 ent, 64 bit.

    Solution was found in http://answers.microsoft.com/en-us/windows/forum/windows_7-security/getting-access-is-denied-when-accessing-windows-7/23369f35-bc45-4147-9c3e-74a47d530757

    Solution is realy easy just a one key in registry:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
    create or modify 32-bit DWORD: LocalAccountTokenFilterPolicy
    set the value to: 1

  4. Unknown User (oliverw)

    I got errorCode 0x800703FA on windows 7 x64 running the slave service under a domain account. The solution was this http://blogs.msdn.com/b/distributedservices/archive/2009/11/06/a-com-server-application-may-stop-working-on-windows-server-2008.aspx

    The LocalAccountTokenFilterPolicy reg key fix and the "TrustedInstaller" registry key permission fix were required too.

  5. Unknown User (derekw)

    I had "Access is denied [0x00000005]" as well, with the slave running on Win-7 64-bit Home Premium.  We just moved our master to an https address, and examining jenkins-slave.err.log showed the following:

    "

    Exception in thread "main" java.io.IOException: Failed to validate a server certificate. If you are using a self-signed certificate, you can use the -noCertificateCheck option to bypass this check. at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:263) at hudson.remoting.Launcher.run(Launcher.java:190) at hudson.remoting.Launcher.main(Launcher.java:166)
    Exception in thread "main" java.io.IOException: Failed to validate a server certificate. If you are using a self-signed certificate, you can use the -noCertificateCheck option to bypass this check.

    at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:263)

    at hudson.remoting.Launcher.run(Launcher.java:190)

    at hudson.remoting.Launcher.main(Launcher.java:166)

    ...
    "
    But of course, simply adding -noCertificateCheck to the jenkins-slave XML arguments tag didn't work.

    An additional step is necessary, outlined here: http://apache.resourcezen.com/jenkins-slave-authentication

    Basically, create a directory called 'lib' within the directory where jenkins-slave.exe resides.  In this 'lib' directory, you need to put the commons-codec-1.6.jar file (or whichever the current version is), as downloaded from: http://commons.apache.org/codec/download_codec.cgi

    Then, in the jenkins-slave.xml file, you'll see an '<arguments>' tag.  Append the following to the end of what's there: -classpath "%BASE%\lib\commons-codec-1.6.jar" -noCertificateCheck

    (In the resourcezen link specified above, it suggests using jnlpCredentials too, but our master does not require this, so I left them out.)

    Now, I had done several other things as suggested on this wiki and within other forums to get this up and working, but inclusion of the common-codecs.jar is what ultimately succeeded.  It's possible that something else I changed helped this to succeed, so I'll detail the one additional step which may be necessary.  Since we're running Win7 Home Premium (not Professional or Ultimate), "Local Security Policy" under "Administrative Tools" is no longer available.  Never fear...regedit is here!

    In the registry key: HKLM\SYSTEM\CurrentControlSet\Control\Lsa , add a 32-bit DWORD with the name ' LmCompatibilityLevel ' and set its value to 1.  Information about this registry key can be found here: http://technet.microsoft.com/en-us/library/cc960646.aspx

  6. Unknown User (vlatombe)

    As already told by other users, here what worked for me (Windows Server 2008 R2, 64bits)

    Jenkins requires full access to WBEM Scripting Locator (HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}). Default for administrators group is just read.Change permissions for administrators group to "Full Control".

    1. Launch 'regedit.exe' as 'Administrator'
    2. Find the following registry key: HKEY_CLASSES_ROOT\CLSID\ {76A64158-CB41-11D1-8B02-00600806D9B6}
    3. Right click and select 'Permissions'
    4. Change owner to administrators group.
    5. Change permissions for administrators group. Grant Full Control.
    6. Change owner back to TrustedInstaller (user is "NT Service\TrustedInstaller")
    7. Restart Remote Registry Service
    8. Install http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5582 on the slave
    9. Make sure java is accessible in the PATH.
  7. Unknown User (mlbright)

    In a completely firewalled environment, opening port 35380 seems to have helped a lot, in addition to the ports mentioned above.

  8. Unknown User (eric_henrard)

    Hello,

    Very nice/usefull error-code page.

    I have another to submit to your powerfull brain ;-)

    when i tried from a solaris to connect a Windows 2008R2 I get this error :

    [0x80020009]- Profile:WMIProfile

    Unknown macro: {domain="MYDOMAIN", username="MYUSER", host="MYSERVER_DNS_ALIAS"}

    Query: "ROOT\CIMV2: select Caption, CSDVersion from Win32_OperatingSystem"

    Caused by: org.jinterop.dcom.impls.automation.JIAutomationException: Exception occurred.  [0x80020009]
            at org.jinterop.dcom.impls.automation.JIDispatchImpl.invoke(JIDispatchImpl.java:333)
            at org.jinterop.dcom.impls.automation.JIDispatchImpl.callMethodA(JIDispatchImpl.java:520)
            at org.jinterop.dcom.impls.automation.JIDispatchImpl.callMethodA(JIDispatchImpl.java:526)
            at org.jinterop.dcom.impls.automation.JIDispatchImpl.callMethodA(JIDispatchImpl.java:477)
            at com.quest.qsi.fason.framework.connections.wmi.WMIConnectionImpl.execute(WMIConnectionImpl.java:193)
            ... 4 more
    Caused by: org.jinterop.dcom.common.JIRuntimeException: Exception occurred.  [0x80020009]
            at org.jinterop.dcom.core.JICallBuilder.readResult(JICallBuilder.java:1079)
            at org.jinterop.dcom.core.JICallBuilder.read(JICallBuilder.java:957)
            at ndr.NdrObject.decode(NdrObject.java:36)
            at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:137)
            at rpc.Stub.call(Stub.java:113)
            at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:901)
            at org.jinterop.dcom.core.JIComServer.call(JIComServer.java:856)
            at org.jinterop.dcom.core.JIComObjectImpl.call(JIComObjectImpl.java:266)
            at org.jinterop.dcom.core.JIComObjectImpl.call(JIComObjectImpl.java:153)
            at org.jinterop.dcom.impls.automation.JIDispatchImpl.invoke(JIDispatchImpl.java:315)
            ... 8 more
    !!!Failed to Connect to WMI, Host:MYSERVER_DNS_ALIAS User:MYDOMAIN\MYUSER!!!

    very strange think, when i get the ip address (on the same server by nslookup command) the connection works :

    ###Succeed connecting to WMI, Host:10.xx.xx.18 User:MYDOMAIN\MYUSER###
    Result:
    Class "Win32_OperatingSystem"{
            Property "Caption": Type "STRING" : Value "[Microsoft Windows Server 2008 R2 Enterprise ]"
            Property "CSDVersion": Type "STRING" : Value "[Service Pack 1]"
    }

    Do you have any idea about this?

    Regards,

    Thanks in advance

    Eric

  9. Unknown User (mateosau)

    I have found that some times .Net 3.5 is not installed on the slave machine. Add this through the Windows features and it may resolve issues relating to java

  10. Unknown User (edsherwin)

    ERROR: Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this.
    org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x00000005 at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:542) 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:206) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
    Caused by: rpc.FaultException: Received fault. (unknown) at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:142) at rpc.Stub.call(Stub.java:112) at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538) ... 10 moreAny help or recommendation on this.

    Here's my setup

    • Jenkins master:linux
    • Jenkins slave: windows
    • Slave Launch Method: Let jenkins control this windows slaves as as windows service.
    • and set the administrator username, password, host and run service as: use administrator account give above

    ERROR: Access is denied. See http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM for more information about how to resolve this.
    org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x00000005
    at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:542)
    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:206)
    at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261)
    at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    Caused by: rpc.FaultException: Received fault. (unknown)
    at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:142)
    at rpc.Stub.call(Stub.java:112)
    at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:538)
    ... 10 more

  11. Unknown User (mikesmithnagrastar)

    Given that it takes a book (above) to describe how to solve the problem

    and that some folks have iterated over the book multiple times and still can't get it to work

    Maybe bring back JNLP slave as a selectable option?

    I had to give up and go psexec route to get some automation up and running using Jenkins 2.

  12. Unknown User (dpyoung)

    We're having an issue connecting a Windows 2008 64 bit server as a windows service on our Jenkins. Our Jenkins installation is 1.625.1 running on a RHEL server. We're able to connect the node via JNLP, but when we try to connect using the windows service it throws the below error. We've gone through the troubleshooting steps provided for this error code along with changed the registry key settings and it still fails. Any ideas on what could be the issue is greatly appreciated?

    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.afterDisconnect(ManagedWindowsServiceLauncher.java:484)
    at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:603)
    at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    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)
    ... 11 more

    1. Unknown User (venkatapathy)

      Please follow this below steps to resolve the issue 

      Windows Server 2012 (64bit)

      To connect to Windows Server 2012, Change Permission for following registry key to Full Control:

      - HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID{72C24DD5-D70A-438B-8A42-98424B88AFB8}

      - HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}

      1. Launch 'regedit' (as Administrator)
      2. Find (Ctrl+F) the following registry key: "{72C24DD5-D70A-438B-8A42-98424B88AFB8}" in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\
      3. Right click and select 'Permissions'
      4. Change owner to administrators group (Advanced...).
      5. Change permissions for administrators group. Grant Full Control.
      6. Change owner back to TrustedInstaller (user is "NT Service\TrustedInstaller" on local machine)
      7. Repeat the steps 1-6 for HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}
      8. Restart Remote Registry Service (Administrative Tools / Services)
  13. Unknown User (dineshbabu)

    Hi,

    I'm getting the following error while launching the slave agent on windows 2012 R2 64 bit machine from Jenkins UI. Can somebody provide the workaround for this issue.

    Connecting to x.y.z.a
    
    ERROR: Message not found for errorCode: 0xC0000001
    org.jinterop.dcom.common.JIException: Message not found for errorCode: 0xC0000001
    	at org.jinterop.winreg.smb.JIWinRegStub.winreg_OpenHKCR(JIWinRegStub.java:121)
    	at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:479)
    	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:206)
    	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:253)
    	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
    	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    	at java.lang.Thread.run(Thread.java:745)
    Caused by: jcifs.smb.SmbException: Failed to connect: 0.0.0.0<00>/x.y.z.a
    jcifs.util.transport.TransportException
    jcifs.smb.SmbException: EOF during NetBIOS session request
    	at jcifs.smb.SmbTransport.ssn139(SmbTransport.java:210)
    	at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:249)
    	at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:319)
    	at jcifs.util.transport.Transport.run(Transport.java:241)
    	at java.lang.Thread.run(Thread.java:745)
    
    	at jcifs.util.transport.Transport.run(Transport.java:258)
    	at java.lang.Thread.run(Thread.java:745)
    
    	at jcifs.smb.SmbTransport.connect(SmbTransport.java:309)
    	at jcifs.smb.SmbTree.treeConnect(SmbTree.java:156)
    	at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
    	at jcifs.smb.SmbFile.connect(SmbFile.java:954)
    	at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
    	at jcifs.smb.SmbFileInputStream.<init>(SmbFileInputStream.java:77)
    	at jcifs.smb.SmbFileInputStream.<init>(SmbFileInputStream.java:66)
    	at jcifs.smb.SmbFile.getInputStream(SmbFile.java:2844)
    	at rpc.ncacn_np.RpcTransport.attach(RpcTransport.java:90)
    	at rpc.Stub.attach(Stub.java:104)
    	at rpc.Stub.call(Stub.java:109)
    	at org.jinterop.winreg.smb.JIWinRegStub.winreg_OpenHKCR(JIWinRegStub.java:119)
    	... 10 more
  14. Unknown User (dineshbabu)

    The above specified issue has been resolved, but it is failing with error "ERROR: The service did not respond. Perhaps it failed to launch?" though the jenkins slave is running fine in windows machine.

     

    The error logs from Jenkins are as follows,

    Connecting to x.y.z.a
    Checking if Java exists
    
    java -version returned 1.8.0.
    
    Copying jenkins-slave.xml
    Copying slave.jar
    
    Starting the service
    
    Waiting for the service to become ready
    
    ERROR: The service did not respond. Perhaps it failed to launch?
  15. Unknown User (gurce)

    I got this error and none of the answers above seemed to cover it:

    org.jinterop.dcom.common.JIException: Message not found for errorCode: 0x00000005
        at org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:297)

     

    In the end I found the answer here:

     

    Basically:

    • Run regedit as admin
    • Visit "HKEY_CLASSES_ROOT\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}" and change your preferred user/group's setting to be "Full Control".
    • I had this error when I tried it though:
    • With a bit more googling here, this can be resolved by changing ownership of the key as follows:
      • Right-click this {76A64...} key and go to "Permissions..."
      • Click the "Advanced" button
      • Go to the "Owner" tab
      • In the Change owner to field, select the user/group you want to own the key and press "Apply" and "OK"
      • Now try get "Full Control" for your user/group and it should work
      • Back on your Jenkins server's slave node, click "Launch agent" and hopefully all fares well now
  16. Unknown User (edgarcb)

    I made each and every fix here and my slaves does not even connect for the first time. can anybody actually confirms that this even works?