Not a valid repository error

Hi there guys,

I’m trying to setup a “virtual studio” via a few VMWare machines simulating render nodes, licence servers and asset management servers etc… for testing purposes (only using 2 “free” Deadline licences right now).

The setup is as follows:

HOST MACHINE (the phys. one, Win Vista Business x64): has a repository folder on the F:\ drive shared as “DeadLine_Repository” with full access to “everyone”. I have a Deadline Slave installed here as well.
VMachine01 (render node, WinXP x64): has full access to the repository folder via windows explorer, cmd, everything. I’m logged in as an admin. Deadline Slave installed here as well.
VMachine02 (licence server, WinXP x86): has full access to the VMachine01 shared folders as well as the HOST shared folders. Tested, RW, all fine. No Deadline licences (yet, but these will be stored here), only some other sw licences.

However, the VMachine01 Deadline Monitor or Slave throws me an error saying “Not a valid repository”, see the attached picture. I have no idea why that is. I have full access from this machine to the repository folders Read and Write, no problems at all.

The idea is to have the repository on a separate machine (NAS), the lic server (Win XP x86) will be a separate machine as well, there will be an asset management server (Fedora 9) running probably on a virtual machine on the lic. server with a different IP that’ll have to be able to launch Deadline jobs (WIP), then there will be the render nodes with the very same setup (Win XP x64 probably) and preferrably the workstations (Vista x64 or Win7 x64) will have to be able to run Deadline as well so overnight we can let them render too.

Please, can you tell me what this is? Or why it’s throwing me the error? I can’t continue developing the pipeline without this simple setup up and running first.

Thanks a lot in advance, cheers,

That’s quite odd. We’ve tested Deadline in many virtual environments, and we’ve never run into this specific problem. One thing that I noticed though is that the folder browser window doesn’t have a [+] next to the repository path (see attached picture). Are you able to browse through the repository folders through the folder browser? How about through Windows Explorer? Have you tried using the IP address for duberizer instead of it’s host name?

We’re not doing anything fancy when checking for the repository. We just check if the folder exists and display this error if it doesn’t. I know that non-server editions of Windows operating systems have a remote connection limitation of 10, but if you’re only have a couple of clients connecting to the repository machine, this shouldn’t be a problem. Although, it is possible that remote connections can linger, and maybe the total has reached the limit of 10. This can cause unexpected results, like the client machines no longer being able to see the folder.

On Vista, to check the remote connections, follow these steps:

  1. Open the control panel and select Administrative Tools
  2. Open Computer Management
  3. Select Shared Folders and open Sessions

Cheers,

  • Ryan
    repos_01.png

Hi there rrussell,

sorry for the bother, I have no idea what went wrong, but now I fired up the virtual machines and all of a sudden I can connect to the repository, so it must have been a temporary bug of some sort.

Again, I’m sorry to have bothered, it didn’t work no matter what last time, even though I was able to navigate and manipulate with the repository via explorer in the virtual machine, but I couldn’t connect to it via DeadLine.

Anyways, it’s all up and running, so it’s time for some testing :slight_smile:

Thanks again, I appretiate your time and effort.

  • loocas