Many of my slaves can’t connect to the database when they startup (they log automatically). I have to log off and relog each of them and then they can connect…
i use win 7 and all firewall are off. my deadline version is 7.1.0.35 R
Hello,
Can I ask are you running Active Directory? If so, that connection might not be happening fast enough. You can try to set automatic start with delay if you run launcher as a service, but if not I think a customer has a solution that worked for them. Let me know.
I don’t know what active directory is… I’m on windows 7. where can I set a delay?
And No I’m not running the launcher as a service.
It was not doing that prior to deadline 7.
Hello,
I shared some info from another customer on the ticket you made.
Finally here is what I did just in case someone else has the same problem:
In the deadline monitor I selected all slaves, then right click and go to modiy slaves properties.
in idle detection I checked “override Idle Detection settings” and “start slave when machine is idle for” and choose 1 minute.
I also went remotely on each slave to uncheck “stat slave at startup” in the deadline launcher.
Just an update to report that finally it still doesn’t work that way (even if the servers are idle for more than a minute, deadline slaves are not starting) so I will try with windows task scheduler instead for the time being.
Hey Jocelyn, when you get some time could you call us here so we can work on this with you? My direct number is in my signature here.
We’re in Winnipeg, and I’m usually in from 9h00 to 17h00 here.
We’ve done a fair bit of testing on our side to make sure this works, so if you’ve managed to find a bug, we’re interested in fixing that up (I’m also pretty curious what it is 
)
I had this and thought it was just a Windows 10 glitch. My solution though was to use Automatic (Delayed) in the service. If you find a deeper root cause/solution I would like to hear it too.
Hi All,
My problem is now solved!
I just had a team viewer session with Dwight. He found out a workaround. In the deadline repository, settings/dbConnect.xml files, he removed the string for the host name to leave only the ip adress numbers. And all my problematic slaves connected instantly when he saved the change.
example:
this
192.168.1.101
instead of
Popol;192.168.1.101
Indeed we did. Not sure why but the bad ipv6 address being used for the hostname seemed to cause problems.