topic Re: Vault Basic 2025 - can't check-in new file after file rename in vault in Vault Forum

Vault Basic 2025 - can't check-in new file after file rename in vault

JBerns — Thu, 26 Feb 2026 17:12:57 GMT

Community,

I had a part in Vault named WH3855. It was used in two assemblies and drawings.

I renamed the file using Vault. New name is OBS_WH3855.

I created a new WH3855_17-4 part in my workspace.

When I attempt to check-in the new part, Vault reports the local part is out of date and needs to be refreshed. Check-In is not allowed.

I have restarted Inventor, Vault, and my PC - Vault still thinks the local copy requires refreshing.

I checked-out the drawings and assemblies. I replaced the obsolete part with the new part. Vault still does not allow check-in. Insists old part requires refresh.

Other new parts can be checked-in, so I it does not appear to be a folder mapping issue or permission issue.

How can I get this new part in to Vault?

Thank you for your time and attention. I look forward to your feedback.

Regards,
Jerry

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

ihayesjr — Thu, 26 Feb 2026 19:19:11 GMT

In the Vault Browser, right-click on that part and select Go to Vault Folder.

Where does it take you in Vault?

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

JBerns — Thu, 26 Feb 2026 21:37:21 GMT

It took me to the folder where the renamed (OBS_WH3855) file resides.

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

ihayesjr — Thu, 26 Feb 2026 21:40:50 GMT

Have you tried logging out of Vault in Inventor and logging back in?

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

JBerns — Thu, 26 Feb 2026 21:50:20 GMT

Log out and reboots.

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

ihayesjr — Thu, 26 Feb 2026 21:54:00 GMT

In Windows Explorer, did you just rename the original file to WH3855_17-4.ipt?

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

JBerns — Thu, 26 Feb 2026 22:13:26 GMT

No, renamed in Vault from WH3855 to OBS_WH3855.

Get renamed file from Vault into workspace.

Opened, modified and then Saved As the new name, WH3855_17-4.

Deleted local copy of OBS_WH3855.

Opened new file and tried to check-in. Reports out of date and needs to be refreshed.

I may try a few more attempts tomorrow, but if unsuccessful, I will delete renamed and its "where used" references.

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

ihayesjr — Thu, 26 Feb 2026 22:39:14 GMT

Try saving it again as a different name and see if that one can be checked in.

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

JBerns — Fri, 27 Feb 2026 19:21:47 GMT

Irvin,

It failed to check-in.

I am going to just delete the file and its references and start over.

Thanks for the suggestions to resolve this issue. Much appreciated.

Regards,

Jerry

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

Doug_Spivey — Fri, 13 Mar 2026 20:12:32 GMT

Show hidden files, .dwf may be checked out and locked under old name.

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

JBerns — Sat, 14 Mar 2026 01:27:11 GMT

I recall showing normally hidden files in the Vault and removing visualization (DWF) files too.

Still could not check it in.

As stated above, I deleted the problem files and checked in the new files.

Thanks though for the suggestion.

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

River.EngumYTTWH — Tue, 11 Aug 2026 17:35:16 GMT

I'm having this problem as well. Pretty frustrating that this is happening with no apparent cause or solution.

Re: Vault Basic 2025 - can't check-in new file after file rename in vault

River.EngumYTTWH — Tue, 11 Aug 2026 17:48:07 GMT

I got around this by "Save As"-ing the 'new' file as a different file name. It may also help to force the .dwf (visualization) to update of the old version in vault to get the .dwf renamed. I haven't been able to test that yet though.