Error 403: The current user is not authorized to see this content.

Error 403: The current user is not authorized to see this content.

Anonymous
Not applicable
2,317 Views
5 Replies
Message 1 of 6

Error 403: The current user is not authorized to see this content.

Anonymous
Not applicable

Username: Nabi Nabiyev
UserID: 6TNZRMAYYAK6
AssetID: 7491
Code: 403
Details: This error occurred while attempting to migrate a collab doc to a draft savepoint.
Time: 1/25/2019 @ 18:27:55Capture.JPG

Reply
Reply
0 Likes
Accepted solutions (1)
2,318 Views
5 Replies
Replies (5)
Message 2 of 6

david.mellis
Autodesk
Autodesk
Accepted solution

Thanks for reporting this! We're working on a fix for it... 

 

It looks like this package is from an Autodesk-supplied EAGLE library, so you don't have permission to edit it. If you need to, as a workaround, you can make a small change to the footprint, then create a new version of the managed library. That will fork the 3D package and you should be able to edit the fork. We're also working on a better workflow for that.

Reply
Reply
Message 3 of 6

Anonymous
Not applicable

Hi David, i am also having this 403 error issue, but since i used a lot of the eagle default libraries in my design, does this mean i will have to re-edit/save the library's locally, then create a new managed library, just so that i can export my design as a step file?

Reply
Reply
0 Likes
Message 4 of 6

david.mellis
Autodesk
Autodesk

The parts should still work fine for creating a STEP file or pushing to Fusion. It's just opening them inside the package editor in EAGLE that gives this error message (but again, you wouldn't be able to edit these 3D packages anyway). We should have a fix out for this soon.

Reply
Reply
0 Likes
Message 5 of 6

Anonymous
Not applicable

I had a similar issue but with a 3d model I made with the package generator.

I'm confused as to how I would not be able to access it.

Reply
Reply
0 Likes
Message 6 of 6

david.mellis
Autodesk
Autodesk

@Anonymous this should now be fixed, i.e. you should again be able to open these packages in read-only mode inside of EAGLE (and in the web). Again, to edit them, you'll first need to edit the footprint and create a new version of the managed library. We're continuing to work on a better workflow for that.

Reply
Reply
0 Likes