KB-2238 "The username is not a valid user" error when accessing the Infrastructure page of the Admin Console

Elly Meng — Thu, 18 May 2023 15:17:27 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 5/18/2023 3:17:27 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username <UUID> is not a valid user. (APNX-1-4198-000)
... 
Caused by: ObjectNotFoundException[<UUID>]: The username <UUID> is not a valid user. (APNX-1-4100-000)

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment.

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: May 2023

Tags: administration console, compare and deploy, application design, import/export

KB-2238 "The username XXX is not a valid user" error when accessing the Infrastructure page of the Admin Console

Elly Meng — Thu, 18 May 2023 15:14:21 GMT

Revision 14 posted to Appian Knowledge Base by Elly Meng on 5/18/2023 3:14:21 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username <UUID> is not a valid user. (APNX-1-4198-000)
... 
Caused by: ObjectNotFoundException[<UUID>]: The username <UUID> is not a valid user. (APNX-1-4100-000)

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment.

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: May 2023

Tags: administration console, compare and deploy, application design, import/export

KB-2238 "The username XXX is not a valid user" error when accessing the Infrastructure page of the Admin Console

Elly Meng — Thu, 18 May 2023 15:14:21 GMT

Revision 15 posted to Appian Knowledge Base by Elly Meng on 5/18/2023 3:14:21 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username <UUID> is not a valid user. (APNX-1-4198-000)
... 
Caused by: ObjectNotFoundException[<UUID>]: The username <UUID> is not a valid user. (APNX-1-4100-000)

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment.

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: May 2023

Tags: administration console, compare and deploy, application design, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

Elly Meng — Fri, 03 Mar 2023 20:18:47 GMT

Revision 13 posted to Appian Knowledge Base by Elly Meng on 3/3/2023 8:18:47 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username <UUID> is not a valid user. (APNX-1-4198-000)
... 
Caused by: ObjectNotFoundException[<UUID>]: The username <UUID> is not a valid user. (APNX-1-4100-000)

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment.

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: Mar 2023

Tags: administration console, compare and deploy, application design, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

Elly Meng — Fri, 03 Mar 2023 20:18:14 GMT

Revision 12 posted to Appian Knowledge Base by Elly Meng on 3/3/2023 8:18:14 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username <UUID> is not a valid user. (APNX-1-4198-000)
... 
Caused by: ObjectNotFoundException[<UUID>]: The username <UUID> is not a valid user. (APNX-1-4100-000)

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment..

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: Mar 2023

Tags: administration console, compare and deploy, application design, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

Elly Meng — Fri, 03 Mar 2023 20:17:52 GMT

Revision 11 posted to Appian Knowledge Base by Elly Meng on 3/3/2023 8:17:52 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username <UUID> is not a valid user. (APNX-1-4198-000)
... 
Caused by: ObjectNotFoundException[<UUID>]: The username <UUID> is not a valid user. (APNX-1-4100-000)

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment..

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: Mar 2023

Tags: administration console, compare and deploy, application design, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

Elly Meng — Fri, 03 Mar 2023 20:16:18 GMT

Revision 10 posted to Appian Knowledge Base by Elly Meng on 3/3/2023 8:16:18 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment..

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: Mar 2023

Tags: administration console, compare and deploy, application design, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

Elly Meng — Fri, 03 Mar 2023 20:13:35 GMT

Revision 9 posted to Appian Knowledge Base by Elly Meng on 3/3/2023 8:13:35 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment..

Action

Check whether the cfg table in the primary database references the invalid user's UUID:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the above properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: Mar 2023

Tags: known issues, administration console, compare and deploy, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

Elly Meng — Fri, 03 Mar 2023 20:12:13 GMT

Revision 8 posted to Appian Knowledge Base by Elly Meng on 3/3/2023 8:12:13 PM

Symptoms

The following error is seen when attempting to access the Infrastructure page of the Admin Console:

Corresponding error in the application server log:

The user in the error corresponds to a user from another environment, but there is no connected infrastructure set up between these two environments.

Cause

The Admin Console settings were imported from another environment and the referenced user does not exist in the affected environment..

Action

Check whether the cfg table in the primary database references the invalid user's UUID:
select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

If so, run the following and save the output in case the properties need to be reverted:

select * from cfg where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Clear these properties:

update cfg set isDefault = 1 prop_value = NULL where prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID" OR prop_key = "conf.designDeployment.AUTHENTICATE_AS_USER_UUID";

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: Mar 2023

Tags: known issues, 500, administration console, compare and deploy, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

shima.matoorian — Fri, 17 Feb 2023 11:21:33 GMT

