Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Vault Upgrade 2008 to 2009 causing Content Center problems

25 REPLIES 25
Reply
Message 1 of 26
kennedgy
514 Views, 25 Replies

Vault Upgrade 2008 to 2009 causing Content Center problems

We recently upgraded from Inventor/Vault 2008 to 2009 and have a concern.

When creating a new assembly in 2009 Inventor and inserting Content Center parts
the user is sometimes notified that Content Center files must be checked out.
This happens when local content is out of date, caused when Content used in 2008 is used in 2009.

If the user checks out content center parts, the local components are updated.
My understanding is that it is bad practice to allow all users to Check Out content center files.
If the content is not checked out, it can not be used.

Is this a problem?
25 REPLIES 25
Message 2 of 26
Anonymous
in reply to: kennedgy

were your files migrated before the upgrade?
Message 3 of 26
Anonymous
in reply to: kennedgy

strike that reply, I just noticed you stated local content.

I wonder if having your users delete the old CC parts from their
workstations might fix this issue...

Any ideas anybody?
Message 4 of 26
kennedgy
in reply to: kennedgy

Tried deleting local content and it didn't help.
It appears that Content is created in the Vault whenever a component is used.
The Vault files are being updated when 2008 content is used in 2009.

Did we miss a migration step?

I'm also trying to decipher the Vault content folder structure.
We have multiple folders containing the same content.

For example we have the following folders in Vault for hex nuts...
ANSI B18.2.2(02)
ANSI B18.2.2(03)
ANSI B18.2.2(08)
ANSI B18.2.2(09)
ANSI B18.2.2(10)

Some, but not all, content is repeated.
ANSI B18.2.2 -1_2 - 13(3) is in the (08) folder and
ANSI B18.2.2 -1_2 - 13(2) is in the (09) folder.
Both are 1/2" UNC hex nuts.

Can we eliminate the repetition of identical components?
Message 5 of 26
Anonymous
in reply to: kennedgy

if the local CC files were deleted off the users computer, what should
be happening in different cases is;

1. user checks out an assembly with CC parts out of Vault, which if the
local CC was deleted, Vault should be copying down CC files out of
Vault onto the users computer. This is where migration of current
files in Vault would have taken care of any pre-2009 CC parts in your
Vault.

2. user creates a new assembly and inserts CC parts into it. The CC
parts are now being created from scratch. As long as that is being done
thru Inv 2009, the CC parts will be in version 2009 format.

Content Center parts are created on the users computer from scratch (not
in Vault), and are not put into Vault until the user checks them in.

Deleting all CC files off a users computer (assuming that everything
was checked in first to avoid problems) should take care of this.

As for the multiple files of various hex nuts, all I can think of is
different versions of Inventor over the years possibly created
different paths each time.

I myself would be very hesitant about deleting any CC parts from within
Vault regardless of the repetition due to the fact that anything in
Vault now is tied to or dependent on something else which is also in
Vault.

Try this, on one of the systems that is experiencing this problem,
have the user check in all files they have checked out. Have the user
then go back and delete the *entire* local CC folder, not sure of your
paths so double check first. Then have the user go thru and make sure
any Inventor files are deleted or moved to somewhere outside of the
working folder.

Side note about deleting CC parts, after the above steps are taken, it
might be good to do a complete search of their C:\ drive for any and
all Inventor .ipt files to see if there are some "stray" CC parts
anywhere. Some people may have copied files to other locations or
maybe were practicing questionable modeling practices, you never know!

Then try to check out an assembly with CC parts that you know has given
you problems before and see what happens.

possibilities...

Everybody is on 2009 now right? Nobody is accidentally starting up 2008
are they (assuming you have that installed still)?

Project files OK? During the upgrade process, was your Project file/s
migrated *and* all users got a new copy of the Project file/s?

Throwing out ideas here...
Message 6 of 26
Anonymous
in reply to: kennedgy

On Thu, 22 Jan 2009 18:07:17 +0000
kennedgy <> wrote:

> The
> Vault files are being updated when 2008 content is used in 2009. Did
> we miss a migration step?

Clarification about this. Over the years thru different Inventor
versions, as people create CC parts, they are stored on the users
computer. When a person checks files in, they may or may not be going
back and deleting all files. If they are deleting files after
check-in, they may not be deleting CC parts.

