AWS Thinkbox Discussion Forums

Import Doesn't Work

Deprecated Deadline 7 Bug Reports
#1

I tried to import some things from my D6 install using the Import from the monitor. It didn’t bring over my pools or groups.

#2

Are you on beta 1 (7.0.0.25) or beta 2 (7.0.0.26)? If you’re on beta 1, check out this forum thread that addresses an importing issue in beta 1:
viewtopic.php?f=206&t=12134#p53603

If you’re on beta 2, then this could be another bug. Did you try to import anything else besides pools and groups? If so, did any of the other settings make it over? Also, when the import failed, did any error messages appear in the Console panel in the Monitor?

Thanks!
Ryan

#3

I was using the second build–I don’t think it imported anything, specifically pools and groups. I fear that when I installed the new repository and chose new db it wrote over the old table settings? I’m unclear of what did and didn’t happen in that instance.

#4

Did you install the Deadline 7 repository to a new location? If so, then everything from v6 should still be intact because v7 uses a different database structure, and shouldn’t have squashed anything.

Do you still have a Deadline 6 client installed? If you launch it, does all the data still show up?

#5

Hmm–I launched my D6 monitor and all my previous stuff is gone like it got wiped. I installed the repo to the default \deadlineRepository7.

#6

When you installed the Deadline 7 database, did you install to the same location as the original DeadlineDatabase6 folder, or did you install to a new DeadlineDatabase7 folder? If it’s the latter, then I think that explains what you’re seeing here. The problem with the initial installers for beta 1 and 2 is that they just replace the old MongoDB Service with the new one, and since it’s using the same port as the previous service, Deadline 6 ends up connecting to the Deadline 7 database (which of course contains no Deadline 6 data). We are addressing this in the beta 3 installer so that it creates a service name with the Deadline version number in it, and doesn’t remove the original service.

Here’s what you can do:

  1. Open a command prompt and go to the DeadlineDatabase 6 mongodb bin folder (C:\DeadlineDatabase6\mongo\application\bin) and run this (notice I’m using 33333 for the port number):
mongod.exe --logpath "C:\DeadlineDatabase6\mongo\data\logs\log.txt" --quiet --port 33333 --dbpath "C:\DeadlineDatabase6\mongo\data"

  1. Go to the Deadline 6 repository settings folder (C:\DeadlineRepository6\settings) and open dbConnect.xml in a text editor. Set the Port property in there to 33333 (the same as the port that mongo is running with above).

  2. Launch the Deadline 6 monitor again and see if you can see your data again. If you can, you should now be able to import it into Deadline 7.

Cheers,
Ryan

Privacy | Site terms | Cookie preferences