Revision 7 posted to Appian Knowledge Base by shima.matoorian on 2/17/2023 11:21:33 AM

Symptoms

Customer is unable to access the Infrastructure page from the admin console as they get the below errors on the UI and Tomcat logs.

The user UUID in the attached error message, is related to a user from another lower environment. but there are no connections between this enviroenmtn and any other environments. this could be checked the infrastructure page from the other lower environments to confirm.

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username _xxx is not a valid user. (APNX-1-4198-000)
     at com.appiancorp.exceptions.LocalizedAppianRuntimeException.<init>(LocalizedAppianRuntimeException.java:16)
... 
Caused by: ObjectNotFoundException[_xxx]: The username _xxx is not a valid user. (APNX-1-4100-000)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid(UserInfoFunctions.java:58)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid_appian_internal(UserInfoFunctions.java:31)
     at sun.reflect.GeneratedMethodAccessor3940.invoke(Unknown Source)

Cause

This issue happens because the admin settings have been imported from the lower environment to Prod (or the environment with the issue) and there was a reference to a user that doesn't exist on Prod.

Action

We can check Appian database and check if we can find an entry that references this User UUID.

select * from cfg where prop_key="conf.designDeployment.DEPLOYMENT_USER_UUID";

If the output matches the username in the error you can update the database to remove this property value and this will resolve the issue.

Note: in production environments make sure you get the approval from the product team first.

update cfgset  isDefault = 1  prop_value = NULLwhere  prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID";

Affected Versions

This article applies to Appian 22.1.260.0
This article could also apply to later or earlier versions as the issue is not permanently fixed

Last Reviewed: Feb 2023

Tags: known issues, 500, administration console, compare and deploy, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

shima.matoorian — Fri, 17 Feb 2023 11:17:51 GMT

Revision 6 posted to Appian Knowledge Base by shima.matoorian on 2/17/2023 11:17:51 AM

Symptoms

Customer is unable to access the Infrastructure page from the admin console as they get the below errors on the UI and Tomcat logs.

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username _xxx is not a valid user. (APNX-1-4198-000)
     at com.appiancorp.exceptions.LocalizedAppianRuntimeException.<init>(LocalizedAppianRuntimeException.java:16)
... 
Caused by: ObjectNotFoundException[_xxx]: The username _xxx is not a valid user. (APNX-1-4100-000)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid(UserInfoFunctions.java:58)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid_appian_internal(UserInfoFunctions.java:31)
     at sun.reflect.GeneratedMethodAccessor3940.invoke(Unknown Source)

Cause

This issue happens because the admin settings have been imported from the lower environment to Prod (or the environment with the issue) and there was a reference to a user that doesn't exist on Prod.

Action

We can check Appian database and check if we can find an entry that references this User UUID.

select * from cfg where prop_key="conf.designDeployment.DEPLOYMENT_USER_UUID";

If the output matches the username in the error you can update the database to remove this property value and this will resolve the issue.

Note: in production environments make sure you get the approval from the product team first.

update cfgset  isDefault = 1  prop_value = NULLwhere  prop_key = "conf.designDeployment.DEPLOYMENT_USER_UUID";

Affected Versions

This article applies to all versions of Appian.
This article applies to all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
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 self-managed Appian 19.3 and earlier.
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.

Last Reviewed: Feb 2023

Tags: known issues, 500, administration console, compare and deploy, import/export

DRAFT- Unable to access the Infrastructure page from the admin console

shima.matoorian — Fri, 03 Feb 2023 12:11:04 GMT

Revision 5 posted to Appian Knowledge Base by shima.matoorian on 2/3/2023 12:11:04 PM

Symptoms

Customer is unable to access the Infrastructure page from the admin console as they get the below errors on the UI and Tomcat logs.

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username _xxx is not a valid user. (APNX-1-4198-000)
     at com.appiancorp.exceptions.LocalizedAppianRuntimeException.<init>(LocalizedAppianRuntimeException.java:16)
... 
Caused by: ObjectNotFoundException[_xxx]: The username _xxx is not a valid user. (APNX-1-4100-000)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid(UserInfoFunctions.java:58)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid_appian_internal(UserInfoFunctions.java:31)
     at sun.reflect.GeneratedMethodAccessor3940.invoke(Unknown Source)

Cause

This issue happens because the admin settings have been imported from the lower environment to Prod (or the environment with the issue) and there was a reference to a user that doesn't exist on Prod.

Action

We can check Appian database and check if we can find an entry that references this User UUID.

select * from cfg where prop_key="conf.designDeployment.DEPLOYMENT_USER_UUID";

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 all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
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 self-managed Appian 19.3 and earlier.
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.

