File in Inventor Vault tree but not in Inventor assy

[bhenderson]

In the 10+ years of using Inventor + Vault I have struck this problem twice. I did not get a resolution to the first instance.

I have an assy file that shows a file in the Inventor Vault tree that is not in the Inventor assy. This file is in Vault and is also shown (where used) in the assy. But the file IS NOT IN THE INVENTOR ASSY! It can't be seen in the model tree or the BOM on the Model Data, Structured or parts Only tabs. It cannot be found by searching in the Inventor model tree search function.

This file was in the Inventor assy at a previous version and was deleted. Somehow there is still a link in Vault that says the file is still being used.

Curiously if I run a Pack-N-Go in Inventor the part is shown in the Files Found list.

If I RMB on the file in Inventor Vault tree and select Find In Window there is no result.

I have deleted the non-used file and opened the assy and dealt with the Resolve issue but can't then check the file back into Vault as there is nothing to resolve.

I have opened the assy file, placed the spurious file, checked it into vault, seen that the file is indeed used in the assy. Then opened the assy, checked it out, deleted the spurious file and checked the assy back into Vault. I can still see that the file is in the assy but it's not!

To any Autodesk database gurus out there, I can supply the Pack-N-Go of the assy if required. In the previous company where I had this exact same problem I even supplied the database for Autodesk to investigate but sadly the issue was never resolved.

@Anonymous 

[cbenner]

@bhenderson 

Just reaching here,... but was this a virtual component by chance?

[bhenderson]

Hi Chris.

No, a regular iam with regular ipt children.

[cbenner]

@bhenderson 

I'm at a loss......

@ihayesjr  any ideas?

[ihayesjr]

Is it possible for me to get the Pack-n-Go of this assembly?

[bhenderson]

I can strip down the assy and email it. Send me a DM with your email address or cloud folder and I will send it.

[Anonymous]

I have this problem more regularly than I'd like to admit.

I typically run in to this issue when I replace one iAssembly factory with a different iAssembly factory, or when I use Copy Design in Vault for assemblies including factories.

I currently have one where I followed an earlier workaround suggestion - I logged out of Vault, deleted the offending file from my local drive, opened the assembly, and resolved the offending ghost file to the actual file I'm using.

...so now I have an iAssembly, with an active row determined by the parent-level iAssembly in which I'm working, and [i]the same iAssembly as a ghost file with no active row selected[/i].

It's frustrating and there seems to as yet be no solution, despite nearly a decade of forum posts on the issue.

[Maxim-CADman77]

I wonder have you tried to perform the official recommendations (https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/Inven...) ?

[Dylan-White-Con-form]

@bhenderson 

Have you had any update to this issue? I'm encountering the same problem. 

[bhenderson]

Gday. No update on this. Occurred a few times since. Just a sporadic unreproducible glitch ☹

[Dylan-White-Con-form]

@bhenderson Thanks for getting back to me. Shame about this issue.

Trying to figure out a workaround without recreating the Asm. 

I think in my case the rouge part was part of the original assembly and a copy design action was performed. There was a hole feature applied at the assembly level and it included this part. I have since tried to delete this feature entirely and recreate but there seems to be some link back to the offending part somehow. 

Not sure where to turn but I shall persist. 

Perhaps a purge function could do the trick? 

Thanks again. 

[^_^clovis^_^]

I'd check the I-property "location" of this assy to verify where it is.

The map in Vault might not be the same as the map on your PC.

[Genicee]

I have ran into this a few times. Most often it is when I have replaced a part (Component Replace) in an iAssembly before removing said part from the iAssembly Table. The key is to delete the column(s) that reference the part in the iAssembly Table before doing a component replace. 

If you don't do it before you can always add the new part to the table then delete it. Then add it back. Or something along those lines. I haven't nailed that down yet.