topic Re: Sharing file in 14 loses library in Libraries & objects

Sharing file in 14 loses library

Anonymous — Wed, 24 May 2023 08:18:41 GMT

I have been updating my 13 templates and files to AC14. I was very pleased to find that opening a 13 file with the 14 Library loaded automatically converted legacy 13 parts to 14. For instance 'D1 Commercial Door 13' automaticaly was substituted with 'D1 Commercial Door 14' ! I said WOO HOO! that just saved me a bunch of time swapping out parts in my template and legacy files. so I went along my merry way, until I shared this same file. Once the Library was changed from local server to Bim Server (same library, I quadurpel checked, rebuilt and uploaded) all parts reverted to their original 13 state, so I lost all my parts unless I change them all manually, or load multiple Release libraries.

If i take the shared file, and save out to a .pln and reload the 14 library it re-converts them.

works as .pln not as TW file..... AArghh

am I missing something or do I have to bite the bullet and swap all my parts if I want to upgrade a file to 14 but keep only one (basic) library loaded?

Re: Sharing file in 14 loses library

Anonymous — Thu, 29 Jul 2010 20:53:43 GMT

Actually even as a .pln if I change the AC14 Library from linked to BIM server library, I still lose them all, until I switch it back to Linked library.

Re: Sharing file in 14 loses library

Laszlo Nagy — Tue, 03 Aug 2010 16:03:08 GMT

Maybe you should use the AC13 Migration Library that comes with AC14.

Re: Sharing file in 14 loses library

Anonymous — Tue, 03 Aug 2010 17:35:01 GMT

Tried it. Doesn't help.
An Update that points to a server side problem. We are Running two separate BIM Servers for the two studios in our office. the problem I am encountering only happens on one of the two servers. if I share the same file or use the AC14 library from the other server it works fine and I don't lose objects.

I am running down permission issues on the server....

Re: Sharing file in 14 loses library

Anonymous — Tue, 03 Aug 2010 18:36:24 GMT

Looks like we fixed it.

It ended up being permission conflicts on the folder containing the libraries that the problem BIM server was referencing. We fixed the permissions on the folder and re-uploaded the library. No more problem.

whew!