Inventor Assembly Part Reference To Resolved Document Is Not Usable

[Anonymous]

I am going to attach a screenshot of the issue that I am now having. Every time that I open this file it gives me this error code and I have to go and find parts for the assembly again. Its not very many parts but its the same number of the same parts. I noticed I was also having issues saving the file. It would act like I saved it then if I clicked the save button again It would act like I never saved it. But it would save any major changes that I made in the assembly but it would still ask for those missing parts that I had already found every time I opened the file. Is this a corrupt file again or is this due to something else. Please let me know what you can. Thank you for your time and help.

Trevor Jordan

kelly.young has embedded your image and edited your subject line for clarity: Having issues with a part in an assembly

[TheCADWhisperer]

---

@Anonymouswrote:

... or is this due to something else. ...

---

This looks like operator error to me.  (Hmmm, I just took a look at your other posts and it appears beginner taking over from someone else who might have had poor practices.)  I recommend that you pull in a consultant for a day to tidy everything up and maybe a few hours of training to build a strong foundation.

Are you using Projects (*.ipj) 

or are you using Vault?

Have you used Windows Explorer to rename files?

Can you attach *408.ipt and *405.ipt here?

[Anonymous]

I am a bit experienced with the Inventor software and while I am still learning I understand most all of the good practices and operations. I am spending a lot of time cleaning up from the previous guy who made a mess of the files and left me with a mess. 

[TheCADWhisperer]

---

@Anonymouswrote:

... I am spending a lot of time cleaning up from the previous guy who made a mess of the files and left me with a mess. 

---

Learn Projects and for clean-up learn Pack and Go.

[johnsonshiue · Accepted solution]

Hi!

This warning comes up when the file Inventor tries to open carrying a different document id than the recorded id saved in the assembly. I suspect the prior user changed The file name via File Explorer. This is not a corruption. You can simply accept the resolved file and save it. Next time you open the drawing or assembly file, the warning should not come up.

Many thanks!

[Anonymous]

When I try to resolve the files I get this message (linked blow). Then I save it and it seemed like it worked, but when I closed it and reopened it, it made me find the files again. 

[johnsonshiue]

Hi! The error message here indicates that you are trying to select the link file, which is the source file itself. Do you use Inventor Project? Or, you use Default project to manage the files? Could you share an example here?

Many thanks!

[Anonymous]

I have tried to use both the default project and have created my own project files. I haven't seen a difference.

[johnsonshiue]

Hi! Then I will need to see an example exhibiting the behavior.

Many thanks!

[Anonymous]

@johnsonshiue  i get similar kind of message but it doesn't say it is not usable but it is able to find the location of file and asking if we want to resolve this or not.

so is there any way out to identify such cases beforehand using some scripts?

[johnsonshiue]

Hi! This is tricky with data management system like Vault. I don't believe there is a way to predict it. The issue here is that the original source file cannot be found. But, a file with the same name but with a different document ID can be found.

In order to predict this condition, you will need to open the Inventor file and find the document ID it is referencing. Then try to match it with files on disc.

I think you will want to use Vault to manage the files. So, you would not run into the problem that you have files with the same name but they are actually different.

Many thanks!

[Anonymous]

@johnsonshiue hey thanks for the information.

we will definitely  try your way of approach to identify, but we will still need some kind of script to catch hold of that message when we try to open the assembly using script as we have huge amount of data and have less time for migrating the data. 

[Anonymous]

Johnson,

There is a difference between the message ending with "most likely stuff will fail" and the one ending with "is not usable". You can ignore the first one and proceed. The second message fails to make the link and leaves you helpless.

By the way, it would be useful to have 'edit links' in all environments, like it is now in drawing environment only (at least in my version of IV). We are all grownups here. If we exchange a derived part with another we know that all sketches will fail to attach but at least we don't have to start from scratch.

BR

Alex

[radu1234]

Hi Johnson,

I hope all is good with you during these unusual times...

I had the same issues a few times and I have hard time to re-match with the original files; people just dont understand that renaming files in Windwos explorer (instead of Vault) is not the correct way.

My question to you... is there a way to see the document ID and recorded ID that you mention above? That will help me identifying the correct parent faster. I need to know on the faulted file what is the ID that is looking for. 

Appreciate your help

radu

[Bert_Bimmel]

Hi all,

