HELP! Unable to open assembly

HELP! Unable to open assembly

Anonymous
Not applicable
1,116 Views
8 Replies
Message 1 of 9

HELP! Unable to open assembly

Anonymous
Not applicable

I have been able to open the current version several times since saved on 3/9/16 and today I get the error:  

 

"std:: exception"

 

A360 Error Message

Design data is not available for the selected version.

Could not open file: /Users/Lison/Library/Application Support/Autodesk/Autodesk Fusion 360/XKRNNN8K4WPF/W.login/F/Assembly_SFSD.c3582561-45ea-4eea-86c3-e76d9ddbbf20.f3d, Version Number: 15, Error message: std::exception

0 Likes
1,117 Views
8 Replies
Replies (8)
Message 2 of 9

innovatenate
Autodesk Support
Autodesk Support

Could you uplaod a copy of the Fusion 360 Diagnostic log files?

 

Diagnostic Log files ppt.png

 

For a quick work-around, you may be able to promote a previous version of a design and then open it.

 

See the below link for some details on how to do this.

http://fusion360.autodesk.com/learning/learning.html?guid=GUID-A5F8A894-8CA4-4075-B686-1A81E206C963

 

Hope that helps!

 

 

 




Nathan Chandler
Principal Specialist
0 Likes
Message 3 of 9

Anonymous
Not applicable

I am not able to promote a previous version for some reason. Attached is the error message and log files.

0 Likes
Message 4 of 9

innovatenate
Autodesk Support
Autodesk Support

There appears to be a bad reference in the file causing this issue.

 

Can you try promoting the design named 91290A340.STEP.f3d back to version 1 and then retesting to see if the file will open?

 

If this doesn't work, you may have to promote version 10 of the assembly. This is the last version of the file that does not contain a reference to the bad file. If the  above suggestion does not work, can you give this a try.

 

I hope this helps!

 

Thanks,

 

 




Nathan Chandler
Principal Specialist
0 Likes
Message 5 of 9

Anonymous
Not applicable

I promoted v1 of "91290A340.STEP"f3d" then tried to open v15 of the "Assembly_SFSD" like you suggested but it gave the same "std:: exception" error message. I tried opening version v10 and it opened just fine. The only problem is there is a lot of work lost between v10 and v15.

 

I have opened v15 several times to view then closed with no trouble until today. I have not modified any of the referenced files either. The only thing that I can think of that possibly could have went wrong is that a couple times when I opened the file, I closed my laptop and lost the connection and when I opened my laptop, I had to restart Fusion 360. Upon restarting, I was prompted with the option if I would like to restore an autosave, I declined and instead I just opened v15 again because I was not attempting to make any changes, I was just getting dimensions off some components. 

 

What are my other options here besides going with v10? Is it possible to just exclude that bad reference file from the assembly? So then I would only have to worry about that one component and any subsequent references.

0 Likes
Message 6 of 9

saketsatta
Autodesk
Autodesk

Hi,

 

We might be able to repair v15 of the assembly so it can be opened again. Can you export the entire assembly as an f3z (it should be at v15 when you export) and send the f3z to saket dot satta at autodesk dot com?

 

Thanks,

Saket Satta

Fusion 360 Engineering

Message 7 of 9

Anonymous
Not applicable

Hi Saket. The repaired file work for me the first time. I opened it and deleted the broken references and replaced the dummy file and all was good. That was Saturday. Today I try to open the same file and I get an error message:

 

"Could not open file: /Users/Lison/Library/Application Support/Autodesk/Autodesk Fusion 360/XKRNNN8K4WPF/W.login/F/Assembly_SFSD.a83bd81f-4c0c-46b9-b025-8bde6a6981ca.f3d, Version Number: 1, Error message: Ok"

 

So then I tried reuploading the repaired assembly file into the data panel again, but now it says that file is corrupt. How can that be? Also, I try opening other files and it seems that none of my files will open, regardless of what project they are in.

 

It seems to me there is a problem with the Fusion software or my permissions perhaps. 

 

I have attached the diagnostic files for reference. 

0 Likes
Message 8 of 9

Anonymous
Not applicable

Hey @Anonymous,

 

This error may be related to the recent update of Fusion and not your previous issue - Have you tried restarting Fusion and seeing if that helps? That is what worked for me.

 

Hope this helps!

0 Likes
Message 9 of 9

Anonymous
Not applicable

Wow yes, that did the trick. Thank you Autumn!

0 Likes