Windows letter drives are commonly used as references in the scene files and to store the scene itself. Deadline may throw error while trying to access those paths if it is run by a service user. There is a difference between accessing letter drives for the user account and the service account. Usually two configurations of Deadline/applications can cause issue while using the letter drives as scene/references:
- When Deadline Launcher runs as a service: Worker runs in the service context. Letter drives might be available for the logged in user but not for the Worker because it is started by service user which runs Launcher.
- When you are using AWS Portal Asset Server: Asset server is the component of AWS portal which uploads scene/references from it's root directories. It runs as a service like Worker when Launcher is running as a service. Asset Server's service user will not be able to access the letter drives.
To map letter drives for service users running Deadline applications or Asset Server, Deadline has a feature called "Mapped Drives". You will need to add those letter drives in Deadline so that Deadline will map them for you. Here's how: https://docs.thinkboxsoftware.com/products/deadline/10.2/1_User%20Manual/manual/repository-config.html#mapped-drives
The mapped drives entry in the Deadline Monitor> Tools> Configure Repository Options> Mapped Drives should look below:
Select the correct letter drive from dropdown "Mapped Drive", put in the correct UNC path in "Remote Path", then click on three dots button to make sure that it takes you the correct location. Add authentication if you are required to authenticate when you need to access the letter drive.
After you are done adding the letter drives you will need to restart the Worker for the changes to take effect immediately or wait for around 10 minutes for the changes to propagate.