DCM Error - Collaboration Sharing Error: Borrowed object misuse

Hello Community!

We are having an issue with the DCM setup. What happenes is that we get the error message " Collaboration Sharing Error: Borrowed object misuse"

The steps we do to resolve it is:

1. Open the workflow. Try to run it. It throws an error.

2. We go to connection Manager and choose the "Test Connection". This opens the browser authentication we have setup. The test fails.

3. Running the flow now, still fails.

4. Back to connection manager. Edit connection, make NO CHANGES, and agin click "Test connection". Now it is successfull and the flow runs.

This is going to annoy our users a lot. Anyone had the same issue with a solution? We are also making a ticket with Alteryx on this, but it is nice to hear if others may have a solution or to create a thread on the issue.

How our DCM is setup:

1. We user Azure AD application and Private tokens

2. Our data source is snowflake

3. Deigner and Server version 2024.2

image (1).png

Database Connection

Accepted answers

jensroy

Hello and thanks for looking at it!

Yes, I can confirm that we are only sharing the Data source and not the token itself just like that doc explains.

We had a call with Alteryx Support on Friday which said this is likely solved on version 2025.1, and we were on 2024.2.

I tested it this morning, and so far it seems that upgrading Alteryx does solve it. But so far I have a sample size of 1, I'll need more feedback from the users.

All comments

Dean4U

Hi @jensroy,

Thanks for reaching out to us. Please check out the below knowledge base article with a possible resolution.

Alteryx DCM Error KB

Let us know if this helps you out.

Take care.

jensroy

Hello and thanks for looking at it!

Yes, I can confirm that we are only sharing the Data source and not the token itself just like that doc explains.

We had a call with Alteryx Support on Friday which said this is likely solved on version 2025.1, and we were on 2024.2.

I tested it this morning, and so far it seems that upgrading Alteryx does solve it. But so far I have a sample size of 1, I'll need more feedback from the users.

jensroy

I will paste in respons from support as well:

Hello

I hope you had a great weekend!

As we discussed on the call, this issue is related to a known defect. The defect ID is GDCM-4925.

This issue has been fixed on the latest version of Alteryx version 2025.1

I am checking further internally to find a potentially viable workaround.

We understand the importance of this, and we deeply apologize for any inconvenience this may cause.

If you have any questions or need further clarification, don’t hesitate to reach out.

Have a great day!

Best regards,

Quick Links

This months top contributors

hhaigh1 280

FláviaB 262

JORGE4900 235

caltang 177

DanM 167