Slave FAQ

1 Slave FAQ

Can I run the Deadline Slave on an artist's workstation?

It is not recommended to run the Deadline Slave on artist workstations while they are in use, but we encourage running the slave on these workstations when they will not be in use for a fair length of time (overnight, for example).

Is it possible to automatically start the Deadline Slave when the workstation is not in use?

Yes, you can use the Deadline Screen Saver application to do this.

Can I run the Deadline Slave as a service?

Yes. If you're running the Deadline Launcher as a service, then it will run the slave in the background as well.

Is it possible to stop the slave application from the command line?

Yes, launching Deadline Slave from the command line with the argument -s will stop the slave running on the machine:

> DeadlineSlave.exe -s

What does it mean when a slave is stalled, and is this a bad thing?

Slaves become stalled when they don't update their status for a long period of time, and is often an indication that the slave has crashed. A stalled slave isn't necessarily a bad thing, because it's possible the slave just wasn't shutdown properly (it was killed from the Task Manager, for example). In either case, it's a good idea to check the slave machine and restart the slave application if necessary.

The Slave gives a SocketException error message.

This problem occurs because in Microsoft .NET Framework 1.1, a socket cannot be created if your computer has more than 50 network bound protocols. This problem occurs if you have any combination of network adapters and protocols that causes your computer to have more than 50 network bound protocols. A simple workaround is to remove any unused protocol bindings from the problematic machines.

This article describes this problem in detail, and provides a resolution for it.

The Slave does not pick up any jobs and gives an UnauthorizedAccessException error message.

This happens if you run try running the slave as a non Administrator user. If you want do not want to run the slave as an Administrator, follow the steps below to allow access to the Deadline Repository for all users.

On the machine where the Deadline Repository is installed, navigate to the folder where it is installed using Windows Explorer (default installation path is c:\DeadlineRepository).
Right-click on the Deadline Repository folder and select Properties from the menu.
Select the Security tab.

If there is already an Everyone item under Group or user names, you can skip the next two steps.
Click on the Add button.
In the resulting dialog, type Everyone and click OK.

Select Everyone under Group or user names.
Ensure that Modify, Read & Execute, List Folder Contents, Read, and Write are all checked under the Allow column.

Click on the OK button to save the settings.

Now your slaves should be able to read and write to the Repository while logged on as any type of user.

The images above are from Windows XP. The procedure for Windows 2000 is similar to that of Windows XP.