Error code "EXC-002" when accessing an exchange file

[Cheyne.Sear55GJ9]

Hi All,

I am currently following the Task 1 - Access Exchange Container (https://aps.autodesk.com/en/docs/fdx/v1/tutorials/1_access_exchange_container/). However, when I query the exchange container within ACC Docs (generated from a Revit 2023 file) in Step 5 I get the following error:

Status code: 403
{"title":"Access denied regardless of authorization status.","detail":"Read on the source file is forbidden.","requestId":<requestedId>,"code":"EXC-002"}

I am authenticating this via a two-legged authentication flow and have tested it with both a Traditional Web and a Server2Server App. Both return the same error.

The permissions on the folder are set for "Everyone" as Create->(View+Download+Publish-markups+Upload). However, I am unsure how to set the permissions for the Source Revit file and the Exchange file individually. Furthermore, I am unsure if these permissions have an affect on app permissions.

Happy to provide any additional information, if needed.

Thanks,
Cheyne

[srinivasan.jayaraman]

Would it be possible for you try with 3-Legged token ? Data Exchange system has restrictions on 2-Legged token. 

[Cheyne.Sear55GJ9]

Thanks for the reply.

Would you happen to have any links to where Autodesk identifies these restrictions? The workflow I am looking at developing requires a server-to-server connection without user authentication.

I noticed in the API Reference page for GET Retrieve exchanges that the Authentication Context is "app only" and the scope only requires "data:read". According to Autodesk this is sufficient to make calls using a 2-Legged token (link). I'm still unsure, however, if this context applies across the whole Data Exchange API or not.

[srinivasan.jayaraman]

I agree that this is not explicitly documented. We are working on supporting 2-Legged for your use-case and we will get back before end of day today on the status of the feature . We are hoping to get this LIVE today so that you can continue trying it out.

[Cheyne.Sear55GJ9]

Great, thank you.

[srinivasan.jayaraman · Accepted solution]

@Cheyne.Sear55GJ9 - 2-Legged support is LIVe now. can you please check and let me know? 

[Cheyne.Sear55GJ9 · Accepted solution]

@srinivasan.jayaraman that worked! Thank you very much for the quick resolution.

[jontyrhodes1970]

Error code "EXC-002" means that the exchange file is corrupt or invalid. This can happen for a number of reasons, such as:

• The file was not properly created or saved.
• The file was damaged during transmission or storage.
• The file is trying to be opened by a program that does not support it.

To resolve this error, you can try the following:

• Check the file format. Make sure that the file is in the correct format for the program you are trying to open it with.
• Try opening the file on a different computer. If the file opens on a different computer, then the problem is likely with your computer.
• Try repairing the file. There are a number of software programs that can be used to repair corrupted files.
• Recreate the file. If all else fails, you may need to recreate the exchange file.

[jontyrhodes1970]

I hope this information is helpful.

[jontyrhodes1970]

Data exchange communities can be formal or informal. Formal data exchange communities often have a set of rules and procedures that govern how data is shared.