Gallery Data Connections not syncing with the designer
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello
We have a server with lots of gallery data connections, we recently observed that the gallery connections are not being synced with the designers of the users. I tried to rename the galleryalias.xml file and relaunched the designer but it did not create a new galleryalias.xml file. The users are able to open workflow from server in designer, publish new workflows to the server from designer but they are not able to sync the gallery data connections. Can anyone please help in finding the solution for this
Server version: 2022.1.1.42654 Patch: 7
Thank you
- Labels:
- Alias Manager
- Gallery
- Server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Did this ever get resolved for you? We're on 2022.3.1.637 Patch: 11 and are seeing this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nope
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
We've seen this after our last two upgrades. If it is the same issue, re-entering the passwords on all of the connection strings fixed the problem for us. Unfortunately it wasn't something we could test because it wouldn't work until they had ALL been done (and non functioning connections removed).
Something similar happened in DCM after desktop upgrades - they stopped syncing. We had to remove all the connections on the desktop machine then re-synchronise to pull down the connections from the server. Again, it was all or nothing.
PLEASE make sure you back everything up before starting to delete stuff.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
This is the "fix" for it. In our case, the server token keeps getting corrupted. When it happens, we have to generate a new token, re-enter the MongoDB password, and re-enter the password for all connections that have a saved password.

- « Previous
- Next »