Windows Cloud Slave can not be provisioned in JOC using DCOM

Issue

I am getting the stacktrace below after using DCOM as shared cloud in a VMWare Virtual Machine (“Windows Build Pool”) in order to provision slaves.

From the Enterprise Master slave.log
Connecting to XX.XX.XX.XX 
Failed to connect to port 135 of XX.XX.XX.XX. Is Windows firewall blocking this port? Or did you disable DCOM service?

Environment

CloudBees Jenkins Operations Center 

Resolution

You can try the following the suggestions from the Jenkins wiki page about the 0x8001ffff error code.

When using DCOM is really difficult to diagnosis the main root cause of failure. The generic error code it returns and the lack for any diagnostic log make it hard to setup.

JNLP slave is a far better option. Installed as a windows service, it will automatically reconnect any time the Windows server is up-and-running. Other possible option is to setup cygwin and openssh on your Windows node so Jenkins can manage it as a ssh slave, just like it does for Unix slaves.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.