Cannot synchronise DCM between Server & Designer

[chrisha]

Hi everyone,

we've recently upgraded to Alteryx 2022.3 and would like to make use of the DCM for managing our credentials.

We have DCM enabled on both the Server and the Designer machines (screenshot from Designer machine, settings identical on Server):

When trying to synchronise credentials on the Designer, however, we cannot connect to our Gallery:

Server connection failed. Check your network connection and server credentials.

Connecting to the Gallery for opening and saving Workflows works without a problem. We are using "Integrated Windows authentication with Kerberos" for authenticating users.

Any points what might be the issue here?

Best regards

Christopher

[gabrielvilella]

Does the version number match between Designer and Server? The full version number.

[chrisha]

Yes:

Designer: 

Version:  2022.3.1.450  Patch: 2

Server:

Firewall allows traffic on ports 80 and 443 per Server documentation. Port 27018 is filtered as we are using the embedded MongoDB on a single server instance (single node).

Any other ideas?

Best

Christopher

[gabrielvilella]

You might need to raise a support ticket. 

[SeanAdams]

Hey @chrisha - did you manage to get to the bottom of this one - this is an important discussion as more and more of us start leaning on DCM - and so if you've managed to figure this out it would be great to hear what helped here!

[chrisha]

I talked to support, the fix was simply removing the Gallery connection and re-adding it. Afterwards everything synced fine.

[SBK]

I have a similar issue where I can't sync server connections to my Designer. I can connect and open gallery workflows just fine, but I get the below error "Server response decryption has failed" when syncing connections in my connection manager.

Anyone have any idea what could be the cause? I tried recreating the connection multiple times but still the same error.

[mjackey]

SafaB 
Were you able to resolve your issue?  I am having the same issue.

[SBK]

Hi Mjackey,

My Org IT folks performed a reindexing of the MongoDB and I believe it's what helped. I haven't come across this error since.