Issue with Server Data Connections after Updating to Version 2024.1.1.49

[esar]

Hello,

I recently updated the server to the latest version 2024.1.1.49 and Designer to Version: 2024.1.1.49 Patch: 1.

Since the update, I have encountered an issue with updating Data Connections from the server. The DCM shows the following error: "Incorrect decryption parameters" on the Desktop side.

Additionally, there are errors in the Manage Data Connections window, and the Sync All function does not perform any actions. 

Data Connections are showing like this in the Server, but if I try to open any of them, there is just a blank area.

 

 

Can anyone assist with resolving this issue?

Thank you in advance!

[MikeFranklin]

Hi Esar - were you able to resolve this issue? If so, do you mind sharing the steps to fix? We recently upgraded to 2024.1.1.49 from 23.2 and are experiencing the same issue.  We have a case opened with Alteryx support and will share our findings as well.

[CatheyH]

Same here :(

[CatheyH]

Solution (with thanks to Alteryx support). @MikeFranklin @esar - hopefully you've been able to get this fixed by now, but documentation for next time! :

On the DCM Credentials - go into Gallery and DCM credentials and re-enter ALL you passwords. If you can't remember any then you will need to delete them. Once all your passwords have been re-entered, Alteryx recognises that these are the most up-to-date credentials and will use these to create credentials on your desktop when you synchronise. You will continue to get errors until ALL credentials have been updated.

The principle is the same with Gallery connections - go through ALL of your connections and reenter/save any passwords where they have been hardcoded into the connection string. Once they have all been done you should notice that the sync button starts working again. You might get a lot of red exclamation marks - click on any one of these to make them go away. If there is still a problem, one thing I have noticed helps (but no idea why) is to File/Open Workflow/Server/Select your gallery then CLICK on any one of your apps/workflows. No need to open it - close the window then try syncing again.

For emphasis: You WILL continue to get errors until ALL credentials have been updated - Alteryx refuses to synchronise unless ALL credentials/connections are error-free.

Note that if you have deleted / recreated any credentials in trying to fix the issue, they will need to be re-entered into your workflows/apps.

[MikeFranklin]

@CatheyH - thank you for your reply.  Adding to your solution steps below with the steps to complete the same via command prompt.  Referencing @esar 's last screen shot, attempting to update the data connection through the gallery resulted in a blank, grey, screen, so we could not immediately complete this online.

Command prompts to execute:

• Navigate to the Alteryx\bin file path

cd "D:\Program files\Alteryx\bin"

• Navigate to the mongo shell 

mongosh -u user -p password -host localhost:##### AlteryxGallery

- replace password with the password (not the admin password) in your system settings: controller > persistence> database > host 

- replace localhost:##### with the host name in your system settings: controller > persistence> database > host

• Update all passwords 

db.getCollection("dataConnections").updatemany({},{$set : {PasswordSecured:''}})

- note, we only have 5 data connections with 1 encrypted password causing the issue, so 'updatemany' was acceptable for us.  If you have more connections and want to attempt to target the update, you can run the script below instead by targeting the specific connection to update:

db.getCollection("dataConnections").update({},{$set : {PasswordSecured:''}})

You can now access the data connections through the gallery to update all necessary passwords.

[pcieslak]

We recently updated from 23.2 to 24.1 and are experiencing this same issue. We have over 150 credentials so manually updating each individually is not feasible. Are they any other troubleshooting options or workarounds to fix these the corrupt parameters or at least help identify which credentials are corrupt?