[ https://issues.jenkins-ci.org/browse/JENKINS-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Naga Venkatesh Gowru resolved JENKINS-12820. -------------------------------------------- Resolution: Fixed Found a way to make Windows 7 machine as Slave through Jenkins. Updated the configuration steps in comments section, please find them > Unable to start Jenkins Service in Windows 7 Slave machine > ---------------------------------------------------------- > > Key: JENKINS-12820 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12820 > Project: Jenkins > Issue Type: Bug > Components: master-slave > Affects Versions: current > Environment: Master: Windows XP (or) Windows 7 > Slave: Windows 7 > Jenkins 1.432 > Reporter: Naga Venkatesh Gowru > Priority: Blocker > > Launch Method: control this Windows slave as Windows Service > ============== > When I try to establish Master (XP) and Slave (Windows 7) connection, I saw > the below error > 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: 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.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:297) > at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:480) > at org.jinterop.dcom.core.JIComServer.<init>(JIComServer.java:427) > ........... ... > I browsed the web and found a work around for this, I did the below steps > 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 > > Now the above mentioned error got rectified and connection has established, > but Master is unable to start the Jenkins slave service. > Connecting to XXXXXXXXX > Checking if Java exists > java full version "1.4.2_13-b06" > Copying slave.jar > Starting the service > Jenkins in Master hangs here, After this nothing is being displayed in the > log. -- 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