KB-2042 Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

Parmida Borhani — Thu, 19 Dec 2019 03:21:51 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 12/19/2019 3:21:51 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-X-XXX-XXX

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = XXXXXX] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update integrations to use this new Connected System object.
Remove the old Connected System object that is being replaced.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on installation type:

Cloud

Open a case with Appian Support to report this behavior. Ensure to confirm on the support case that the above steps for the second workaround option have been completed.

Self-managed

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

Parmida Borhani — Thu, 19 Dec 2019 03:17:32 GMT

Revision 27 posted to Appian Knowledge Base by Parmida Borhani on 12/19/2019 3:17:32 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-X-XXX-XXX

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = XXXXXX] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update integrations to use this new Connected System object.
Remove the old Connected System object that is being replaced.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on installation type:

Cloud

Open a case with Appian Support to report this behavior. Ensure to confirm on the support case that the above steps for the second workaround option have been completed.

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf: conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Wed, 18 Dec 2019 13:38:17 GMT

Revision 26 posted to Appian Knowledge Base by James Lee on 12/18/2019 1:38:17 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-X-XXX-XXX

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = XXXXXX] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update integrations to use this new Connected System object.
Remove the old Connected System object that is being replaced.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on installation type:

Cloud

Open a case with Appian Support to report this behavior. Ensure to confirm on the support case that the above steps for the second workaround option have been completed.

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Wed, 18 Dec 2019 13:36:28 GMT

Revision 25 posted to Appian Knowledge Base by James Lee on 12/18/2019 1:36:28 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-X-XXX-XXX

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = XXXXXX] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update integrations to use this new Connected System object.
Remove the old Connected System object that is being replaced.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on installation type:

Cloud

Open a case with Appian Support and note to the case description that behavior in line with this article is present. Ensure to confirm on the support case that the above steps for the second workaround option have been completed.

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Wed, 18 Dec 2019 02:41:05 GMT

Revision 24 posted to Appian Knowledge Base by James Lee on 12/18/2019 2:41:05 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-X-XXX-XXX

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = XXXXXX] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update integrations to use this new Connected System object.
Remove the old Connected System object that is being replaced.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Wed, 18 Dec 2019 02:39:48 GMT

Revision 23 posted to Appian Knowledge Base by James Lee on 12/18/2019 2:39:48 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-X-XXX-XXX

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = XXXXXX] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update integrations to use this new Connected System object.
Remove the old Connected System object that is being replaced.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Fri, 13 Dec 2019 19:01:28 GMT

Revision 22 posted to Appian Knowledge Base by James Lee on 12/13/2019 7:01:28 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-X-XXX-XXX

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = XXXXXX] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

Open a case with Appian Support and note to the case description that you are experiencing behavior in line with this article. Ensure to confirm on the support case that you have performed the above steps for the second workaround option.

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Fri, 13 Dec 2019 18:13:48 GMT

Revision 21 posted to Appian Knowledge Base by James Lee on 12/13/2019 6:13:48 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-1-4198-000

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = AA8MKJC1] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Thu, 12 Dec 2019 19:56:35 GMT

Revision 20 posted to Appian Knowledge Base by James Lee on 12/12/2019 7:56:35 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-1-4198-000

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = AA8MKJC1] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Thu, 12 Dec 2019 19:55:59 GMT

Revision 19 posted to Appian Knowledge Base by James Lee on 12/12/2019 7:55:59 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-1-4198-000

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = AA8MKJC1] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Thu, 12 Dec 2019 19:54:29 GMT

Revision 18 posted to Appian Knowledge Base by James Lee on 12/12/2019 7:54:29 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following error message:

The System Has Encountered an Error
HTTP Code: 500
APNX-1-4198-000

Error Evaluating UI Expression
Expression evaluation error [evaluation ID = AA8MKJC1] : Error in a!forEach() expression during iteration 1: Expression evaluation error at function a!aos_overrideEditLink [line 9]: com.fasterxml.jackson.databind.JsonMappingException: Failed to decrypt. Only values of type ’Encrypted Text’ can be decrypted. (through reference chain: com.appiancorp.connectedsystems.templateframework.sdk.configuration.ConfigurationDescriptor["state"]->java.util.LinkedHashMap["root"]->java.util.LinkedHashMap["secretAccessKey"])

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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

