topic Incomplete file reference information in Vault Forum

Incomplete file reference information

Gabriel_Watson — Mon, 02 May 2022 16:48:19 GMT

Vault 2022, server build 27.0.80.10, client built 27.0.80.0. Inventor 2022.2.

When attempting to move large amounts of Inventor files in Vault, I came across the following warning for about one in every thousand or so:

I believe that proceeding with YES would cause some related assemblies/drawings that consume such files to become unresolved, is that correct?

I could only find an Autodesk article on this type of issue in Google cache, not active anymore:

https://webcache.googleusercontent.com/search?q=cache:AIoa9t6gD4kJ:https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles/Warning-Reference-information-for-the-restricted-child-file-was-not-supplied-or-could-not-be-generated-in-the-listed-parent-files-when-renaming-an-Inventor-file-in-Vault.html+&cd=1&hl=en&ct=clnk&gl=ca

However, the fix's suggestion of using "Update File Reference" did not solve the problem, as the warning re-appeared when attempting to move files again. Is it necessary to open the individual files, save them again in Inventor, and check them back in to fix this (migrate that way if needed)? Would there be any way to search for whichever files have this issue before attempting to move them??

Thanks for any tips/hints in the right direction.

Re: Incomplete file reference information

CGBenner — Mon, 02 May 2022 17:08:49 GMT

@Gabriel_Watson

Hello Gabriel! Do the files involved contain model states?

Re: Incomplete file reference information

Gabriel_Watson — Mon, 02 May 2022 19:24:34 GMT

Hi Chris,
I have picked a couple to double-check now, but nope, only Master MS.

I know it is only a warning, and that the greater risk here is of losing time in fixing relationships broken by pushing the move. Or time lost in opening and updating/saving/checking back in files. However, we should be able to spot these land mines beforehand and get clear instruction on what could be done to prevent them.

I was hoping anyone with experience in dealing with these could shed some more light as well. Workarounds are very welcome. Thanks again.