Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

This document contains unresolved components

julian.paphitis
Contributor

This document contains unresolved components

julian.paphitis
Contributor
Contributor

Hi Guys ,

 

I'm getting this error on opening:

 

This document contains unresolved components. Saving it may result in links to the unresolved component to be lost for ever.

 

I've been plagued by this error for over a year, I'm at my wits end and not sure how practical F360 is for large scale assemblies, sorry for the tone, I am very frustrated.

 

Basically many joints have just exploded and are in red. I believed this is related to the recent update. This is the first time I have opened this design since. I have tried opening previous versions and they all fail in the same way. So I don't think the message is strictly true that a component is unresolved.

 

I've had this before and support were not able to resolve and escalated to development (if I remember correctly), never heard back.

 

I was advised to restore from my own exported .f3z backup. Since then I have many drawings and they don't get backed up, so I guess they will be orphaned if I restore from my .f3z backup this time.

 

I now do a Compute all before every save and have no Positions in the Timeline (I've learnt to my cost they can cause this issue). That has served me well for a few months until now.

 

Any assistance in getting my latest version fixed would be much appreciated.

 

Julian

0 Likes
Reply
444 Views
9 Replies
Replies (9)

HughesTooling
Consultant
Consultant

I see you have a lot of inserted components, is the timeline marker at the end of the timeline in all the designs you've inserted? Only time I've seen this sort of error is when I've forgotten to move the timeline marker to the end and made a save in a design. Wish Fusion would warn you when you save, especially if the design is used in another design or drawing.

 

Mark

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


0 Likes

tyler_henderson
Community Manager
Community Manager

Hi Julian,

Can you tell me if you have turned on the Preview Feature for "Resolve External Components"?

If you have that turned On, then you should be able to determine the reason for each unresolved component.  However, from the image you attached, it looks like the unresolved components may be nested in the assembly structure, so you may have to expand the browser nodes to find them.  They will appear with a red "?" on them in the browser, then you can hover on them to see a tooltip that tells you the reason.  Potential reasons are: component files were deleted, components were moved to a Project to which you don't have access, or components are in a Project that was archived.  If you you don't have any success, is it possible for you to share the dataset so I could check it for you?

Tyler Henderson
Principal User Experience Designer

0 Likes

julian.paphitis
Contributor
Contributor

Hi Tyler,

 

Thanks for the reply. So yes I did try the preview feature. I was unable to locate any unresolved components in the Browser, however as you alluded to maybe I did not dig deep enough into the tree. I did not have the Compute Unresolved in the menu though. I've not worked on any component files for weeks.

 

Anyway the plot thickens. We have a power cut at work, so I tried at home and guess what it loaded fine. I will need to try at work when the power comes on. Could this be a caching issue?

 

I'll keep you posted once I get back on my work PC.

 

Thanks

 

Julian

0 Likes

julian.paphitis
Contributor
Contributor

Hi Mark,

 

Thanks for the reply. I don't think I forgot to move the Timeline marker to the end, but like you say I can't be sure!

 

Best regards

 

Julian

0 Likes

tyler_henderson
Community Manager
Community Manager

Thanks for the additional information, Julian.  I'm definitely interested to hear what you discover when you are back on your work PC.

Tyler Henderson
Principal User Experience Designer

0 Likes

julian.paphitis
Contributor
Contributor

Hi Tyler, so the problem persists on the work PC. I turned on the preview feature and that will allow it to open with no errors, however if I do a compute all the errors then appear. On the face of it the errors look identical to when first opened without the preview feature. Like you say if I nail down the tree I can find the offending inserted components, they are in red and if I right click there is an option to Resolve Component.
I'm reluctant to do that in light of the fact that it runs OK at home. Happy to give you access to the design, perhaps email me directly on the email associated with my account and the forum and I can give you access?

 

Thanks

 

Julian

0 Likes

tyler_henderson
Community Manager
Community Manager

Hi Julian,

If you click the "Resolve Component" command, it will display a dialog that tells you why the component is unresolved.  You can cancel that command, but could you tell me what that dialog tells you about the reason those components are unresolved?

Thank you.

Tyler Henderson
Principal User Experience Designer

0 Likes

julian.paphitis
Contributor
Contributor

Hi Tyler, so it does nothing when I click Resolve Component. However I have fixed it! I cleared the cache as per this: https://knowledge.autodesk.com/support/fusion-360/learn-explore/caas/sfdcarticles/sfdcarticles/How-t...

 

It seems OK now. For reference, pre fixing it, the offending unresolved components were just completely gone. They were still in the project and also they were down another level. These started life as STEP files.

 

Not sure if you want to dig deeper? but I'm happy now:)

 

Thanks

 

Julian

0 Likes

tyler_henderson
Community Manager
Community Manager

Thanks for the additional information, Julian.  This is a unique scenario that our development team is looking into.  I'm glad you were able to get past this issue and continue working normally.  Hopefully our team can determine why this happened and prevent it in the future.  I'll let you know if we need anymore information from you to assist this effort.

 

Best regards,

Tyler Henderson
Principal User Experience Designer

0 Likes