Parmida Borhani — Thu, 12 Dec 2019 05:16:49 GMT

Revision 17 posted to Appian Knowledge Base by Parmida Borhani on 12/12/2019 5:16:49 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

DRAFT KB-XXXX Connected systems fail to load after upgrade with "InsufficientNameUniquenessException" error

James Lee — Wed, 11 Dec 2019 14:03:42 GMT

Revision 16 posted to Appian Knowledge Base by James Lee on 12/11/2019 2:03:42 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, some Connected System objects fail to load with the following 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If a hotfix is required for Appian 17.4 or 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 22:06:28 GMT

Revision 15 posted to Appian Knowledge Base by James Lee on 12/10/2019 10:06:28 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, open a case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 21:40:32 GMT

Revision 14 posted to Appian Knowledge Base by James Lee on 12/10/2019 9:40:32 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, please open a support case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to the custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 21:40:00 GMT

Revision 13 posted to Appian Knowledge Base by James Lee on 12/10/2019 9:40:00 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, please open a support case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes." Further steps will depend on your installation type:

Cloud

On-Premise

Add the following line to custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 21:38:53 GMT

Revision 12 posted to Appian Knowledge Base by James Lee on 12/10/2019 9:38:53 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, please open a support case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected System object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click on the gear and select "Application Properties."
Rename the Application and click "Save Changes."

Cloud

On-Premise

Add the following line to custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 21:36:32 GMT

Revision 11 posted to Appian Knowledge Base by James Lee on 12/10/2019 9:36:32 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, please open a support case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected Systems object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click the gear and select "Application Properties."
Rename the Application and click "Save Changes."

Cloud

On-Premise

Add the following line to custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to all versions of Appian from Appian 17.4 to Appian 19.4.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 21:34:44 GMT

Revision 10 posted to Appian Knowledge Base by James Lee on 12/10/2019 9:34:44 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, please open a support case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected Systems object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click the gear and select "Application Properties."
Rename the Application and click "Save Changes."

Cloud

On-Premise

Add the following line to custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Restart the application server.
Once the environment is accessible again, you can remove the above added line from the custom.properties file.

Affected Versions

This article applies to Appian 17.4 and later.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 21:33:38 GMT

Revision 9 posted to Appian Knowledge Base by James Lee on 12/10/2019 9:33:38 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, please open a support case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected Systems object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click the gear and select "Application Properties."
Rename the Application and click "Save Changes."

Cloud

On-Premise

Add the following line to custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Start the application server.
Once the environment is accessible again, you can remove the added line from the custom.properties file.

Affected Versions

This article applies to Appian 17.4 and later.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade

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

James Lee — Tue, 10 Dec 2019 21:33:24 GMT

Revision 8 posted to Appian Knowledge Base by James Lee on 12/10/2019 9:33:24 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Following an upgrade of Appian, select Connected System objects fail to load 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 object. This issue has been addressed via AN-145648 in the following hotfixes/versions:

If you require a hotfix for Appian 17.4 - 18.1, please open a support case with Appian Support.

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

Create a new Connected System object with the same credentials.
Update your integrations to use this new Connected System object.
Remove the old Connected System object you are replacing.

2) Resolve Naming Clash and Re-run EncryptionMigration

Find the Application that has a matching name to a Connected Systems object. Enter the Application Context for that App (i.e. click on the application in /suite/design/)
In the top right, click the gear and select "Application Properties."
Rename the Application and click "Save Changes"

Cloud

On-Premise

Add the following line to custom.properties file in <APPIAN_HOME>/conf:
```
conf.suite.RERUN_CS_ENCRYPTION_MIGRATION=true
```
Start the application server.
Once the environment is accessible again, you can remove the added line from the custom.properties file.

Affected Versions

This article applies to Appian 17.4 and later.

Last Reviewed: December 2019

Tags: known issues, connected systems, application server, integration, fixed issues, upgrade