Content Center Parts and Vault Issue

[geamike]

Hi All,

Forgive me if this has been asked and resolved before (and if so, please link me the solution!) but I wasn't able to find anything related.

Here goes:  We use Inventor 2016 with Vault 2016 Pro.  We're set up to access standard Content Center parts from the Vault server (Application Options/Content Center/Access Options: Autodesk Vault Server).  Most of the libraries we use, I have made as Custom, either Copy from an Inventor standard or from scratch, as an iPart publication to Content Center.  For the most part, things are running smoothly.  We have several users spread out across the country.

We've run into the following scenario:  Let's say I create an assembly, and place Part A in as a Standard Content Center part.  It's already in Vault, so it plops in, no problem.  I do the same for Part B, Part C, and so on.  Each part is from the same family, but just different sizes.  Placement goes smoothly.  However, when I try to save the assembly, for some reason I am being asked if I want to save not only the assembly, but Part A!  The status states that it is not checked out from Vault.  I have done nothing more than simply place it into my assembly, and it is only this one part.

If I go to the ribbon and navigate to Manage/Content Center/Refresh, nothing pops up as needing a refresh.  I look at the Vault Status Icon through Vault Pro, and the part is fine.

If I save the assembly, but not the standard parts, then re-open the assembly, everything is fine.  However, as soon as I do anything like try to constrain one of the affected parts, and then save, we're back to the prompt that tells me the part is not checked out from Vault.

Of course, if I hit "yes" to save the part, it wants to check it out from Vault.  If I do that, and then check it back into Vault, the whole process is repeated.

This is frustrating, and it only affects a couple iterations out of a entire Content Center family.  The only way around it seems to be to close the assembly, then re-open.  Imagine an assembly with hundreds of parts, and a few that are standard content center parts, and you're trying to figure out which to save and which to not save....

Any thoughts?  Is there a setting I'm missing?  Do we have a corrupt library that needs re-publishing?

Thanks for any insight.

[Mark.Lancaster]

Did you just start using Inventor and Vault 2016?  Or were the content center files already in a previous version of Vault?  If so the required save is most likely to migrate the existing content center part version to 2016.   The refresh under Manage/Content Center will not detect that change or migration need.

[geamike]

Sorry, I should have noted that:  All of these files have been migrated to 2016.  I ensure that all standard Content Center parts have been migrated to the most recent version as soon as we switch.  In this case, all files were migrated to 2016 back in June this past year.

It's really odd.  It's as if Inventor (or Vault?) is recognizing that there was a change to that one part, even though nothing has changed at all, other than you placed it for the first time, or you constrained it to something else.  If you close down the assembly and save everything but the individual Content Center parts that Inventor is prompting you to save, and re-open it, then the issue goes away.  Everything is fine.

This happens to me with drawings, as well.  I'll balloon the details, make section views, or turn visibility off of various things, and all of the sudden I'm prompted (at Save) that a few Content Center parts aren't checked out from Vault.

And it is only a few part iterations from the same Content Center family; all other iterations don't have this issue.

This happens to all of our users (12 of us) here in our office, I imagine it's happening to other users in our other offices.

EDIT: Understand that this issue has not appeared at all until this past Monday.  

We're all on Build 210, Release: 2016 SP1-Date: Tue 10/13/15

Also, our Vault is set up so that anyone who is NOT an administrator for Vault is not able to check out any Content Center files.

[Mark.Lancaster]

I'm not assuming so this is the reason why I'm asking...

YOu indicate the files were migrated to 2016..  How was that done?  Inventor Task Scheduler?

[geamike]

Task scheduler was not used when migrating the files over; I did it all manually.  That was back in June, and this issue has just surfaced in the past week.

[geamike]

I'm bumping this up, as the issue stated above is still present.

Has anyone else run into this issue?  

[Ray_Feiler]

This is just a guess but maybe Inventor is updating it's "where used" data.

For what it's worth I see this all the time but we don't use Vault so I simply update the files (no check-in check-out needed).

[geamike]

I don't think that's it.  I say that, because it does not matter if the part you create is "Standard" or "Custom".

The only difference between creating the part as "custom" is that now it updates every time, and no check-out is required.

The only way we're able to work around this, without a constant reminder to "check out" these Content Center files, is to make the parts as "custom".

The real stumper for me is why is it only happening to a few select members of a Content Center family?  I can create standard or custom parts of every size configuration within a given family with no issues.  But there are two or three sizes within a family that are affected, the only difference being size.

I have tried to go in to the Content Center Editor and Suppress the offending line within that family.  I create a completely new line using the data from the offending one, and it still happens.  I have tried re-publishing the iPart file, and the same thing happens.  The only solution that works so far is for me to completely start fresh with a new iPart file and publish as a new Content Center part.

We've also tried to "check out" the Content Center part and check it back in.  The only thing this does is bump the Version up a notch each time, because the next time you have that part in an assembly, it still wants you to check it out!  

Sigh.  Just frustrating, that's all.  No rhyme or reason as to why it does this.  The only thing I can guess at (but no way for me to test) is that something happens where the parameters of the part are messed up somehow, perhaps for that particular instance where a line shoots off the opposite direction of where it's supposed to.  I dunno, I'm just stumped.

[Ray_Feiler]

If and when we go to Vault I'm sure I will be right with you.

[geamike]

Figure I'll bump this up again.  Anyone else having this issue?

It seems across the board, whether the Content Center part has been created as "custom" or "standard".  Not all families are affected, only a few.  And not all iterations within a given family, only a few.  Just seems really odd.

[smilinger]

Do you have some ilogic or VBA code running in the background or in the template? And if so did you create these families with this template? Disable them all and see how it goes.

Are you also using "Build All" command all the time? Please stop it. I believe it will constantly dirty you files.

Try also unload all the third party add-ins installed, and test again.

[Anonymous]

I think this is the same issue I'm having.

My issue is seen in this picture: literally the only thing I've done to this file is open it and check it out. Now when I go to save it, it gives me all of these content center files to not save because not checked out from vault... why do I even have to see them!?!?!

We've had this issue since 2015.

I don't technically think that the files were "migrated" for us because they exist in the 2018 libraries that we downloaded and put on the Autodesk Vault server... right? Or do these files still need to be migrated?

Sigh... 

[Anonymous]

I tested my theory and in my case, the files need to be migrated... I don't understand why, but the parts disappear from the list after checked out and migrated.

[geamike · Accepted solution]

In the past year, this issue seems to have resolved itself.  There was a service patch a while back (don't recall which one, but it was within the past year) that, once applied, seemed to resolve this issue.  We haven't had any problems since.

So, Autodesk must have fixed the bug via the service pack.

Keep your service packs up to date!