Struggling to launch Windows 7 64-bit slave

477 views
Skip to first unread message

David Aldrich

unread,
Jun 11, 2013, 11:49:39 AM6/11/13
to jenkins...@googlegroups.com

Hi

 

We are struggling to launch a Windows 7 64-bit slave.  Our master is on Centos 5 and we have successfully launched Win XP 32-bit slaves and Win XP 64-bit slaves.

 

I have looked at the Jenkins wiki articles about DCOM errors etc.  Currently, the slave reports:

 

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.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:297)

                at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:480)

 

Does anyone have definitive instructions on how to launch a Windows 7 64-bit slave please? 

 

Or should I use a different approach such as JNLP?

 

Best regards

 

David

 

David Aldrich

unread,
Jun 12, 2013, 8:42:28 AM6/12/13
to jenkins...@googlegroups.com

This problem is now fixed.

 

Best regards

 

David

Click here to report this email as spam.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

bearrito

unread,
Jun 12, 2013, 1:19:52 PM6/12/13
to jenkins...@googlegroups.com, david....@emea.nec.com
Can you post your fix in case it helps future users.

David Aldrich

unread,
Jun 13, 2013, 5:10:03 AM6/13/13
to jenkins...@googlegroups.com, bearrito

The fix was:

 

Jenkins requires access to the "WBEM Scripting Locator". The following steps allow that:

  1. Launch 'regedit'
  2. Find (Ctrl+F) the following registry key: "{76A64158-CB41-11D1-8B02-00600806D9B6}" (it's in HKEY_CLASSES_ROOT\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 on local machine: "NT Service\TrustedInstaller")

 

Best regards

 

David

 

Click here to report this email as spam.

Reply all
Reply to author
Forward
0 new messages