[ 
https://issues.jenkins-ci.org/browse/JENKINS-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160147#comment-160147
 ] 

Naga Venkatesh Gowru commented on JENKINS-12820:
------------------------------------------------

      We have solved the issue. To configure Windows 7 PC as Slave in jenkins, 
for the first time it needs to be connected to master through the launch method 
"Launch slave agents via java web start" after that if it is necessary we can 
reconfigure the connection through launch method "Windows slave as  a Windows 
Service".

Step by Step procedure to configure Windows 7 as Slave:
=======================================================

In Master PC:
1.Open jenkins home page in browser, Manage Jenkins->Configure System
2.Set Jenkins URL as "http://Master_PC_name:8080/";
3.Create a new node(Slave node)
4.Configure the launch method as ""Lauch slave agents via java web start". Save 
the configuration

In Slave PC:
1.Open the URL "http://Master_PC_name:8080/ " through a browser in Slave PC.
2.Go to the newly created slave node, Click on launch button which is available 
there
3.It will connect slave to master PC. A pop up window will be visible with a 
message as  "Connected". 

Now a Master Slave connection has established, if slave needs to be connected 
through the launch method "Windows slave as  a Windows Service", then continue 
from the above step 3. In that pop up window click File-> Install as Windows 
Service. Now jenkins service has installed as windows service. Now in Master PC 
reconfigure launch method as "Windows slave as  a Windows Service"  and give 
log in credentials. here after connection will be through windows service 
                
> 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

        

Reply via email to