New coordinator is unable to decrypt existing stored credentials (4234167)

Consider the following:

1. Change Auditor Coordinator is installed and running on Server1
2. There are encrypted credentials stored by Change Auditor for various coordinator tasks such as Internet Proxy Server, SMTP Configuration, Shared Folder configuration, etc
3. The Coordinator on Server1 is uninstalled
4. A new Coordinator is installed on Server2 and uses the existing Change Auditor database
5. The newly installed Coordinator is unable to decrypt the credentials for such configuration items as mentioned above
6. The user must re-specify the credentials and commit the changes again via Coordinator on Server2
7. The Coordinator on Server2 is now able to decrypt the credentials as expected.

Every 5 minutes the currently installed Coordinator(s) check for the existence of any new Coordinator(s). If a new Coordinator is detected, it will generate new encrypted data for which the newly installed Coordinator can now also decrypt. If all original Coordinators are removed before a new Coordinator is added, this process cannot occur and the new Coordinator is unable to decrypt previously encrypted credentials.

WORKAROUND 1:

Whenever possible add a new Coordinator before deprecating the last existing Coordinator to ensure newly added Coordinator is able to decrypt existing encrypted credentials. The Coordinator which is to be removed can also be stopped for a small duration of time to ensure no unexpected issues arise.

WORKAROUND 2:

In the event previously existing Coordinators are removed/no longer available and a new Coordinator is added ensure to re-supply any credentials in the following areas of the configuration (if in use):

• SMTP Configuration (Administration | Configuration | Coordinator)
• Shared Folder Configuration (Administration | Configuration | Coordinator)
• Proxy Server (Administration | Configuration | Agent | Configurations | Proxy Server)