Inventor can't open two versions of the same file

[iamerm]

Since upgrading to Inventor 2024, we frequently get error messages like these:

Part XYZ.ipt [or Assembly ABC.iam] v23 is opened in Inventor and loaded into cache.  The file located at [file path]\Part XYZ.ipt is a different file version.  Inventor can't open two versions of the same file (where path and file name are the same) in the same session.  Save your work, and then close and reopen the documents using the file to clear the cache.

Can anyone help identify the reason for these messages?  Currently we are using Inventor 2024.1.1 along with Vault Basic 2024.1 Update, and our workflow is the same as it was prior to the upgrade.

[Frederick_Law]

Vault has newer version.

The new version is opened in IV.

Then you open a iam which use a older version of the other iam which probably is not checked out.

Do you want the iam to update to newer version?

If yes, check it out.

If not, close the other iam so IV can load old version from Vault.

[iamerm]

@Frederick_Law  thank you for your quick reply.  I probably should have posted this in the Vault forums.

I believe I understand your explanation.  However, what I don't understand is why this never happened in all of our previous years of using Inventor with Vault.  Are you aware of what changed?

[Frederick_Law]

Installing Vault 2024 might have reset a few options.

That warning might have been turned off.

I have this warning in 2020 and 2023.

Talk to reseller that install Vault.

[iamerm]

Thanks again @Frederick_Law 

We upgraded from Inventor 2021.  I don't recall any of our users ever seeing this message before, and I'm not really a fan of disabling prompts.  I'll try to look into this further.

[CGBenner]

Tagging in @johnsonshiue Do you have any thoughts on this one?  Would it be best moved to Vault?

[johnsonshiue]

Hi! I believe OP contacted Autodesk Product Support and asked the same question. Our project team confirmed that it was a new warning message to help detect when the Inventor file on disc is newer than the same named file loaded in the memory. This can happen after Inventor loads a file, a newer version of the file is pulled down from the server on local Vault folder.

At this point, the user may use Refresh command (File -> Manage -> Refresh) to reload the file so that the latest version is loaded in the memory.

Many thanks!

[BDCollett]

---

@johnsonshiue wrote:

Hi! I believe OP contacted Autodesk Product Support and asked the same question. Our project team confirmed that it was a new warning message to help detect when the Inventor file on disc is newer than the same named file loaded in the memory. This can happen after Inventor loads a file, a newer version of the file is pulled down from the server on local Vault folder.

At this point, the user may use Refresh command (File -> Manage -> Refresh) to reload the file so that the latest version is loaded in the memory.

Many thanks!

---

Will this happen automatically if the prompt is suppressed?

Do you know why this message was added, seems to be confusing people more than helping currently.

[iamerm]

@johnsonshiuethank you for your reply.

I did not contact Autodesk Product Support with this question.  However, I'm happy that I'm not the only one asking.

As @BDCollett  mentioned, these prompts are creating confusion.  So I have similar questions:

Are these just prompts that can be ignored allowing Inventor/Vault to process files the way we've been accustomed to for years?

Or, has something changed with the file interactions between Inventor & Vault?

I suspect the latter because we are also seeing a huge increase in the number of check-in/check-out prompts (at times where we never previously received such prompts).

[BDCollett]

On testing, I was only able to see this message when I did something wrong on purpose.

Having a file open, then doing a Get/Override of the local file again.

When this message appears, you cannot do anything to open the files, until a Refresh from Vault is done. 
I am fine with this.

Another user however was seeing a different scenario where they were seeing this message without doing the above, and with a fresh get of all files. Editing the sub-assembly and then opening would allow them to open without the message.
I need to investigate more why it is acting like this for them.

[johnsonshiue]

Hi Ben,

The Refresh command has to be called by the user. Inventor does not automatically reload the out-of-sync files.

Many thanks!

[iamerm]

---

@BDCollett wrote:

On testing, I was only able to see this message when I did something wrong on purpose.

Having a file open, then doing a Get/Override of the local file again.

When this message appears, you cannot do anything to open the files, until a Refresh from Vault is done. 
I am fine with this.

Another user however was seeing a different scenario where they were seeing this message without doing the above, and with a fresh get of all files. Editing the sub-assembly and then opening would allow them to open without the message.
I need to investigate more why it is acting like this for them.

---

@BDCollettthanks for your post.  Have you found a solution for this?  Or a repeatable way to trigger the error message?

[iamerm]

@johnsonshiuethanks for your reply.

Forgive me because my frustration level with 2024 is VERY high at the moment.  I just did a Refresh to "correct" this issue & blew away a bunch of my work.

This particular error continues to happen frequently for us since upgrading to 2024.  The problem is that it seems very random - I cannot understand what triggers it.  The only thing I know is that it usually happens when working with parts or sub-assemblies that are part of an open higher level assembly.

