Ever since I moved to 2022, I have been seeing this error but just ignoring it and moving forward. Today it reached a point where I want to try and resolve this. I searched here and found several posts, but no resolution. The most promising post I found was "Moved, Renamed or Deleted", but the solution to add the DYNAMIC_LOAD_APPLETS system variable did not solve this for me.
The only time I get this error is when I open an iam from Vault. I have noticed that it depends on where in my vault browser I select "Open". I know that seems strange, but so it goes. From Vault, if I select "Open" from here, the iam opens without the message.
When I see the error, it is when I am in the "Where Used" or "Uses" tabs. For instance, when in the "Where Used" tab, if I right-click on the iam and select "Open" from here, I will get the error when the iam opens.
Or, If I right-click on the file from the "Uses" tab and select "Open" I get the error.
I can return back to the main window in vault and select "Open" on the same file and it will open with any messages.
Thanks,
Kirk
Solved! Go to Solution.
Solved by ihayesjr. Go to Solution.
@karthur1
Hi Kirk, that is very interesting. Usually that error (in my experience) meant that a Content Center component file had been deleted locally, but it could also mean that it just doesn't know where to look for it. In your examples, that leads me to wonder if using the "Where Used" and "Uses" search results window somehow does not link the files to the project file... which tells Inventor where to look for all referenced parts etc. Since you are able to open it successfully from the main project explorer, which DOES look at the project, well.... it's got me wondering. If I have some time I'll see if I can reproduce this on my laptop with 2024.
@gandhey Is this something that could/should be investigated?
Chris Benner
Industry Community Manager – Design & Manufacturing
If a response answers your question, please use ACCEPT SOLUTION to assist other users later.
Also be generous with Likes! Thank you and enjoy!
The listed file in the error message is an iPart that I did years ago. When the error comes up, it is always usually a member of this ipart family. That leads me to think that there is an issue with the ipart family, but I have rebuilt \saved\migrated all the members of the family.
But then again, if there was something wrong with the family I would expect get the error when I open the iam from the main explorer window as well.
Kirk
@ihayesjr any thoughts?
Chris Benner
Industry Community Manager – Design & Manufacturing
If a response answers your question, please use ACCEPT SOLUTION to assist other users later.
Also be generous with Likes! Thank you and enjoy!
When you select "Open" from the Uses and Where Used tabs, you are telling Vault to open a specific version of the assembly, not the latest, as when you open from the main file list.
Therefore, if you open a specific version and the components it uses may be different from what it expects, Inventor prompts you with this message.
Instead of opening from those tabs, select "Go to Folder" and open the file from the main grid.
Irvin,
Appreciate the response to my issue.
When I select the file in the "Uses" or "Where Used" panel, it automatically selects the "latest". I don't have an opportunity to select a different version other than the "latest".
Kirk
You are "seeing" the latest in the tabs, but it functions off of a specific version. It is different behind the scenes than opening from the main grid.
Irvin,
I found another weird workflow about this. If I open the file from the "Uses" tab, I get a different result depending on whether or not I have an Inventor session already running. Hopefully you can view the .mp4 that I attached below.
Why is this different?
Thanks,
Kirk
At :37 seconds into the video, after you opened the part the first time, Inventor indicated it changed the file and asked you to save it. You clicked No. When you go to open it the second time, the files are already in the workspace so Vault is not going to download it again, but Inventor is not performing the same background operation. Either way, this message is from Inventor.
The assembly was already in the workspace the first time too. I am trying to figure out why Inventor is looking for that \OldVersion file when I open the assembly from Vault with an Inventor session open. It does not look for that file when its opened from Vault without an Inventor session running.
When I open it from Vault with Inventor running, I looked for the \OldVersion\InternalRetainingRing 3000-x206.0007.ipt is not in that folder. So either the assembly is not calling for it or its found it someplace else.
Kirk
I was still having issues with this and I found it annoying not being able to open from the "Uses" and "Where Used" tabs. One thing that I noticed is that the files that were giving me problems had the Work in Progress life state. I was able to solve my issue of Inventor not locating the versions by changing the state of my iparts to "Released". Now when I open from the "Uses" or "Where Used" tabs, I do not see any errors in Inventor.
I really think there is an issue with the "Non-Released Bias" and "Released Bias" tool because it made no difference when I was working thru this. It seems that what I needed was the "Non-Released Bias". Maybe I don't understand what this tool does.
@karthur1
Hi Kirk, I am assuming you've already seen this, but just to cover all bases here is the documentation on bias. I may also look to see if there are any AU classes which cover this in more detail. Stay tuned.
Chris Benner
Industry Community Manager – Design & Manufacturing
If a response answers your question, please use ACCEPT SOLUTION to assist other users later.
Also be generous with Likes! Thank you and enjoy!
The Released\Non-Released Bias button only effects the display of the grid, not how the files are opened from that grid.
Now I just ran across a different file that is in the Released state, but when I open an assembly from the "Where used" I get the error message. It is trying to find an older version of the part as in my original post.
The file D:\Designs\Drawings\Vendor Parts\JIC Fittings\JIC Male O-Ring Straight\JIC-MaleOringStraight\Jic(-8) to Male O-ring (-8), Straight.ipt version 10 is not the latest version. The Released version of this file is version 22
After the assembly is open, it shows "not the expected revision" in the browser.
Even opening my assembly from Vault's Main window gives me the same "not the expected revision" in the Inventor vault browser.
How can I force my assembly to use the latest released revision?
You need to perform a Get first on the assembly to open with the latest versions of all sub-components.
I had already tried doing a "Get" but I still had the "not the expected revision". I found this article that addresses that issue. Basically, I had to check-out, save and check-in the assembly. After that if I open my assembly in the "Where Used" window, it will open without giving me the prompt saying it could not find the files.
Thanks,
Kirk
@karthur1 @ihayesjr
Playing "devil's advocate" here... I wonder of the bottom line on this work flow is: Don't try to open anything from Where Used. Maybe it would be better to find what you are looking for in Where Used, and then use either Go to Folder (Vault) or even Go to Working Folder (local) and open from there... or open from Inventor and just use the information in Where Used to know where that file lives locally?
This might not help with files already in use, but maybe moving forward it could help prevent this. Irvin, does that make sense, or is this bad advice?
Chris Benner
Industry Community Manager – Design & Manufacturing
If a response answers your question, please use ACCEPT SOLUTION to assist other users later.
Also be generous with Likes! Thank you and enjoy!
It is so convenient to open the assemblies from the Uses and Where Used tabs. I will continue to open from there and fix any issues that come up.
When I run across an assembly that gives me the "The current operation requires data from document xxx, but cannot be found...." error, I will make sure that that file is in the "Released" state. For the assembly files that I have tested this on, this seems to resolve that issue.
If after getting the assembly open, the Vault browser shows the "Not expected revision" icon, the assembly will need to be checked-out, saved, check-in to clear that.
Kirk
Can't find what you're looking for? Ask the community or share your knowledge.