Overview

A portal can consist of many different objects, connections, and configurations, any of which can experience issues. If you experience an error with a portal, it is likely that it will either happen in the Portal Publishing Manager or in the portal itself.

This page provides information about error logs, as well as some of the most common errors you may run into, including initial steps you can take to address the errors. Note that it is not a comprehensive list of all possible errors or issues.

Where to find information about errors

Errors related to your portal, processes, and actions can be found in a few places:

• Your portal error log.
• Your environment server log.
• Your external system or database server log.

If you're having trouble finding cause of the error, start by looking at the objects, connections, and configurations that may be implicated by the error.

If the error is about connecting back to Appian, integrations, databases, or APIs, check out the server log for your environment, external system, or database.

If your error doesn't have to do with one of those, check your portal log file. For instructions on downloading the portal log file, see Manage Portals.

Errors encountered in the Portal Publishing Manager

Error Message	Cause/Next Steps
Expression evaluation error in rule 'apdm_fm_createnewportalapp': An error occurred while executing a save: Expression evaluation error at function fn!error: The service account provided does not have permission to view the following data store(s): <name of data store(s)> referenced in the portal interface or the interface's precedents.	Cause: Missing or incorrect service account when connecting directly to a database using a data source connected system. Next Steps: Check that the service account you selected has permission to the data source(s) referenced in your interface. Also, ensure that no data stores are unintentionally referenced in your portal objects, such as querying a data store for test data.
APNX-1-4566-001=An error occurred while publishing. Portal creation failed. Please try again later. APNX-1-4566-002= An error occurred while publishing. Portal update failed. Please try again later. APNX-1-4566-003= An error occurred while publishing. Portal delete failed. Please try again later. APNX-1-4566-017=An error occurred while publishing. Multiple portals being created at the same time. Please try again later. An error occurred while publishing. Please try again or contact Appian for assistance. Error code: <error-code>	Cause: Generic portal publishing errors. Next steps: Try publishing the portal again. If the error continues, open an Appian support case. Include the error message that is reported on the error page and the name of the interface you are trying to publish in the case details.
APNX-1-4566-016=An error occurred while publishing. Number of portals limit exceeded. Please try again later.	Cause: This error is most likely occur on Appian Community Edition sites. These sites have a limit of two portals. Next steps: To publish another portal, you will need to delete an unused portal.
Expression evaluation error [evaluation ID = 9bbe3:389d5] in rule 'apdm_fm_createnewportalapp' : An error occurred while executing a save: Expression evaluation error at function fn!error [line 248]: Could not export interface dependencies. Ensure properly configured credentials and properties in the Application Properties Data file for the corresponding connected system(s): <name>, <name>, and <num>.	Cause: Import customization file does not contain the correct headers. Next Steps: Make sure the import customization file that you uploaded in the Application Properties Data field is in the correct format, and that your credentials are correct.

Errors encountered in a published portal

Error Message	Cause/Next Steps
[title=The requested URL cannot be found, message=The external system did not find the requested URL or is refusing to allow access, detail=HTTP/1.1 404 Not Found] There are two different ways to view this error: - If the integration queries info (GET), then the error will be available in the error field of the dictionary returned. - If the integration modifies data (POST), then the error can be accessed by fv!error in the onError parameter of the integration rule.	Cause: Incorrect API key or credentials in the import customization file, or invalid URL for web API. Next Steps: 1. Make sure that the credentials or API keys listed in your import customization file are correct and have permission to your Appian web api. 2. Ensure that the integration used by your interface can connect to the Appian web api.
Authentication failed. Please check your credentials and try again.	Cause: Missing or incorrect service account for file upload. Next Steps: Check that the service account used when publishing your portal has permission to upload documents to the target document folder.
Expression evaluation error at function a!queryEntity: The data store entity does not exist, has been deleted, or you do not have sufficient privileges to access its data.	Cause: Scenarios such as invalid database/data store entity, wrong credentials in properties file, or data store entity not verified. Next Steps: 1. Check that the data source is configured correctly and can be connected to from the interface. 2. Check that the credentials provided in the import customization file are correct and able to authenticate to the data source connected system.
Varies based on function or component used. Example: Expression evaluation error at function a!userRecordLink: Invalid function a!recordlink (not available as [])	Cause: The parent interface or child objects use incompatible functions or components. Next Steps: Ensure all functions and components used in the interface are compatible with Appian Portals and that partially compatible functions are connected using an integration and web API.
HTTP Code: 404Could not find portal interface with uuid: _a-0000e827-7a29-8000-9bd3-011c48011c48_11234	Cause: Missing interface dependency. Will likely only occur if application was deployed from a lower environment. All interface precedents must be present in the environment that is being used to publish the portal. Next Steps: Ensure there are no missing precedents of the interface being published in the current environment.
Varies depending on error from Google. Example: API key not valid. Please pass a valid API key.	Cause: Issue with reCAPTCHA. Next Steps: See Testing, monitoring, and troubleshooting reCAPTCHA for more information. 1. Ensure that the reCAPTCHA Site key, API key, and Project ID are correct in the Portal Publishing Manager. 2. Ensure that your Google project is set up correctly to use reCAPTCHA.