So you may have alot of stray, old versions of CC parts on the users
computer.

Migration usually only takes place on the actual Vault server, not on
users computers.

I really suspect there are some old versions of CC parts on the users
computers (in possibly multiple locations) which could be giving you
grief.
Message 7 of 26
kennedgy
in reply to: kennedgy

Thanks for all the tips, Joe.

I think I've got a handle on where we are at.
Here goes...

I looked a little harder at the "duplicate" content and found that though the file names are the same, the components are different (1/2" hex nut, 1/2" heavy hex nut, 1/2" thick hex nut, etc.)

Creating new, previously unused content works fine.

Our real hang up is that we did not migrate the content in Vault as part of the upgrade.
Now the users have to check out content center (and any other 2008) parts when assembled in order to migrate.
They can be checked right back in with the only change being the migration.

If we have mixed 2008/2009 (and possibly older) files in the Vault can we still migrate easily to 2009?
Other than concerns about the integrity of content center files are there concerns migrating files as used?
I saw a bulletin elsewhere on the Autodesk site and they compared "Implicit" and "Explicit" migration.
Autodesk recommends migrating the files as used (implicit).

http://images.autodesk.com/adsk/files/migrating_autodesk_inventor_data_in_autodesk_vault.pdf
Message 8 of 26
Anonymous
in reply to: kennedgy

ah, yes if the files were not migrated then this might be the issue.

Sorry I don't have any experience in migrating so I do not know if
there will be issues with anything previous to 2008 files.

One way to find out is to backup the Vault, then attempt the
migration. Nothing to loose except for your IT/IS staff loosing some
hair or it turns grey on them!
Message 9 of 26
martinxw
in reply to: kennedgy

Re: point 1:

If local CC was deleted and than user go to Inventor and use check-out from vault for assembly with CC, Inventor shows the message - CC files are missing.

Vault add-in in Inventor is not able copy CC files to local from Vault.

But I don't know why, because Vault has associations between the asssembly and this CC files.
Message 10 of 26
ariesk
in reply to: kennedgy

Just to let you know you're not alone. The same problem overhere. Upgraded Inventor and Vault 2008 to 2009 and CC parts want to check out. Our upgrade may went differently however. All new systems and new Vault server with 'clean' 2009 installs. Exported libraries from the old 2008 to the new 2009 vault server. Imported, migrated, ready! Not!
On the clean (formatted etc.) local sytems, CC files want to be checked out. Even after Checking out the entire CC folder from the vault to a local machine and checking back in, clearing the local CC folder (what shouldn't be a problem in my opinion, as CC parts are re-created), a new check out is wanted.
Our reseller will come in and take look, but if you guys have any ideas, I'll surely try them first....and offcourse if we solve it, we'll let you know.
Message 11 of 26
Anonymous
in reply to: kennedgy

On Fri, 23 Jan 2009 13:53:00 +0000
ariesk <> wrote:

> clearing the local CC
> folder (what shouldn't be a problem in my opinion, as CC parts are
> re-created)

I'm not 100% positive so I could be wrong, but I thought that if
Inventor found an existing CC part already on a users computer it just
used that copy instead of creating it from metadata or what ever it's
called.
Message 12 of 26
Anonymous
in reply to: kennedgy

Some how that doesn't sound right.

I could have sworn if a person who has never worked on an assembly
before which is in Vault and contained CC parts, and that person has
never created the particular CC parts that are within that assembly in
any other assembly, then when that person checks out said assembly with
CC parts from Vault, that Vault should be copying down the CC parts to
that users computer.

If the entire CC folder was deleted, Vault should be recreating the
folder structure as needed on that system when files are checked out.
Message 13 of 26
ariesk
in reply to: kennedgy

That is correct, but not the problem. The issue is that with an empty local CC folder, the newly created CC part (or in effect that 'metadata') differs from the vaulted CC parts which ought to be up to date through the migration process... and all libraries (metadata) are 'updated' through the migration...right? So how come they're different?
Message 14 of 26
Anonymous
in reply to: kennedgy

On Fri, 23 Jan 2009 15:00:36 +0000
ariesk <> wrote:

> That is correct, but not the problem. The issue is that with an empty
> local CC folder, the newly created CC part (or in effect that
> 'metadata') differs from the vaulted CC parts which ought to be up to
> date through the migration process... and all libraries (metadata)
> are 'updated' through the migration...right? So how come they're
> different?

I think I can see the issue you are pointing out.

Libraries are installed with the newest version of Inventor, not
migrated I believe, but I understand how you are stating it. However
you have brought up an instance where it is possible for a newly
created CC part that may not/wont jive with a CC part that has been
migrated in Vault.

TGIF
Message 15 of 26
Anonymous
in reply to: kennedgy

just ran a test on 2009

1. created a simple two CC part assy with a nut and bolt.

2. checked in the assembly to Vault (checking the delete files option
apparently doesn't go thru and delete CC parts, only the .iam file)

3. removed the en-US folder from C:\Vault\Work\Content Center Files
which contains the two CC parts in their respective folders and placed
it on my desktop

4. thru Inventor, File -> Open From Vault and choose my assy. It then
prompted me to check out all files.

The results were, no error msg about missing CC parts, it just copied
down the CC parts from Vault to C:\Vault\Work\Content Center
Files\en-US\ into their respective folders.

When I switch over to Vault in the browser inside Inventor, I see just
the assy is checked out, not the CC parts.

Of coarse I do not have any pre-2009 files on this computer so I have
no way of testing with 2008 CC parts in either the Vault or working
folders.
Message 16 of 26
kennedgy
in reply to: kennedgy

To be sure we are talking about the same things, we did move all our data to the 2009 server.
When I say "migrate", I mean updating the file format of parts and assemblies from version 2008 Inventor to 2009 Inventor (which we did not do).
Migration happens in the background when an individual file (2008 format) is opened in 2009.

Here is what I think is happening...
When using content center, new part files are created in the Vault if that particular part has never been used before.
We have no problem with previously unused components.
When inserting a 2008 format component, Inventor requires the file format to be migrated to 2009.
Migration requires the file to be checked out.
After a user migrates the component to 2009, that user can check the component back in to Vault and use it normally without check out.
We are having problems (check out required) if a users local copy is 2008 and the Vault copy is 2009. Still requires check out.

We are planning to migrate all the Vault content center components with Task Scheduler.
I am thinking we need to go through and purge or update local content on all workstations after this.
Message 17 of 26
Anonymous
in reply to: kennedgy

On Fri, 23 Jan 2009 19:23:44 +0000
kennedgy <> wrote:

> I am thinking we need to go through
> and purge or update local content on all workstations after this.

Good idea. If your users have all files checked into Vault (and they
do not have any models stored on their hard-drive which could contain
CC parts, either in or out of the working folder), you should be able to
just go in and delete the folder called en-US in their Content Center
Files (or what ever name it is) folder.

Doing it the way I described above, you might be able to avoid
migrating the Vault files with Task Scheduler - but you would still have
to check out CC parts on a as needed basis in order to get them up to
2009 versions.

Regardless of which ever direction you want to go, it would be best to
go thru and get all the older versions of CC files off every bodies
computer.
Message 18 of 26
martinxw
in reply to: kennedgy

Hello Joe

I try your test too. I tested it in Inventor Professional 2009.
See attachment.

CC is missing. Vault add-in in Inventor wasn't able to copy CC file from filestore to local hard drive.
Message 19 of 26
Anonymous
in reply to: kennedgy

The only thing I did different was when I was opening from Vault, I did
not specify "Check out all".

I let the next screen which pops up and asks if I wanted to check out
all and choose yes.

I don't have an answer as to why your CC parts were not copied down
from Vault.

Assume this situation, you are the person who created this assembly
with one solid body and 4 CC parts. You've checked in the assembly into
Vault.

Another person on a completely different workstation who has never
created any assembly with those exact same CC parts now checks your
assembly out of Vault. What should happen?

I would suggest doing that sort of test with another co-worker and see
what the results are.

HTH
Message 20 of 26
martinxw
in reply to: kennedgy

I tryed your way - didn't specify "Checked out all".

I let the next screen which pops up and asks if I wanted to check out all and choose yes, too.

And than same dialog asked for CC file was appeared :o(((

Next I checked in on first PC and go to another PC - logged to different user - and in Inventor try open from Vault.

I have got same result as in first case.


I'm interested in what I have different from you.

I'll try it in english version of Inventor. Let we see what happened :o))

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report