AWS Thinkbox Discussion Forums

Deadline Maya submitter install failure

Hi All,

I am new to Deadline, in the sense of never having installed it on a machine before.
I am using version 10.1.9.2.

My scenario:

  1. I have 3 computers all on the same local network. one acting as a server which is accessible by the other two as its mapped as a network drive with a static IP.

2.I installed the repository on the shared network drive on the server, not using certs etc, as I am in a remote location (no security threats around here, also nothing important being done)

  1. I installed client on my other two machines (nodes)

  2. During installation, it said my repository location is not accessible, because it is on a network, but gave me the option to proceed anyways, so i did.

  3. installation finished, and i launched the monitor. It didnt pick up the repository first time, and i set it again… after which it connected. and every time I started it after that it takes two (2) tries before it successfully connects to the repository.

  4. I use maya 2019, so started install for the submitter (found in the repo)

  5. Keep getting this error: "Could not detect the Deadline Repository Directory because there was an error running deadlinecommand.exe from C:\Program files\Thinkbox\Deadline10\bin.
    this is the correct location of the install on both my nodes, and i got the same error on both nodes.

  6. as a test i installed client on the server, and the submitter installed successfully.

9.I tried the manual route, explained in the documentation, but deadline shelf doesn’t show in maya.

I am not a seasoned computer specialist, so would appreciate help in layman’s terms :wink:

Many thanks!!!

Hello!

The reason you’re getting errors trying to install is because the submitter installer is having trouble connecting back to your Repository (just like the trouble the Monitor is having).

Could you go into C:\ProgramData\Thinkbox\Deadline10\logs (or right click on the Launcher icon and choose ‘Explore Log Folder’) and copy one of those deadlinemonitor log files over? Be sure to open it up to see that it’s one where there are connection issues so I can see if there’s a clue as to what’s going wrong.

I think that I am having the same issue. Just setup the repository and client. The worker connects fine, now I would like to install the Maya plugin. The installer fails with message “There was an error running deadlinecommand.exe” . Can you provide any info on how to correct this?

Same problem here but with cinema4D submitter installer. I think is the same issue…
@Justin_B or @Siemon how did you fix it?

@Patrick_Coan any luck?

Thanks!

M.

The main issue appears to be attempting to use a Mapped Drive as the Repository location.
You have to keep in mind that Mapped Drives are mapped for each user, so it is possible to be logged in as a Windows user that has a drive mapped, and execute an installer that runs under a different user (e.g. Administrator) where the drive is not mapped.

For that reason, it is highly recommend to configure the Direct Connection to a Repository folder using the UNC path of that share, and not a Mapped Drive letter.

When the integrated submitter’s installer runs, it calls the deadlinecommand -GetRepositoryPath command to find out where the integration scripts are located. If the Repository path is on a mapped drive, the installer might not be able to access it due to the above reasons, and throw an error.

Alternatively, you could install the Deadline Client on the Repository machine, and check the “Remote Connection Server” option during the installation. Once you have deployed the RCS with TLS/SSL, you can use the IP address, port 4433, and the Deadline10RemoteConnection.pfx certificate to connect to the Repository via a proxy instead of directly. This will remove the need to deal with any paths, UNC or Mapped, when connecting to the Repository.

When connected to an RCS, any files on the Repository requested by Deadline commands and installers will be seamlessly copied over to a local cache folder on the local machine, and run from there. So even if the Repository machine is totally locked down except for the RCS, your installers would be able to get to the script files needed to install the integrated submitters.

Thanks for this. Will look into this direction and report any progress.

It worked for us, thanks!

M.

Privacy | Site terms | Cookie preferences