Hi
New to the Deadline world, getting a test farm setup, and trying to get the client installed with the TLS certificates. We have been following the installation tutorials pretty rigidly.
This is the error we get
Tried pointing at the Deadline10Client.pfx file both locally and on the network, also both passwords we were asked to set up during the repository setup.
Any idea where we may be going wrong? Any help appreciated.
Windows x64 setup throughout
Hello!
I think a screenshot didn’t make it into your post. No worries, the installer log alongside the installer error can usually answer most questions. The installer logs will be in your %tmp% directory or\Users\<username>\AppData\Local\Temp. They’re named bitrock_installer_<some process id>.log. Grab the latest and share that and we should be able to figure out what’s up.
Thanks @Justin_B
This is the error from the log. It’s a bit repetitive, so I’ve truncated it
...
Checking if SecretsManagement is enabled
Executing C:\Users\<user>\AppData\Local\Temp/clientinstalltemp/deadlinecommand.exe RunCommandForRepository Direct "\\myserver\DeadlineRepository10;C:\Users\<user>\Downloads\Deadline10Client.pfx" IsSecretsManagementEnabled
Script exit code: 1
Script output:
Error encountered when loading the configured Client Certificate (C:\Users\<user>\Downloads\Deadline10Client.pfx). It is likely either an invalid x.509 certificate, or the wrong passphrase was provided.
Full Error:
The specified network password is not correct.
Script stderr:
Program ended with an error exit code
Error running C:\Users\<user>\AppData\Local\Temp/clientinstalltemp/deadlinecommand.exe RunCommandForRepository Direct "\\myserver\DeadlineRepository10;C:\Users\<user>\Downloads\Deadline10Client.pfx" IsSecretsManagementEnabled: Program ended with an error exit code
I can see that it is complaining about the passphrase, but it’s the one we literally just created on the repository end.
Is there a way to just recreate the certificate with a new passphrase without going through the whole install again? It might have been a miss-type and therefore not what I thought it was… 
Which version of Deadline is this? I’m assuming 10.1.15.2?
There is a way to re-create the certificate, but re-running the repository installer is the simplest way to do it.
But before you try that, try starting the installation, let it fail then quickly (before the Temp directory is cleared out) run:
C:\Users\<user>\AppData\Local\Temp/clientinstalltemp/deadlinecommand.exe RunCommandForRepository Direct "\\myserver\DeadlineRepository10;C:\Users\<user>\Downloads\Deadline10Client.pfx" IsSecretsManagementEnabled
To confirm that the issue is a bad password and not some other issue. You may need to leave the installer open while you run that command if the clientinstalltemp directory is getting cleared away too quickly.
@Justin_B
Thanks for the help.
The short term solution turned out to be unchecking the remote connection box and removing the cert requirements for now. We’re just testing right now, so there’ll be no outside world interaction.
Cheers