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?

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...

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.

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.

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))

My results are:

Inventor 2009 EN (english):
CC file is copyed to local hard drive. It is fine and correct.

Inventor 2009 CS (czech):
CC file ISN'T copyed to local hard drive. It is fail.

Some Vaults are set up to restrict user access to Content Center files. Do you both allow check out of Content Center part files, or is that limited to admin only?

This does sound like a software glitch.

I also found that if we use "place component" rather than "place from content center" we are able to avoid the bug (allows "get latest version"). This does require that content center files are on the workstation hard drive, and also requires browsing unrecognizable file names rather than the nice graphical interface of content center.

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



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.

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!

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



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.

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



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

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



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.