Hello,
We are trying to send a render from Maya 2022 / 2020 and we are not getting an output of frames. We are getting an error saying “Ouput locations " [Path name]” does not exist.
We have reinstalled both Maya and the Deadline client. Made sure the Deadline submission plugin is installed.
Any ideas?
does the output location exist? is it set relative to the project and is that project set to a network location?
I think Maya defaults to the image being output to the ‘images’ folder within the project. This folder isn’t automatically created
What is the error from the log? How are you setting the output path in Maya and with which renderer?
The output location does exist and it is set to a network location. Both input and output are on UNC network drive paths. We are running through Arnold Renderer.
Couldn’t find any errors in the Maya Log
Does the job submit? is there an error log from Deadline? or a job log that points to anything specifically?
are you able to override the output path in Deadline and see if it writes to that location?
The job submits, can’t find anything in the error log that indicates a problem. Works fine on other machines just this one.
I tried to send it to a different output folder and even on a different machine.
ok, if it is just one machine that narrows it down.
Which OS? are you running as a service? or elevated user? does that user have the correct drive mounted/mapped? can you run the deadline command on that machine outside of deadline and does it render?
We recently ran into an issue of path length too. Could it be that?
this is a good shout, think someone else posted an issue with non-standard châràcters too.
I like how you included a few of your own there. 
Windows 10, using the client, the user does have the correct drive mounts and permissions. I in fact switched to a different user which also has the same problems.
Not sure how to run the deadline command …
@Robert_C_Powell
Is that an output path or both?
Interestingly we have had the problem on both Windows and AWS Linux machines (more rarely). Apparently there is a fix for windows to allow it to use longer path names. In our cases this was for output from a deadline job, but many of our jobs are also using the output of the last job as input as well. If the path is too long on Windows and you don’t have the long path name enabled, both would fail. You can’t even open up the file in windows explorer.
p.s. can you not use deadlinecommand.exe with a info.job and plugin.job file? That’s typically how we fire off our jobs on both platforms.
If you can navigate to the bottom of the path where a file is an yet you cannot open the file, that’s a good sign of the long path problem. Otherwise it’s probably something else.
Here’s a ‘How To’ for the long path fix:
I have never used the deadlinecommand.exe do you have a link for me to study?
Will have a look at the path length bit
Just tried the long windows path thing still no luck
Well deadlinecommand.exe is documented in the Deadline/Thinkbox manual. Let me see here…
Check here under ‘Create Job Submission Files:’
https://docs.thinkboxsoftware.com/products/deadline/10.1/1_User%20Manual/manual/manual-submission.html?highlight=deadlinecommand%20exe
As I said, if you can go to the path in explorer, and open the file at the end of the path, then it’s probably not a long path problem. Good luck though!
So ran the exact same render on another computer and it works fine. So doesn’t seem to be a path issue.
Could be a permissions issue, did both jobs run under the same user? Or maybe the previous machine where it failed doesn’t have the drive mapped correctly?
Tried it with 2 different users on the same machine.
Its bizarre how this computer does not like any of it