Permission errors opening files?

[Garrett_Wade]

For some reason recently i've started to get these types of errors (see attached screenshot). I usually work on one of 2 computers and most of the time the errors only seem to happen on the 2nd computer after working on the file on the 1st one. I've found that sometimes rolling back a version will allow me to open the file but this obviously isn't ideal.

Any insight to the cause of this or how I can fix prevent it from happening?

[karina.harper]

Hi @Garrett_Wade 

Can you attach the .zip of  your log files? I can look in there and see if I can get more information on what's happening.

You might also try performing a clean uninstall and reinstall.

Let me know what happens.

For searchability's sake, here's the error message:

boost::filesystem::status: Permission denied: "...f3d"

[Garrett_Wade]

@karina.harper Sure, Please let me know if there is anything else that may be of assistance:

[karina.harper]

Hi @Garrett_Wade 

Thanks, those are super helpful.

- Were you able to uninstall/reinstall? I'm wondering if this is due to one computer receiving the hotfix but not the other. Try that first.

- Is this occurring with one particular file or multiple?

- Can you share the file with me as a link? If you have referenced designs it should come through as an .f3z

[Garrett_Wade]

@karina.harper 

Here is a link to one of the files i'm experiencing this issue on. 

https://a360.co/2UubWus

I just got back to the 2nd computer (one having issues opening some files). I'll attempt to uninstall and reinstall now. I did ensure both computers are on the latest version of the OS and already did an uninstall/reinstall on the 1st computer.

[karina.harper]

Hi @Garrett_Wade 

This is a bit of a guess, but I'm thinking it could have to do with the Generic Vise that you have in the file.

Something I would try is:

1. delete the generic Vise

2. open the Generic Vise sample file

3. right click the top component -> Save Copy As. (Not File -> Save As!!)

4. Replace the vise in the assembly with this newly created "Save Copy As" Version.

We have an issue currently where "Save As" doesn't create a new ID# for the new file created. This can cause some confusion when deriving these features as Fusion is looking at multiple files with the same internal ID#. It's possible that your assembly is looking at both the copy of the file you made as well as the "locked" sample file and not allowing you to access/edit because of that. 

Let me know how it goes!

[karina.harper]

Whoops, duplicate post.

[Garrett_Wade]

@karina.harper 

Ok, so fresh install now on both machines, same issue still exists.

I think I understand what you are explaining as a possible cause/explanation for this issue.....and on its surface that makes sense. What is interesting is that i'd imagine that issue would exist on both machines attempting to open that file and it doesn't, it seems to be isolated to only one direction. In addtion to that viewing these files in a web browser or in the a360 app doesn't seem to be an issue and I'd imagine the same ID conflict issue would be a problem here also.

As far as your suggested solution - I'd imagine once I get back to the location of the first machine I could open this file and remove the vise out of this file -> save > test opening the file next time at the 2nd computer (different location across town) to see if this works. Unfortunately it will be tomorrow before i'm able to fully test this.

If this does work, in files like the one provided- its not a huge deal to delete the vice since it was only there for visual checks in CAM simulation, but some of my other projects having this same issue, this will not be as easy to simply delete other parts out of them without breaking most of the project due to how they were designed or setup.

This would lead to another question. Besides using 'Save as' rather than save right now due to this being known to potentially cause issues (possibly my problem here). Should I also stop work on other designs built in this same manner or continue with them under the understanding that i'm at risk of having to redo it?

[karina.harper · Accepted solution]

Hi @Garrett_Wade 

Great questions and great thoughts.

First off - I think a workaround would be to export your file from your hub as a .f3z file and then uploading it via the data panel. I would try that when you receive the error and see if it will repair it. This is not an ideal solution, but it might provide a workaround in the meantime.

..

---

This would lead to another question. Besides using 'Save as' rather than save right now due to this being known to potentially cause issues (possibly my problem here). Should I also stop work on other designs built in this same manner or continue with them under the understanding that i'm at risk of having to redo it?

---

This is a great question. First to clarify: "File -> Save As" is broken. Right clicking the component and selecting "Save Copy As" is functional.

If it were me, I would probably perform a "save copy as" on any misbehaving components and re-derive them - particularly if the original component and the "saved as" component are derived into the same file. I've seen this cause some issues. But if you haven't seen issues relating to that (unexplained/unexpected de-linking or requesting link be updating) you may not have to worry about it.

Another question for you - are you an admin on both computers?

[Garrett_Wade]

@karina.harper 

Thanks for all of your help and suggestions on this.

To answer your question, I am the admin on both machines. I'm actually the only person with password/access to both of the computers mentioned which is why I was so confused to see a permissions type error (my computers, my account...etc)

[Garrett_Wade]

@karina.harper 

As an update to this it appears you are correct and its perhaps the issue you described. Going through the website and downloading a copy of the file (*.f3z) and then right clicking on the data panel and doing a "import new version" seems to allow me to open one of the files I previously could not on this machine.

I'm still curious if this is a file ID conflict type issue why it would work without issues on one machine and not the other...but I suppose that is more of a backend thing for the devs to worry about and not something that has any real impact on me.

Thank you for all your help. For now i'm going to consider this issue solved. It's not entirely I guess... but the problem appears to be known and there is a workaround path than can be followed in the short term.

If other issues related to this appear or it doesn't work on some of the files i'll report back here.

[karina.harper]

Hi @Garrett_Wade 

That is interesting. I will pass this thread along to our devs who are working the issue in case it could be informative for them.  And yes - if you see it again and this method doesn't work please let us know. Also if you notice any other hints or triggers that might be causing the behavior.

Thanks!