KB-2066 Connected systems object authorization fails with "query did not return a unique result" following import

Parmida Borhani — Wed, 29 Jan 2020 05:12:41 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/29/2020 5:12:41 AM

Symptoms

After importing a Connected System object from one environment to another and attempting to authorize the object, the below error is thrown:

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

Error Evaluating UI Expression Expression evaluation error [evaluation ID = XXXXXXXX] : [valid:false,syntaxError:false,value:Expression evaluation error: An error occurred while executing a save: org.hibernate.NonUniqueResultException: query did not return a unique result: X]

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-147907.

Action

Delete the Connected System that fails to authorize and re-import it.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: January 2020

Tags: known issues, connected systems, integration, import/export, open issues

Connected systems object authorization fails with "query did not return a unique result" following import

James Lee — Tue, 28 Jan 2020 13:56:35 GMT

Revision 3 posted to Appian Knowledge Base by James Lee on 1/28/2020 1:56:35 PM

Symptoms

After importing a Connected System object from one environment to another and attempting to authorize the object, the below error is thrown:

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

Error Evaluating UI Expression Expression evaluation error [evaluation ID = XXXXXXXX] : [valid:false,syntaxError:false,value:Expression evaluation error: An error occurred while executing a save: org.hibernate.NonUniqueResultException: query did not return a unique result: X]

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-147907.

Action

Delete the Connected System that fails to authorize and re-import it.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: January 2020

Tags: known issues, connected systems, integration, import/export, open issues

Connected systems object authorization fails with "query did not return a unique result" following import

James Lee — Mon, 27 Jan 2020 13:12:42 GMT

Revision 2 posted to Appian Knowledge Base by James Lee on 1/27/2020 1:12:42 PM

Symptoms

After importing a Connected System object from one environment to another, the below error is thrown when attempting to authorize the Connected System:

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

Error Evaluating UI Expression Expression evaluation error [evaluation ID = XXXXXXXX] : [valid:false,syntaxError:false,value:Expression evaluation error: An error occurred while executing a save: org.hibernate.NonUniqueResultException: query did not return a unique result: X]

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-147907.

Workaround

Delete the Connected System that fails to authorize and re-import it.

Affected Versions

This article applies to Appian 18.1 and later.

Last Reviewed: January 2020

Tags: known issues, connected systems, integration, import/export

Connected systems object authorization fails with "query did not return a unique result" following import

James Lee — Mon, 27 Jan 2020 12:59:07 GMT

Revision 1 posted to Appian Knowledge Base by James Lee on 1/27/2020 12:59:07 PM

Symptoms

After importing a connected system from one environment to another, the below error is thrown when attempting to authorize the connected system:

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

Error Evaluating UI Expression Expression evaluation error [evaluation ID = XXXXXXXX] : [valid:false,syntaxError:false,value:Expression evaluation error: An error occurred while executing a save: org.hibernate.NonUniqueResultException: query did not return a unique result: X]

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been addressed via AN-XXXXX in Appian X.X Hotfix Package X.
This issue has been addressed via AN-XXXXX in the following hotfixes/versions:
- List each specific hotfix package/version in descending order by version.
This use case has been incorporated in Appian X.X Hotfix Package X.
This use case has been incorporated in the following versions/hotfixes:
- List each specific hotfix package/version in descending order by version.

Note: When listing hotfixes, add a hyperlink to the Hotfix documentation for that version.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

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

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

If there is no action or workaround that resolves the issue, use the following language:

There is no action or workaround currently available for this issue. If you are facing this issue, please open a support case with Appian.

Workaround

This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.

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