I am currently struggling with a related problem: I have an assembly, that references a part file with the admittedly not very unique filename "3.ipt"  (which has been automatically created upon importing some downloaded STEP file from some purchase part, so don't blame me for that - i have dozens of parts named "1.ipt", "2.ipt", 3.ipt" and so on).

when i try to open that assembly it tells me the following:

the english version would probably be "the file 'blah blah' as a reference to '<incomplete_path>\3.ipt'. this has been resolved to '<UNC-path>/3.ipt', which is actaully not the same file. all references will probaly fail etc. blah blah. Do you want to use it anyway?"

The fact, that it asks me what to do, but then leaving me no real choice by graying out all other options let's me raise an eyebrow, but not to worry, as the only left choice is what i actually want...

Next thing happening is Inventor asking what to use instead:

So, i navigate to the correct folder and give him the correct file.  The next thing is Inventor complaining, that the selected file is not the first file with the given name within the search-path, and offers me the same wrong file he has just offered to me before:

...of course I say "NO", but that just returns to the dialog in which I have been before to tell what file I actually want.

Klicking "Yes" instead won't open the wrong file either, but returns to the file dialog too. So, the only way to escape this infinite loop is clicking "skip", ending up with an assembly with unresolved references:

So, i click "replace component" ("resolve missing component" will result in the same erratic behaviour i have just described), select the appropriate file at the appropriate location, and inventor will complain about not beeing the first file again, and offering the wrong file once again. But here I can klick "No, i really want what i'm telling you"  and Inventor will finally accept it.

So, i save it, close it, reopen it, and everything starts all over again.  I really don't get why Inventor is so stubborn here: The file reference-list point to the correct absolute path where it can find the file with the expected filename and the expected InternalName:

So, why can't Inventor simply open what it is supposed to open, and only complain, if there actuall are issues, such as file not existing, or file bearing a wrong InternalName?

[johnsonshiue]

Hi! The behavior you describes sounds nonsensical to me, unless the selected file has a different DocID than the last resolved file or the file was saved in a newer version of Inventor. If possible, please share the files that exhibit the endless loop behavior. I would like to understand it better.

Many thanks!

[Bert_Bimmel]

Hi Johnson,

here comes the assembly with all its parts. But I doubt, that it is very helpful in diagnosing, as the disturbing part (which is located at a completely unrelated path, which just comes prior to the appropriate path in an order by whoever knows which criteria) is missing in this file set.

But i have also attached two different .ipj-Files, one letting Inventor open the assembly without complaint, and the other one causing the erratic behaviour that i have just described. This reminds me of a thread here that i vaguely remember, but cannot find again, whose core message was "changing the project changes the file", i.e. the file-reference table of an assembly (or drawing, or derived part) contains some information that is affected by the project file, that is currently in use. I have been aware of this fact for ages, but never understood, how this is supposed to make any sense, as the reference table contains absolute paths for each referenced component.

FYI: The appropriate file has the correct InternalName (I assume, that's what you mean with  "DocID"?) and has been saved the last time with the same Inventor Version  as all other files:

Greetings,

Christian (Bert)

[johnsonshiue]

Hi Christian,

Many thanks for sharing the files! I am still trying to understand the problem. I don't think it is a DocID issue. As long as the files can be resolved, they should be fine.

The only difference between the working project and failed project is the Workgroup paths. The working one does not have them. The three ipt files referenced by the assembly were last saved in "4JET_IV\30xxx\konfektionierte Zukaufteile\Siemens\." Is this a library path?

Many thanks!

[Bert_Bimmel]

Hi Johnson,

no, there are no library paths ecxcept for the ContentCenter-Paths* (as you should be able to see, when examining the project files, shouldn't you?).

But another relevant information i missed to share is the original storage location of these two project files, as the project paths within are stored as relative paths (".\Something"), and thus, the location of the project file matters a lot.

So here are the original locations:

Works_fine.ipj: "D:\Vault\4JET_IV" 

Works_not:  "\\4jet\dfs1\SpeedyFileStore"

*FYI: I avoid using library paths as they're totally counterproductive because of this:

https://forums.autodesk.com/t5/inventor-ideas/stop-telling-me-i-need-to-save-something-i-haven-t-cha...

Greetings, Chris

[johnsonshiue]

Hi Christian,

The network path indeed could be an issue. It seems that due to certain user profile settings or security settings, a network path may not be recognized properly by Inventor. Here is a related article.

https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/How-t...

Many thanks!