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

From: bearrito [mailto:[email protected]]
Sent: 12 June 2013 18:20
To: [email protected]
Cc: David Aldrich
Subject: Re: Struggling to launch Windows 7 64-bit slave

Can you post your fix in case it helps future users.

On Tuesday, June 11, 2013 11:49:39 AM UTC-4, David Aldrich wrote:
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



Click 
here<https://www.mailcontrol.com/sr/VpoMfn7N5eHGX2PQPOmvUgMAe56rOQQtpbuEppB1ukjzuYmLhi0r3aODvkFpRyTpHrzgtNI8Mf9ue2rhFpgg0Q==>
 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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to