[JENKINS-4859] Slaves cannot be started using Windows Service on Windows Server 2008 x64

Type: Bug
Resolution: Won't Fix
Priority: Major
Component/s: windows-slaves-plugin
Labels:
None
Environment:
Platform: All, OS: Windows XP

Similar Issues:
Powered by SuggestiMate

Show

Slave OS: Windows Server 2008 x64
(This seems to be valid also for Vista64)

Repro steps:
1. On the Hudson master, create a slave pointing to a machine running Windows
Server 2008 x64 (This seem to be valid also for Vista64)
2. Choose to let Hudson control the slave as a Windows Service
3. Click the "Launch slave" button on the slave page on the Hudson Master

Result: Hudson cannot control the slave. Stack trace below.

Expected: That Hudson can control the slave properly.

N.B. the slave adheres to the info on the following URL
(http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM)

Stack Trace:
============

Connecting to qa-w2k8x64-01

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)
	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(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.jinterop.dcom.common.JIRuntimeException: 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.IJIWinReg$createKey.read(IJIWinReg.java:459)
	at ndr.NdrObject.decode(NdrObject.java:19)
	at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138)
	at rpc.Stub.call(Stub.java:112)
	at org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:291)
	... 10 more

depends on

JENKINS-4929 windows 7 x86_64 slave fails to launch via DCOM

Resolved

is duplicated by

JENKINS-16418 Cannot start Windows Server 2012 slave.

Closed

perostman created issue - 2009-11-16 04:48

Kohsuke Kawaguchi made changes - 2010-01-13 15:04

Description

Original: Slave OS: Windows Server 2008 x64
(This seems to be valid also for Vista64)

Repro steps:
1. On the Hudson master, create a slave pointing to a machine running Windows
Server 2008 x64 (This seem to be valid also for Vista64)
2. Choose to let Hudson control the slave as a Windows Service
3. Click the "Launch slave" button on the slave page on the Hudson Master

Result: Hudson cannot control the slave. Stack trace below.

Expected: That Hudson can control the slave properly.

N.B. the slave adheres to the info on the following URL
(http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM)

Stack Trace:
============

Connecting to qa-w2k8x64-01

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)

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(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Caused by: org.jinterop.dcom.common.JIRuntimeException: 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.IJIWinReg$createKey.read(IJIWinReg.java:459)

at ndr.NdrObject.decode(NdrObject.java:19)

at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138)

at rpc.Stub.call(Stub.java:112)

at org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:291)

... 10 more

New: Slave OS: Windows Server 2008 x64
(This seems to be valid also for Vista64)

Repro steps:
1. On the Hudson master, create a slave pointing to a machine running Windows
Server 2008 x64 (This seem to be valid also for Vista64)
2. Choose to let Hudson control the slave as a Windows Service
3. Click the "Launch slave" button on the slave page on the Hudson Master

Result: Hudson cannot control the slave. Stack trace below.

Expected: That Hudson can control the slave properly.

N.B. the slave adheres to the info on the following URL
(http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM)

Stack Trace:
============

{noformat}
Connecting to qa-w2k8x64-01

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)
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(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jinterop.dcom.common.JIRuntimeException: 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.IJIWinReg$createKey.read(IJIWinReg.java:459)
at ndr.NdrObject.decode(NdrObject.java:19)
at rpc.ConnectionOrientedEndpoint.call(ConnectionOrientedEndpoint.java:138)
at rpc.Stub.call(Stub.java:112)
at org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:291)
... 10 more
{noformat}

Kohsuke Kawaguchi added a comment - 2010-01-13 15:20

Can you describe the set up of your Windows 2008 server a bit more? Is it in a domain? A domain controller itself?

The error is "Access denied" when trying to access the registry from a remote machine. Can you think of anything that might have affected that?

Kohsuke Kawaguchi added a comment - 2010-01-13 15:20 Can you describe the set up of your Windows 2008 server a bit more? Is it in a domain? A domain controller itself? The error is "Access denied" when trying to access the registry from a remote machine. Can you think of anything that might have affected that?

samiph added a comment - 2010-01-13 22:58

We have the same problem. Here's some info about our setup:

