Checking out Library parts

[Anonymous]

We just upgraded to Vault 5, for some reason it is now always asking us to check out library parts - and this is causing major problems when someone else needs to open a library document in there assembly. Is there some setting that we have to adjust to prevent this from happening?
Regards,
Rick

[Anonymous]

Hello Rick,
When you upgraded to Vault 5, did you upgrade to Inventor 11 as well? If so,
consider migrating the CAD files and libraries. You could also uncheck the
Prompt to Save for migration option in Inventor. Are these iParts that are
prompting for Check Out and update? Have the paths changed in the ipj file?
Once you check these out and save, does it keep prompting you? Let us know.

--
Brian Schanen
Product Designer - Data Management
Manufacturing Solutions Division
Autodesk, Inc.
wrote in message news:5171554@discussion.autodesk.com...
We just upgraded to Vault 5, for some reason it is now always asking us to
check out library parts - and this is causing major problems when someone
else needs to open a library document in there assembly. Is there some
setting that we have to adjust to prevent this from happening?
Regards,
Rick

[Anonymous]

Hello Brian,
Yes we also upgraded to Inventor 11. They are part factories that are prompting us. I have a Silly question, how do I "Migrate" the libraries? Is there a batch utility to assist in the process?
Regards,
Rick

[Anonymous]

Okay,
We have migrated the library parts and that seems to have fixed the problem. Thanks.
Rick

[Anonymous]

Hi Rick,
Good to hear! By the way, Inventor's Task Scheduler can be used to migrate
the files.

--
Brian Schanen
Product Designer - Data Management
Manufacturing Solutions Division
Autodesk, Inc.
wrote in message news:5171804@discussion.autodesk.com...
Okay,
We have migrated the library parts and that seems to have fixed the
problem. Thanks.
Rick

[Anonymous]

Brian,
That is what we used, is there a different way?

Now we have an additional problem, when inserting a file from the library in the vault we now get a project path error. So we just insert the file from the local library and it works. do you know why this is?
Rick

[Anonymous]

After you insert the library part using Inventor's Place Component, what
does the Vault Browser show for the file? A Project path error is indicative
of a ipj path error or mapping error in Vault Explorer. Verify the Vault
library folder is mapped properly.

--
Brian Schanen
Product Designer - Data Management
Manufacturing Solutions Division
Autodesk, Inc.
wrote in message news:5171844@discussion.autodesk.com...
Brian,
That is what we used, is there a different way?

Now we have an additional problem, when inserting a file from the library in
the vault we now get a project path error. So we just insert the file from
the local library and it works. do you know why this is?
Rick

[Anonymous]

Brian,
The mapping appears correct, at least it was the way it worked in 10, and we get the following error.
Rick

[Anonymous]

Rick,
This message is a core Inventor Project path error. It is stating that you
are attempting to save the file outside of either the cone of influence, or
a legal declared Library path. Verify all the path settings in the ipj
first, then the Vault browser should appear correctly. A hunch: perhaps the
Content Center path has changed or a library subpath. Watch for misspellings
too! I have seen 'Fastener' change to 'Fasteners' and this can throw an
error. Hope this helps.

--
Brian Schanen
Product Designer - Data Management
Manufacturing Solutions Division
Autodesk, Inc.
wrote in message news:5172010@discussion.autodesk.com...
Brian,
The mapping appears correct, at least it was the way it worked in 10, and we
get the following error.
Rick

[Anonymous]

Brian,
We had our local support person come in yeasterday. We believe this error is because we had duplicate files in the vault. This was left over from legacy import data when we first installed the vault. Apparently in 10 it worked fine, but in 11 it appeared not to work anymore. We created new project files, deleated duplicate file names, migrated the Library and Content center files and updated our server files - most problems have seemed to have been resolved since then. Thanks for your help.
Regards,
Rick