Trouble loading Scene over AWS Portal

Deadline
1

Ok licensing seems to be fixed! Thankyou.

But now it’s having trouble loading the scene. Should I be able to see the files in the S3 bucket? Currently I can only see the certs.

2

Hey Alex,

The bucket that the certs are in is different from the one that contains the assets and output. You can find the name of the bucket that holds the assets listed in your Tools > Configure Asset Server Settings under S3 Bucket.

Did you configure Tools > Configure Asset Server > Root Directories with your asset locations?

Are you specifying Mapped Drives in Tools > Configure Asset Server > Root Directories. If so you need to add entries for those Mapped Drives in Tools > Configure Repository Options > Mapped Drives. The reason for this is that the user running the AWS Portal Services uses these entries to map the drives for the service user (which is different than the logged in user).

Restart the AWS Portal Asset Server Service or Daemon after changing Configure Asset Server and/or Mapped Drive Settings.

  • Windows: Located in Windows Services
  • Linux Command: sudo service awsportalassetservershellscript restart

https://docs.thinkboxsoftware.com/products/deadline/10.0/1_User%20Manual/manual/aws-portal-advanced-installation-topics.html#drive-mappings-with-service-accounts-windows

Does the job report indicate that the scene is failing to load? Can you provide a job report? In this situation I would take a look at the Asset Server Controller log which is located on the machine where AWS Portal was installed.

AWS Portal Log Locations:

https://docs.thinkboxsoftware.com/products/deadline/10.0/1_User%20Manual/manual/aws-portal-troubleshooting/aws-portal-log-locations.html#aws-portal-log-locations-ref-label

In this log you will be able to see upload and download entries performed by the Asset Server. Any problems with uploading files should be indicated here.

Here is our troubleshooting doc for this issue:

https://docs.thinkboxsoftware.com/products/deadline/10.0/1_User%20Manual/manual/aws-portal-troubleshooting/job-report-says-it-failed-to-load-scene.html

Regards,

Charles

  • List item
3

Thanks for your amazing support. Turned out that Deadline wasn’t recognising a mapped network drive (which was actually mapped to a location on a local drive).

Is that normal? My data is all on a local file system but I map a drive letter directly to the folder with my work in it to make the path simple, and it trivial to have consistent paths when other machines access remotely.

I tried it by mapping as a network location, and also tried using the “subst” command line tool but neither approach seems to be recognised my deadline.

Thanks!

4

Hey Alex,

My apologies I missed a step here. After adding the mapped drive entry into the Repository Settings Restart the AWS Portal Asset Server Service. This needs to be done for the service user to pickup the new drive mapping.

Let me know if that works.

-Charles

5

Turned out that service couldn’t see the mapped drive due to the method I had created it. Using the registry to create it lower level fixed the problem. Thanks!