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