DCM Redshift Connection Suddenly Malfunctioning

[cleigh]

I use DCM to connect to Amazon Redshift ODBC.

Until now, I've been able to build my workflows in Alteryx Designer, then publish to Alteryx Server using the DCM connection. Usually, the connection string on my input tool looks like dcm:HR Prod-cleigh (where HR Prod is the data source and cleigh is my Credential)

Today, I dragged a new Input Tool to the canvas, checked the 'Use DCM' box, clicked 'Set Up a Connection', and navigated to Server > Gallery > HR Prod (Gallery).

(It did not ask me which credential to use).

I set up my redshift query, clicked OK, and when the window closed, the 'Use DCM' checkbox was suddenly unchecked, and the alias changed to a local odbc connection aka:HR Prod. The workflow runs successfully in Designer, but I can't save to Alteryx Server because aka:HR Prod is not a recognized connection.

Approaches I've taken:

I changed my DCM settings to force DCM connection Only. No success. Restarted Designer, restarted my work PC. Tried In-DB tools instead of a basic Input tool. No success. Modified my DCM Data Source and Credential in Server and re-synced in Designer.

I created a new DCM Data Source for the same Redshift credential (this synced in Designer, but does not show up in the list of available Connections when trying to configure an Input Tool)

Strangely enough, I can copy-paste an old Input Tool from an earlier-built workflow that successfully connects to the dcm:Hr Prod-cleigh, and modify that query with no issue. If I try to modify that same tool's connection, it will again uncheck Use DCM and revert to aka:HR Prod

Any idea what's going on? Do I have an aliasing issue on my side? Or could something be wrong on the Server/DCM side? I don't know why the Input tool would 'force-quit' using DCM...

[AlteryxMatt]

Hi @cleigh!

I think this may be a good candidate to report through my.alteryx.com to ensure Customer Support is aware and can provide insight into resolution. The case submission process will also search the Knowledge Base in case there is a known solution

[cleigh]

My internal IT contact who manages the Alteryx Server did end up reaching out to Alteryx technical support.

We had a troubleshooting session, and we found a workaround.

We didn't confidently determine the cause of the issue where Designer was not connecting the DCM Redshift connection, but my hypothesis is that the Redshift ODBC datasource was configured on the company Alteryx Server without credentials (due to security concerns). For whatever reason, that configuration worked for a couple months and allowed me to connect and pass through a DCM credential but stopped working in Designer this past week.

The workaround: instead of connecting to DCM in Designer, I set up an ODBC connection on my work PC that shares the same name as the ODBC connection on Server, and has credentials embedded (encrypted, I think?). When I publish the workflow to Server, the DSNs match, and the workflow runs like magic 🙂