[JIRA] Commented: (HUDSON-4929) windows 7 x86_64 slave fails to launch via DCOM

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[JIRA] Commented: (HUDSON-4929) windows 7 x86_64 slave fails to launch via DCOM

Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139370#action_139370 ]

sayres commented on HUDSON-4929:

One point of note is that when I use "user.machinename" it still sometimes throws the error but then manages to connect after 10-15 seconds.  Will take a closer look at the machine to see what else I could have changed to fix the issue.

> windows 7 x86_64 slave fails to launch via DCOM
> -----------------------------------------------
>                 Key: HUDSON-4929
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-4929
>             Project: Hudson
>          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.hudson-ci.org/display/HUDSON/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 contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]