Hi Seth,
Aside from the error you get, there is a way to manually repair the
assemblies you mention. The files that you've manually placed in the Vault
need to be resolved to the assemblies, and those assemblies will look to the
local workspace for the children. In Vault Explorer, right click and Get
Entire Folder. You'll get a message about Getting the Entire Vault, click
OK. Verify the location it is retrieving to is correct and click OK again.
These assemblies should now resolve to the manually placed Vault files, and
can be checked back in. This should get you going. The Task Scheduler can
also be used here (use migrations mode) to automate this.
--
Brian Schanen
Product Designer - Data Management
Manufacturing Solutions Division
Autodesk, Inc.
wrote in message news:5193644@discussion.autodesk.com...
I have attached a picture of an error I get when I try to run Autoloader. I
have tried about seven times and Autoloader crashes. This is the most
frequent error I have gotten, but once I received a little circled red X
that said server error (one of the files it was trying to upload) and once
it just went away, it didn't even say bye. This is become a very frustrating
piece of software as it loads 1400 of my 1857 files in this project. So then
when I have to manually place (using Vault E
xplorer) a file into the Vault, I try to open it in Inventor and it has to
resolve every part link because it won't look in the Vault, it trys to look
at my local mapped workspace. This is not fun because I have to open every
part and check it into my workspace before I open the assembly. Luckily my
assemblies so far have been about sixteen parts. I think I want to take my
money out of the Vault and put it underneath my mattress.
Seth Holmes