When I try to run the Deadline Launcher Service the computer shows up as offline and disabled. And if I try to use the Remote Control start Slave I get this Failure: cannot accept a connection because Remote Administration has been disabled under the Launcher Settings in the Repository Options.
Obviously I have checked this option to true and it works fine for all other computers that isn’t running in service mode.
Which versions of Deadline and which Windows OS are you using?
Just to clarify, the “offline” status is the status of the Slave application, not the machine. Also, where are you seeing “disabled”? If this is under the Ping column, that’s because the Ping option itself has been disabled. You can enable it under View → Ping Slave Machines. This is disabled be default because it causes the slave list refresh to take longer.
The fact that you’re seeing this is an indication that at least the Launcher application is running. Now the reason why the launcher might be giving you this message is that it can’t connect to the repository properly, so it uses the default of OFF for this setting. A few questions:
- How are you connecting to the repository on this machine? UNC path or mapped drive?
- What user account is the launcher running under. You’ll likely have problems running under the local SYSTEM account, so you should make sure you are using a network domain account.
- If you are using a network domain account, make sure that the account has the necessary permissions to read/write to the repository.
Cheers,
- Ryan
The Deadline version is 4.0.0.39717 and the slaves are running vista 64 business SP1.
- I’m connecting to the repository using UNC.
- I have tried both local SYSTEM account and a network domain account with all the necessary permissions.
I have tried Deadline 3.1 before and I didn’t had any problems with that version.
/Richard
Hi Richard,
We just tested running Deadline 4 as a service on Vista, and the Launcher is running fine and responding to Remote Control commands properly. We should check the launcher log to see if it is printing out anything that may be helpful. On Vista, the logs should be here:
C:\ProgramData\Prime Focus\Deadline\logs
Maybe try restarting the launcher service itself so that it creates a fresh log. Then try sending it a few remote control commands. Next, find the most recent deadlinelauncherservice log and see if it contains any errors or any other information that might explain why it’s not reading in the network settings properly. Feel free to post the log here and we’ll take a look.
Cheers,
- Ryan
Hey,
I was having the exact same issue but only on a few of the computers I was updating and I found a solution. Some would show up in the config window and a select few would not. Here’s the service log from one of those computers.
2010-02-10 03:55:52: BEGIN - TX101-16\deadline
2010-02-10 03:55:52: Perfoming remote admin check
2010-02-10 04:05:42: Perfoming remote admin check
2010-02-10 08:07:43: Perfoming remote admin check
2010-02-10 09:35:04: Perfoming remote admin check
2010-02-10 09:53:56: Perfoming remote admin check
2010-02-10 10:03:56: Perfoming remote admin check
2010-02-10 10:08:48: ::ffff:***.***.*.* has connected
2010-02-10 10:08:48: Launcher Thread - Received command: GetVersion|GetRepository|VerifyRepository|GetLicenseServer|GetRunningAsService|GetLaunchAtStartup|GetLaunchSlaveAtStartup|GetIPAddress|GetMacAddress|GetOSShortName|GetUserName|GetSlaveStatus
2010-02-10 10:08:48: Launcher Thread - Responded with: Failure: cannot accept a connection because Remote Administration has been disabled under the Launcher Settings in the Repository Options
2010-02-10 10:13:56: Perfoming remote admin check
2010-02-10 10:18:37: Shutting down
I have the clients installed as a service using a domain login with admin permissions to run the service and remote admin is turned on.
I’ve removed the ip address but you can see that I was getting the error about remote admin being disabled. I tried starting/stopping the service, uninstalling/reinstalling, and deleting the program data and app data deadline folders but it didn’t work. This was all under my domain account with admin privileges.
It was only when I logged in as a different user, the same user I am using for the service, reinstalled the client did it pick up and work. So login as a different user with admin permissions and install the client and see if that works.
Hope this helps,
chance
Ah, that makes sense. The client configuration file (deadline.ini) is a per-user configuration, so if you configured Deadline for a logged in user, but then switched to a different user for the service, it wouldn’t be using the same configuration.
Thanks for the info! Definitely helpful.
Cheers,
- Ryan