Windows Server 2008 R2 Standard x64
Slave server is in domain (subdomain of the master Hudson's domain)
Not a domain controller
User defined in the slave configuration is Administrator of the slave's domain
UAC is disabled (there was another error when it was enabled)
Remote Registry service is on

samiph added a comment - 2010-01-13 22:58 We have the same problem. Here's some info about our setup: Windows Server 2008 R2 Standard x64 Slave server is in domain (subdomain of the master Hudson's domain) Not a domain controller User defined in the slave configuration is Administrator of the slave's domain UAC is disabled (there was another error when it was enabled) Remote Registry service is on

perostman added a comment - 2010-01-14 01:41

Windows Server 2008 R2 Enterprise x64
Slave server is in same domain as the master Hudson, not a domain controller.
UAC disabled.
Remote Registry Service on

Note that I have it working fine on Windows 2008 Server Standard x64

perostman added a comment - 2010-01-14 01:41 Windows Server 2008 R2 Enterprise x64 Slave server is in same domain as the master Hudson, not a domain controller. UAC disabled. Remote Registry Service on Note that I have it working fine on Windows 2008 Server Standard x64

pprochazka added a comment - 2010-02-25 04:16

We have the same problem. Configuration of environment:
Server:

Hudson server running in Tomcat 6.0 on SLES 11 (amd64)
Server is not in domain

Agent:

Windows Server 2008 R2 Standard (x64)
Server is in domain (using company domain controller)
Local account with Administrators privileges
Remote registry running
Firewall disabled

I try connect remotely to Computer Management and Remote Registry. Both operation was successfully.

pprochazka added a comment - 2010-02-25 04:16 We have the same problem. Configuration of environment: Server: Hudson server running in Tomcat 6.0 on SLES 11 (amd64) Server is not in domain Agent: Windows Server 2008 R2 Standard (x64) Server is in domain (using company domain controller) Local account with Administrators privileges Remote registry running Firewall disabled I try connect remotely to Computer Management and Remote Registry. Both operation was successfully.

daav added a comment - 2010-05-10 05:04

Seems to occur also on Windows 7 x64
cf ~~JENKINS-4929~~

daav added a comment - 2010-05-10 05:04 Seems to occur also on Windows 7 x64 cf JENKINS-4929

nuncanada added a comment - 2011-01-26 14:02

I have found out the problem, the Remote Registry user, in my case "LOCAL SERVICE", didn't have read access to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg in the slave.

nuncanada added a comment - 2011-01-26 14:02 I have found out the problem, the Remote Registry user, in my case "LOCAL SERVICE", didn't have read access to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg in the slave.

nuncanada added a comment - 2011-01-26 14:05

This problem happens because of a "strange" permission configuration on the slave side where the user running the Remote Registry service isn't able to read the registry entries which restrict the remote accessible registry paths, more specifically the children of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

nuncanada added a comment - 2011-01-26 14:05 This problem happens because of a "strange" permission configuration on the slave side where the user running the Remote Registry service isn't able to read the registry entries which restrict the remote accessible registry paths, more specifically the children of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

nuncanada made changes - 2011-01-26 14:05

Assignee		New: nuncanada [ nuncanada ]
Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Assignee:: nuncanada

Reporter:: perostman

Votes:: 13 Vote for this issue

Watchers:: 20 Start watching this issue

Created:: 2009-11-16 04:48

Updated:: 2022-11-22 19:14

Resolved:: 2022-11-22 19:14

Jenkins

Details

Description

Attachments

Issue Links

Activity

Collapse comment: Kohsuke Kawaguchi added a comment - 2010-01-13 15:20

Expand comment: Kohsuke Kawaguchi added a comment - 2010-01-13 15:20

Collapse comment: samiph added a comment - 2010-01-13 22:58

Expand comment: samiph added a comment - 2010-01-13 22:58

Collapse comment: perostman added a comment - 2010-01-14 01:41

Expand comment: perostman added a comment - 2010-01-14 01:41

Collapse comment: pprochazka added a comment - 2010-02-25 04:16

Expand comment: pprochazka added a comment - 2010-02-25 04:16

Collapse comment: daav added a comment - 2010-05-10 05:04

Expand comment: daav added a comment - 2010-05-10 05:04

Collapse comment: nuncanada added a comment - 2011-01-26 14:02

Expand comment: nuncanada added a comment - 2011-01-26 14:02

Collapse comment: nuncanada added a comment - 2011-01-26 14:05

Expand comment: nuncanada added a comment - 2011-01-26 14:05

People

Dates