This error is seriously getting old. Autodesk PLEASE FIX THIS

[TYoung_Combi]

Once again, I am here to complain about the error; "The current operation requires data from document.....".

This time, I was trying to render a model for our marketing department to use. Why can't the reason for this error be fixed? This has plagued Inventor for YEARS. For release after release after release. This is getting OLD. We pay good money for our subscriptions to your products. In my case, I have 32 seat licenses that I manage, and my users are so tired of this error.  FIX THIS PLEASE. FIX THIS PLEASE. FIX. THIS. PLEASE.

EDIT TO ADD: 

When this error appears and I do a Vault search for the part in question, Vault will return a blank triangle status icon (The local copy is a historical revision of the leading revision in the Vault) for the offending part. Many times, we are able to get rid of this error by searching in Vault for, and performing yet another "get" on the part and then selecting "Retry" from the error dialogue.

This does NOT always work, however.

[BDCollett]

---

@TYoung_Combi wrote:
We have done all of the above that you have suggested. This error can pop up out of nowhere at any time. It happens a lot when the mouse cursor happens to touch a .ipt or .iam in the model that Inventor decides that we do not have. It can pop up when loading a freshly 'gotten' assembly. It can pop up when using the 'measure' tool. It is seemingly random, but obviously that can not be the case; SOMETHING has to trigger it.

---

What version of Inventor are you currently on?

This article mentions a fix in patches, 2022.4 and 2023.1

"The current operation requires data from document but it cannot be found... " when opening file fro...

If it is still happening with those versions, it really points to a localized issue. Do you have Anti-Virus scanning files?

Something does have to be causing it, unfortunately you are going to have to find out what that is.

You need to dig under and see what processes are being triggered to correspond with the error in Windows.

It is worth using something like "Fiddler" to monitor HTTP traffic. There is an extension created to monitor Vault API

How to use Fiddler to troubleshoot Vault client HTML connectivity issues. | Vault Products 2020 | Au...

GitHub - coolOrangeLabs/vapiTrace: vapiTrace - Fiddler Extension to trace Vault API calls

[johnsonshiue]

Hi! I am shooting in the dark. Try changing the Project option "Using Unique File Names" to No. I suspect you may have duplicated files somewhere in your project, but "Using Unique File Names" is set to Yes. As a result, Inventor/Vault may not try to find the file. This is just a guess.

Many thanks!

[TYoung_Combi]

@johnsonshiue 

Since Autodesk can't seem to replicate the error, and so many other people are also getting the error, I volunteer my company as a testing ground. Can you send someone to our facility to spend some time with me to monitor the issue? This has been happening for far too many releases to ignore.

[johnsonshiue]

Hi! The forum is meant to be for quick tips, educational info sharing, and workarounds. It is not meant to be a replacement for subscription support. Please contact our reseller and Autodesk Product Support.

Many thanks!

[Frederick_Law]

I saw this a few times.

I did notice when it happen, I had an assembly opened using "Historic Version" of some files.

Opening another assembly that use a different Version of those files will cause the "file not found: error.

If you look at Vault tab in IV, you'll see a triangle in those files status.

This could happen a lot if you have a common part in different subassembly through the years.

Vault remember all Versions and Revisions of all parts used in assembly.

An old assembly could use an old version of a part.

Another assembly use a newer version (or rev) of same part.

The error occur when both assemblies are open.

[TYoung_Combi]

@Frederick_Law 

It would seem to me that Autodesk could figure out some way to stop this from happening. It happened to me 4 times today, and every time I had to completely close Inventor and restart it. It really gets old and frustrating.

[Frederick_Law]

AutoDesk would say user should update assemblies to latest parts version.

I don't have different version in same assembly.

I do work on new one and open some old assembly for ref.  That's when it blow up.

See if your is same problem with "Historic Version".