topic Re: This error is seriously getting old. Autodesk PLEASE FIX THIS in Inventor Forum

This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Wed, 05 Jan 2022 12:03:49 GMT

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.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

CGBenner — Tue, 04 Jan 2022 15:47:24 GMT

@TYoung_Combi

Please don't hate me for asking this, but IS the file where it says it should be?

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Tue, 04 Jan 2022 15:52:44 GMT

@CGBenner Yes sir, it is. We have exhausted every possible means to make this error stop happening, but release after release after release after release it persists. I can't believe that it can not be fixed.

No hate, by the way; not my style! Although this particular issue is really starting to grind me down.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

CGBenner — Tue, 04 Jan 2022 15:55:37 GMT

@TYoung_Combi

Just my feeble attempt at humor to defuse the situation. 😂 But thank you for answering the obvious question.... just needed to get that out of the way.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Tue, 04 Jan 2022 16:03:53 GMT

@CGBenner 😂😂 Laughter is most certainly the best medicine! I always appreciate a light-hearted reply. 😎

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

CGBenner — Tue, 04 Jan 2022 16:17:01 GMT

@TYoung_Combi

Have you noticed any repeatable patterns in the parts where you see this problem? For example, are they derived parts, contain any custom data such as threads or appearances etc...? Anything common at all between them? (yeah... I'm really reaching here).

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Tue, 04 Jan 2022 16:31:11 GMT

@CGBenner This seems to happen with any given part at any given time, whenever Inventor feels like causing heartache. I do appreciate you trying to nail down SOME sort of common characteristic, but I'll be darned if I can find a pattern. I will start having my users start documenting which parts this is happening with and we'll try to create a database.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

CGBenner — Tue, 04 Jan 2022 16:34:57 GMT

@TYoung_Combi

That could actually help. I'm not the product expert (in this case), But I know many of them and the more information we can give them to solve this... the better. I do remember seeing this a few times back when I was designing, but I can't remember if I saw any patterns either.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Tue, 04 Jan 2022 16:43:08 GMT

@CGBenner I really appreciate the offer of your help. This has been the most positive experience of all of my posts about this. Yes; I have posted this same request at least 4 times now.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

tomasz.sztejka — Wed, 05 Jan 2022 10:15:43 GMT

It may be totally irrelevant, but from my observation Inventor often displays non-informative or misleading error messages when it can't access file for writing because there is a "read only" attribute set or part is at a path it thinks it can't write to (ie. "library path" in project).

I have seen "Your file is not checked out from Vault" on systems which have never seen a Vault when file attribute was incorrect.

Since You are saying that file is there then maybe this is the case?

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

CGBenner — Wed, 05 Jan 2022 11:40:17 GMT

@TYoung_Combi

One instance where I remember seeing this error was on parts that used a custom appearance with a bitmap texture. The bitmap was located outside of the Design Data folders and, in fact, outside of the active project. Even after removing the appearance from the part it still seemed to hold onto it and look for it. This was why I asked if there might be a similar pattern here. Otherwise, I’m scratching my head on this one…..

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Wed, 05 Jan 2022 12:01:44 GMT

@tomasz.sztejka

That's a valid thought; the same thing crossed my mind so I have checked that and it is not the culprit.

I am going to add an amend to my OP stating that when this error comes up 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.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Wed, 05 Jan 2022 12:57:04 GMT

@CGBenner

re: looking for patterns

I understand why you are asking me about patterns or other similarities. I have sent out a department-wide email, asking my users to document each .ipt file which appears when they get this issue. Hopefully they will fill out the spreadsheet as requested so that I can try to put together some commonalities.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

karthur1 — Fri, 07 Jan 2022 16:21:49 GMT

@TYoung_Combi wrote:

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.

...

...

There are a few times I have seen this, but it is normally when working in an assembly that is using Level of Detail. One reason that we try to avoid LOD's unless absolutely necessary. Inventor would sometimes get crossed up and it can't locate the files.... even though you know for a fact that they are right there.

Do you see this on assemblies that are NOT using LOD? I don't and could not stand for it if I did. I have numerous other users here and I can assure you that if they were having that error, I would get a call.

Kirk

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Mon, 10 Jan 2022 19:11:12 GMT

@karthur1 I am honestly not certain, as nearly all of our subassemblies have LODs, thanks to previous CAD Admins. I have been trying to do away with them and I hope that when we upgrade to 2022 next month and the problem DOES stem from LODs, that the removal of them will resolve the issue.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

scott_ainsworth — Wed, 12 Jan 2022 21:13:47 GMT

I don't know the cause of the problem. In my experience I think it involves a corruption or error in the .v files that vault creates. I think they are crib notes on vault status and where used. If you set your windows explorer so you see hidden and system files you will see a folder _V at in each vaulted folder. When inventor and vault seem to be stumbling all over each other, I find that deleting the _V folders for the relevant files clears things up. Vault will happily recreate the folders and files but without the errors and confusion, at least for a while.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

bradeneuropeArthur — Wed, 12 Jan 2022 23:12:26 GMT

Are some of your missing you files stored locally or on a server?

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Thu, 13 Jan 2022 12:38:42 GMT

@scott_ainsworth

I will have to give that a try. We simply restart Inventor and the problem goes away, at least for a short period.

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

TYoung_Combi — Thu, 13 Jan 2022 12:40:53 GMT

@bradeneuropeArthur

We have Vault set up so that when a 'get' is performed, all parent and child files are downloaded from Vault to each individual machine's "Vault Working Folder".

Re: This error is seriously getting old. Autodesk PLEASE FIX THIS

CGBenner — Thu, 13 Jan 2022 14:13:08 GMT

@scott_ainsworth wrote:

When inventor and vault seem to be stumbling all over each other

😂 I seriously like that mental image.