File exists in vault tab not in model tab

File exists in vault tab not in model tab

plausa.us
Advocate Advocate
420 Views
6 Replies
Message 1 of 7

File exists in vault tab not in model tab

plausa.us
Advocate
Advocate

I am perplexed, I hope someone can help with this issue.

I have an assembly model (linked to vault) open in Inventor.  On the vault tab there is a file (now) called 'Ghost File Cant Delete......'  When you try to find this part in the Model Tab, It just is not there, not to be found.  I've expanded everything, can not find it. In Vault Tab, I right click to find in Window, it does not move, zoom, nothing.  It is not found.

 

I have tried removing file locally, open assembly, it requests to download.  If no, it is unresolved (skip). There is no right clicking on this file in vault tab to delete.  If it could be found in the model tab it could be deleted.

 

Has anyone seen anything like this, and can give me the how to, to get rid of this attached/file association?  I would appreciate your help.

 

0 Likes
421 Views
6 Replies
Replies (6)
Message 2 of 7

Gabriel_Watson
Mentor
Mentor

What is the ghost file's extension format? This could be a (texture) bitmap or image file associated with any one of your file's material appearances. To remove links use Tools tab > Links > select and "Break Link". If that doesn't work, try via iLogic:

- Inventor model links cannot be broken (OLE links):
1- Go to the Manage tab > Add Rule;
2- Paste the following code into the new rule;
3- Click on "Save & Run" and hit OK to remove each OLE link.

 

 

Dim oDoc As Document
oDoc = ThisApplication.ActiveDocument
If oDoc.ReferencedOLEFileDescriptors.Count = 0 Then
    MsgBox("There aren't any OLE references in this document.")
    Exit Sub
End If
Dim aOLERefs() As ReferencedOLEFileDescriptor
ReDim aOLERefs(oDoc.ReferencedOLEFileDescriptors.Count - 1)
Dim iRefCount As Integer
iRefCount = oDoc.ReferencedOLEFileDescriptors.Count
Dim i As Integer
For i = 1 To iRefCount
    aOLERefs(i - 1) = oDoc.ReferencedOLEFileDescriptors.Item(i)
Next
For i = 1 To iRefCount
    If MsgBox("Delete """ & aOLERefs(i - 1).FullFileName & """?", vbQuestion + vbYesNo) = vbYes Then
        aOLERefs(i - 1).Delete
    End If
Next

 

 

Message 3 of 7

plausa.us
Advocate
Advocate

The file in question is an .iam, assembly file that I can't find in model tab to delete.

Never the less, I did run the OLE rule you suggested to see  'There aren't any OLE references in this document'.

 

 

Message 4 of 7

Gabriel_Watson
Mentor
Mentor
On a second thought, just browsing online for the issue points out it might be a file corruption:
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Ghost-reference-in...
Message 5 of 7

cidhelp
Advocate
Advocate

Hello @plausa.us ,

look at the parameters of your assembly. There could be a reference to the "ghost". Also 3D-annotations could reference other models.

 

0 Likes
Message 6 of 7

plausa.us
Advocate
Advocate

This does not seem to apply.  the assembly file wasn't an iassembly change to assembly.  There isn't any ghost part on the drawing.  Technically it is on the drawing because the assembly that has the ghost part is on the drawing. 

The drawing being the upper level, does not seem like it would control the ability to delete a file in the assembly associated.

0 Likes
Message 7 of 7

plausa.us
Advocate
Advocate

The parameters of the assembly.  This is a huge assembly, it has many parameters associated to constraints.  I did purge the 3 parameters associated to nothing, which didn't make the ghost file, appear in the model tab to delete.  If the file could be seen in the model tab then I could see if any constraint parameters were associated.  If I could see it in the model tab, I could delete it, this is the desire.

 

I've tried opening it with the ghost file not existing locally.  It asks to get it from vault.  No.  I don't want to leave an assembly with and 'unresolved' issue. which is the only way to dis associated the ghost file. 

I've tried making some other file with very visible parts inside, saving it as the ghost part.  Then trying to resolve the ghost file with this other assembly and it will not let me.  Even if the same name or a completely different file.  I get this message. (this w/different assembly name).

plausaus_0-1707132134914.png

And it will just not allow it.  It will keep asking to resolve this file, only if it is the original file, will assembly be resolved.

 

0 Likes