I had an odd error crop up for me just now. A script of mine ran and called on deadlinecommand to find a job ID, but it returned an error for me saying that the repository path was invalid because it didn’t have the bin folder.
Error: Given repository path, "\\192.168.10.132\DeadlineRepository\", is not valid. It does not contain the necessary "bin" folder.
There may be a network issue, or a valid repository has not been installed at this location. If one has not yet setup a repository
it is possible to do so using the repository installer included in the installation files.
What’s odd is that this script ran a couple more times after that without the error, and we’ve been using this repository for a while now without issue. It’s the first time it’s come up at all. I checked and the path does exist, because it actually points to the old repository from before we set up Deadline7 and created a new one (which is an almost identical path but instead it’s “\192.168.10.132\DeadlineRepository7”). I wonder if that might be the source of the problem. All that’s in the old folder is an empty ‘python’ folder.
Potentially useful information. The call was just “deadlinecommand” because I have environment variables set up to refer to the deadline path. Here’s the environment variable path:
C:\Program Files\Thinkbox\Deadline7\bin
Nothing about the script that called deadlinecommand is supposed to alter the environment or directory in any way, so it should still be using the path above.
As you mentioned it was a one time thing, and the issue didn’t exist on subsequent renders, I am thinking it was a momentary network problem when the slave was checking. Can you advise if this is something you are seeing often? Is it a widespread, reproducible issue?
It has reoccurred, out of 7 attempted tries it gave that error 4 times. Nothing else has experienced issues with the server that we’re aware of. And regardless of whether or not it could connect to ‘\192.168.10.132’, DeadlineRepository is the wrong folder, that points to the old defunct repository. DeadlineRepository7 is the current one.
Maybe I’m reading it wrong but it seems like it is actually changing where it’s supposed to look for the repository and that’s what I’m wondering about. How does deadlinecommand find the right repository to use when it’s being called from C:\Program Files? Is it possible that’s somehow having an issue where it’s checking the wrong repository folder half the time?
Can you verify there is no entries for the Repo path in the auto config section of repository options? That’s the only reason other than user action where I can see that being changed.
I figured out what it was now, it was actual an environment variables issue.
The service had a different set to the foreground process. So when the service sent “deadlinecommand” to command prompt it actually went to the old installation location in program files. There is still a version 6 of DeadlineCommand there that’s looking for the repository in the old repository path.
I’m able to fix it by just having the full explicit DeadlineCommand path rather than using that shortcut.
Thanks for the help!