DRAFT KB-XXXX Connected systems fail to load with InsufficientNameUniquenessException found in the application server log following a restart

Symptoms

Following a restart of the application server, select Connected Systems fail with the below error message:

In the application server log, the below error message will be printed:

YYYY-MM-DD HH:MM:SS [localhost-startStop-1] ERROR com.appiancorp.connectedsystems.http.migration.configobject.MigratePersistedConnectedSystems - Error persisting, migration will be skipped for this connected system: ... com.appiancorp.suiteapi.content.exceptions.InsufficientNameUniquenessException: Name is insufficiently unique

Cause

This behavior occurs when an Appian application has the same name as a connected system. This issue has been addressed via AN-145648 in the following hotfixes/versions:

• 20.1 GA
• 19.4 Hotfix Package A
• 19.3 Hotfix Package D
• 19.2 Hotfix Package F
• 19.1 Hotfix Package I
• 18.4 Hotfix Package M
• 18.3 Hotfix Package P
• 18.2 Hotfix Package S

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

There are two workarounds that can resolve this issue:

1) Recreate Connected Systems

Recreating any Connected Systems that are in this broken state.

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

• This article applies to all versions of Appian.
• This article applies to Appian 7.11 and later.
• This article applies to Appian 16.2 and earlier.
• This article applies to Appian 7.11 and 16.1.
• This article applies to Appian 16.1, 16.2, and 16.3.
• This article applies to all versions of Appian from Appian 7.10 to Appian 16.2.
• This article applies to all versions of Appian using JBoss EAP 6.4.9 as an application server and Internet Explorer 9 as a web browser.
• This article applies to all versions of Appian Cloud.

Last Reviewed: Month YYYY