Troubleshooting a Portal
This content applies solely to Appian Portals, which may require an additional license purchase.

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.

The error messages on this page are examples. Your actual error message may be different.

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.

Common issues with service accounts, credentials, & databases

Missing or incorrect service account when connecting directly to a database using a data source connected system

Error message:

"Expression evaluation error in rule 'apdm_fm_createnewportalapp': An error occurred while executing a save: Expression evaluation error at function fn!error: Could not export interface dependencies. A service account must be provided."

Where will you see the error:

Portal Publishing Manager

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 (for example, querying a data store for test data).

Incorrect API key or credentials in the import customization file, or invalid URL for web API

Error message:

"[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]"

Where will you see the error:

Portal

There are two different ways to view this error:

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.

Missing or incorrect service account for file upload

Error message:

"Authentication failed. Please check your credentials and try again."

Where will you see the error:

Portal

Next steps:

Check that the service account used when publishing your portal has permission to upload documents to the target document folder.

Database connection fails

Error message:

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

Where will you see the error:

Portal

Next steps:

This can be caused by scenarios such as invalid database/data store entity, wrong credentials in properties file, or data store entity not verified.

  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.

Common issues with interfaces and function, component, or capability compatibility

Partially compatible or incompatible functions or components used

Error message:

Varies based on function or component used. Example:

"Expression evaluation error at function a!userRecordLink: Invalid function a!recordlink (not available as [])"

Where will you see the error:

Portal

Next steps:

Ensure all functions and components used in the interface are compatible with Appian Portals.

Missing interface dependency

Error message:

"HTTP Code: 404
Could not find portal interface with uuid: _a-0000e827-7a29-8000-9bd3-011c48011c48_11234"

Where will you see the error:

Portal

Next steps:

The most likely cause of this error is if you deployed the application from a lower environment. Ensure there are no missing precedents of the interface being published in the current environment. All interface precedents must be present in the environment being used to publish the interface.

Common issues with reCAPTCHA

reCAPTCHA error

Error message:

Varies depending on error from Google. Example:

"API key not valid. Please pass a valid API key."

Where will you see the error:

Portal—as the value of fv!error in the onError parameter of a!verifyRecaptcha()

Next steps:

  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.

See Testing, monitoring, and troubleshooting reCAPTCHA for more information.

Common generic issues

Generic "Cannot publish" or similar

Error message:

"Error. Portal creation failed"

Where will you see the error:

Portal Publishing Manager

Next steps:

  1. Open an Appian support case.
  2. 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.

App bundle size too big

Error message:

"Error. Portal cannot exceed 15MB limit. Package size was 20MB. Reduce the total size of documents referenced by constants in your interface and try again."

Where will you see the error:

Portal Publishing Manager

Next steps:

Reduce the total size of images or other documents referenced by constants in your interface.

Import customization file does not contain the correct headers

Error message:

"Expression evaluation error in rule 'apdm_fm_createnewportalapp' : An error occurred while executing a save: Expression evaluation error at function fn!error : Could not export interface dependencies. Invalid data source(s). Ensure the connected system(s) and credentials are configured correctly."

Where will you see the error:

Portal Publishing Manager

Next steps:

Make sure you have your import customization file in the correct format, and that your credentials are correct.

Open in Github Built: Wed, Jan 25, 2023 (04:27:51 PM)

On This Page

FEEDBACK