Scenario:
If we configure Windows 2008 R2 node to Jenkins, it fails to connect to the node.
Solution 1 :
Try connect the node through JNLP, it'll connect.
Solution 2:
If we want to connect through Windows service, please follow the steps.
If we configure Windows 2008 R2 node to Jenkins, it fails to connect to the node.
Solution 1 :
Try connect the node through JNLP, it'll connect.
Solution 2:
If we want to connect through Windows service, please follow the steps.
- If you see the below error,
Access is denied. [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:170)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
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)
- Turned off the firewall (this could be configured correctly to be safer, but I didn't care since its in a firewalled "safe" part of the net)
- Launch 'regedit.exe' as 'Administrator'
- Find the following registry key: 'HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}' refer here
- Right click and select 'Permissions'
- Change owner to administrators group.
- Change permissions for administrators group. Grant Full Control.
- Restart Remote Registry Service
- Restart the Windows machine.
No comments:
Post a Comment