[
https://issues.jenkins-ci.org/browse/JENKINS-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158716#comment-158716
]
Alexis Morelle commented on JENKINS-4929:
-----------------------------------------
There's a workaround less complicated thanks to Florian Vogler from Hudson-ci
wiki.
It can be applied to Microsoft Windows 7 too. :)
"This is caused by the TrustedInstaller concept of windows.
Solution I found so far:
Hudson 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".
Launch 'regedit.exe' as 'Administrator'
Find the following registry key:
'HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}'
Right click and select 'Permissions'
Change owner to administrators group.
Change permissions for administrators group. Grant Full Control.
Change owner back to TrustedInstaller (user is "NT
Service\TrustedInstaller")
Restart Remote Registry Service"
> windows 7 x86_64 slave fails to launch via DCOM
> -----------------------------------------------
>
> Key: JENKINS-4929
> URL: https://issues.jenkins-ci.org/browse/JENKINS-4929
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave
> Affects Versions: current
> Environment: Platform: PC, OS: Windows 7
> Reporter: evilchili
> Priority: Blocker
>
> This may not be a bug as I don't have another windows 7 box to test with, but
> it
> appears as though launching Windows 7 slaves via DCOM fails (this master can
> launch XP slaves via DCOM without incident). The slave has no firewall, the
> security policy for local accounts is set to 'classic', and the user is a
> member
> of the Administrators local group.
> Stack trace follows:
> Connecting to bursar
> 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: Access is denied, please check whether
> the
> [domain-username-password] are correct. Also, if not already done please check
> the GETTING STARTED and FAQ sections in readme.htm. They provide information
> on
> how to correctly configure the Windows machine for DCOM access, so as to avoid
> such exceptions. [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:41)
> at
> hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:107)
> at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:178)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:636)
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