Refreshing from Vault eliminates any edits that were made (in other words, you lose your work).  And we don't have time to constantly 'close and reopen the documents... to clear the cache.'  This HAS to be more than just a new warning message because you can't move past it.  There's no choice but to go backwards with a refresh or to close.

Interestingly, I have at least 1 report of this happening while working with a newly created assembly that had not yet been uploaded to the Vault.  Has something changed with Inventor's cache (which I literally never thought about until installing this version)?

Our workflow prior to the 2024 upgrade has not changed.  This has become a HUGE problem.  I can't believe more users aren't losing their minds.

[BDCollett]

---

@iamerm wrote:

---

@BDCollett wrote:

On testing, I was only able to see this message when I did something wrong on purpose.

Having a file open, then doing a Get/Override of the local file again.

When this message appears, you cannot do anything to open the files, until a Refresh from Vault is done. 
I am fine with this.

Another user however was seeing a different scenario where they were seeing this message without doing the above, and with a fresh get of all files. Editing the sub-assembly and then opening would allow them to open without the message.
I need to investigate more why it is acting like this for them.

---

@BDCollettthanks for your post.  Have you found a solution for this?  Or a repeatable way to trigger the error message?

---

I could not get it to happen without doing so in a way I would expect it to happen, which is not a usual way or working with Inventor/Vault.

What you are explaining and the other user I dealt with seems different. I have not followed it up any further. It seems like a very isolated issue and hard to determine why it's happening to you.

[johnsonshiue]

Hi! The only way that I am aware to trigger the warning is that the user attempts to open a file (newer version), while the same file (older version) has been loaded. This can happen when multiple users are working on the same assembly but edit different files. For some reason, user A checks in a newer version of a part, while user B already opens the older version. Basically, users are stepping on each others' toe.

The Refresh command works well when the older version of the file is open but unedited. And a newer version arrives on the disc after the older version has been loaded. The command helps bring in the new change.

If you have multiple users working on the same files, hoping to get Google Doc or Office 360 collaborative behaviors, you will be disappointed. Inventor never supports such workflow. Each file can be checked out and edited by only one user at a  time.

Many thanks!

[iamerm]

Thanks again for the input @BDCollett

Thank you, too, @johnsonshiue   I appreciate the responses.

We have been using Vault/Inventor for many years, and we have a good understanding of how Vault works with multiple users.  This issue is occurring with single users working on a project by themselves.  We have not done anything different from what we've always done.  It's very bizarre.

I wish I could explain better.  It's almost like Inventor gets confused within a single session.

Here's the best way I can describe it:

• AssemblyA.iam consists of Part1.ipt, Part2.ipt, & Part3.ipt (all files checked out from the Vault to a single user).
• Make an edit to Part1.ipt by right-clicking on it within the assembly & selecting Edit.  Complete the edit & return to the assembly.  Save (which saves both the updated AssemblyA.iam & the edited Part1.ipt).
• Afterwards, right-click Part1.ipt & select Open to open it explicitly.  Error is triggered.
  • It's like Part1.ipt is updated at the assembly level, but the old version is somehow still in the cache & Inventor doesn't know what to do.  All of this occurs without any Vault interaction.

If that was confusing, I understand.  I'm certainly confused.

[johnsonshiue]

Hi! Many thanks for the clarification! Then let me ask you a question. Is Model States involved? Are the users creating and editing Model States actively?

When a file is opened in Inventor, it is loaded in the memory (RAM). Inventor only works with the files in the memory, not directly on the disc. The only interaction with the disc is open or save. When the user clicks Save, the file in the memory will be saved back to the disc. There isn't any "temp" file somewhere else during the entire operation.

Model States may add some new variables. When a Model State is consumed (in a drawing or an assembly), a member file (mini file within an ipt/iam) is generated. I am wondering if Inventor gets confused somehow.

If you can find a persistent way to reproduce the behavior, please let us know asap.

Thanks again!

[iamerm]

Sorry for delayed response @johnsonshiue 

We are not using Model States yet.

I really wish I could give you a persistent way to reproduce the behavior, but I cannot.  I was on a pretty good roll for a while, but I just got the error message again.  It seems to be very random.

Since Inventor would not open the part I was trying to edit, I performed an edit on that part from within the assembly.  A few clicks later, though, I was forced to refresh & that removed all my changes.  After the refresh there is no option to undo, so I lost work again.

All I can say for certain is that I'm not performing any extra, manual Vault commands.  I'm also not interacting with files through File Explorer.

May I ask:  are there many others inquiring about this issue?

[johnsonshiue]

Hi! We do have some users in collaborative environment seeing the same behavior. However, it seems to be inline with my explanation so far.

Your case is unique at the moment, because it is single-user, no Model States, and no PDM. I am sorry I cannot explain the behavior. Maybe you want to try clean up %temp% to see if it helps.

Many thanks!

[iamerm]

@johnsonshiue  here is a video demonstrating the issue.  The purpose of the video is to show that the files ARE checked out, CAN be edited & saved from within the assembly, but will NOT open explicitly.