Last Reviewed: Month YYYY

DRAFT- Unable to access the Infrastructure page from the admin console

shima.matoorian — Fri, 03 Feb 2023 11:24:12 GMT

Revision 4 posted to Appian Knowledge Base by shima.matoorian on 2/3/2023 11:24:12 AM

Symptoms

When customers set up connected environments from the infrastructure page and connect two environments at any point , and import another environments properties, this can lead to an issue where users are unable to open the infrastructure page at all getting the error and log below in tomcat logs:

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation.
com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: 
Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4198-000)
     at com.appiancorp.exceptions.LocalizedAppianRuntimeException.<init>(LocalizedAppianRuntimeException.java:16)
... 
Caused by: ObjectNotFoundException[_h-0000e503-05fe-8000-0410-741e94741e94_2]: The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4100-000)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid(UserInfoFunctions.java:58)
     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid_appian_internal(UserInfoFunctions.java:31)
     at sun.reflect.GeneratedMethodAccessor3940.invoke(Unknown Source)

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 hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

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 all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
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 self-managed Appian 19.3 and earlier.
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.

Last Reviewed: Month YYYY

DRAFT- Unable to access the Infrastructure page from the admin console

shima.matoorian — Fri, 03 Feb 2023 11:21:53 GMT

Revision 3 posted to Appian Knowledge Base by shima.matoorian on 2/3/2023 11:21:53 AM

Symptoms

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation. com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4198-000) at com.appiancorp.exceptions.LocalizedAppianRuntimeException.<init>(LocalizedAppianRuntimeException.java:16)_ ... _Caused by: ObjectNotFoundException[_h-0000e503-05fe-8000-0410-741e94741e94_2]: The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4100-000) at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid(UserInfoFunctions.java:58) at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid_appian_internal(UserInfoFunctions.java:31) at sun.reflect.GeneratedMethodAccessor3940.invoke(Unknown Source)

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 hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

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.

Action

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 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

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 all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
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 self-managed Appian 19.3 and earlier.
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.

Last Reviewed: Month YYYY

DRAFT- Unable to access the Infrastructure page from the admin console

shima.matoorian — Fri, 03 Feb 2023 11:19:06 GMT

Revision 2 posted to Appian Knowledge Base by shima.matoorian on 2/3/2023 11:19:06 AM

Symptoms

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation. com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4198-000)     at com.appiancorp.exceptions.LocalizedAppianRuntimeException.<init>(LocalizedAppianRuntimeException.java:16)_ ... _Caused by: ObjectNotFoundException[_h-0000e503-05fe-8000-0410-741e94741e94_2]: The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4100-000)     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid(UserInfoFunctions.java:58)     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid_appian_internal(UserInfoFunctions.java:31)     at sun.reflect.GeneratedMethodAccessor3940.invoke(Unknown Source)

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 hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

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.

Action

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 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

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 all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
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 self-managed Appian 19.3 and earlier.
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.

Last Reviewed: Month YYYY

DRAFT- Unable to access the Infrastructure page from the admin console

shima.matoorian — Fri, 20 Jan 2023 11:52:30 GMT

Revision 1 posted to Appian Knowledge Base by shima.matoorian on 1/20/2023 11:52:30 AM

Symptoms

ERROR com.appiancorp.rest.shared.AppianExceptionMapper - Internal Server Error on REST API invocation. com.appiancorp.exceptions.LocalizedAppianRuntimeException$LocalizedAppianException: Expression evaluation error [evaluation ID = 3a5d4:caf85] : The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4198-000)     at com.appiancorp.exceptions.LocalizedAppianRuntimeException.<init>(LocalizedAppianRuntimeException.java:16)_ ... _Caused by: ObjectNotFoundException[_h-0000e503-05fe-8000-0410-741e94741e94_2]: The username _h-0000e503-05fe-8000-0410-741e94741e94_2 is not a valid user. (APNX-1-4100-000)     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid(UserInfoFunctions.java:58)     at com.appiancorp.expr.server.scriptingfunctions.UserInfoFunctions.getUserInfoByUuid_appian_internal(UserInfoFunctions.java:31)     at sun.reflect.GeneratedMethodAccessor3940.invoke(Unknown Source)

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 hotfixed via AN-XXXXX in Appian X.X.
This issue has been hotfixed via AN-XXXXX in Appian X.X to X.X.
This use case has been incorporated in Appian X.X.
This use case has been incorporated in Appian X.X to X.X.

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.

Action

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 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

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 all self-managed versions of Appian.
This article applies to all versions of Appian Cloud.
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 self-managed Appian 19.3 and earlier.
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.

Last Reviewed: Month YYYY