Preamble: we’ve just downloaded Deadline 3.1 with the intent of evaluating for use in-house. I am, therefore, a Deadline newbie. And, naturally, I’m having a “first hurdle” issue with my test install.
I’ve installed Deadline Repo and Deadline Client (Win64) onto the machine I want to be my repo server (DUCKULA). I’ve configured the sharepoint on the repo server. I’ve installed Deadline Client (Win64) onto a second slave box (SLAVE). On both boxes the Deadline Config correctly points to the shared directory on the repo server and I see the SLAVE box correctly identified when it’s running Deadline Slave.
When I launch Deadline Monitor on either box I see the Submit and Scripts menu as greyed out. When I go into Super-user mode and select Tools -> Configure Plugins I get the following:
Could not find any plugins that can be configured!! (System.Exception)
I took a look at the share point and the \plugins directory is empty. I removed both Client and Repo from the repo server and completely reinstalled. No joy.
Both boxes are running Windows XP Pro x64 SP1. MS .Net 3.5 and Mono 2.4.2 are installed.
Am I missing something really obvious in the installation process? Is there a specific issue with x64 (aside from usual Windows issues)?
First, maybe try reinstalling the repository. Then, check to see if the plugins folder is empty after the installation is complete. This will help us figure out if the problem is with the installation.
Also, maybe double check the permissions of the repository share. Everyone needs full read/write access, and you may have to configure this in the Security AND the Share settings.
Yes, I was aware that it had been reinstalled already. I need you to re-reinstall the repository (do an uninstall first), and then before you start up any of the Deadline applications, I need you to check if the plugins folder in the installation directory is empty or not (sorry that I didn’t explain this better in my first post). First, check from the local repository path from the machine you installed it on (ie: c:\program files\frantic films\DeadlineRepository\plugins), and then check from the 2nd machine using the UNC path (ie: \your\repository\plugins).
As I had said, we’re trying to figure out if the problem occurred during installation, or at some point after that.
Thanks. Looks like this is sorted (at least for now). We reinstalled to a local folder c:\blahblah then copied everything into the share. Using the tools we changed the repo location to point to the share and it all works as expected.
I think this has been a 70-30 mix of misunderstanding on our part and documentation that isn’t as clear as it might be. It might be wise to point out to people that the default install location presented immediately after the license agreement is not the destination for installation of executable but should in fact be the target of the full repository location:
Changing the dialog box text from Destination Folder to Repository Folder might also work
So far it’s good. Our render manager is liking the feature sets and we’re prepping a good-sized list of questions on config, operation and systems specs. Most of the links are broken in the PDF form of the doc so we may end up asking more daft questions.
Glad to hear it’s working now. Could you perhaps explain what you mean by the following:
Specifically, I’m not sure what you mean by not the destination for installation of executable. We definitely want our documentation to be as clear and straightforward as possible, so if you could explain what you were expecting to be installed to that location (as opposed to the full repo install), that would be helpful.
Also, our documentation does mention what needs to be done when installing to an existing network share (see the second point):
We admit that the PDF version of our documentation is rather primitive, and we only recommend using it if there are times you don’t have access to the internet. If you do have access, we recommend using the online documentation: franticfilms.com/software/su … ntents.php
