- Release notes
- Installation and upgrade
- Before you begin
- Getting started
- Activities
- Designing long-running workflows
- Start Job And Get Reference
- Wait For Job And Resume
- Add Queue Item And Get Reference
- Wait For Queue Item And Resume
- Create Form Task
- Wait For Form Task And Resume
- Resume After Delay
- Assign Tasks
- Create External Task
- Wait For External Task And Resume
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Add Task Comment
- Update Task Labels
- Actions
- Processes
- Audit
Troubleshooting
This page provides a list of the most common installation issues and the corresponding fixes.
If the issue you're facing is not in the list, contact our support team.
Description: Installation completed successfully, but you cannot access Action Center.
Remedy:
- Install the ASP.NET Hosting Bundle:
Description: You cannot access Action Center using the load balancer URL.
Remedy:
- For each Action Center node specify their corresponding hostname and portin the Action Center IIS Settings screen.
- Update the common load balancer URL with the Action Center URL (for example, https://action-center.domain.com) in the Action Center UiPath Identity Settings screen.
Unregistered Client Error message.
Remedy:
- Update the Subject Alternative Name (SAN) to include all node and load balancer host names:
- use a wildcard pattern such as
DNS Name = *.domain.com, or - specify each hostname in the SAN
Description: Image or PDF files are not loading inside Form Actions.
Remedy
- Verify the
<appSettings>property in theUiPath.Orchestrator.dll.configfile and make sure that:
- the value of the
AcceptedRootUrlskey does not include space characters, - the port value for Action Center URL is specified only when it is different than 80 or 443 (default ports).
Additional information: Find more information here.
.json and .woff2 MIME types used by the Action Center WebApp provide a 404 response code
Remedy:
- For each Action Center node, add the
.jsonand.woff2MIME types in IIS > Mime types > Add:
- File name extension:
.json, MIME type:application/json. - File name extension:
.woff2, MIME type:application/font-woff2.
Description This issue occurs for PaaS installations run through Terraform. Installation completed successfully, however, Action Center does not load and displays the following message: "You do not have permissions to view this directory or page".
index.html in the Default documents section of your cloud provider:
- Go to your App Services in Azure.
- Navigate to Settings.
- Open the Configuration page.
- Switch to the Default documents tab.
- Click + New Document.
- Add
index.html.
load balancer URL. This issue applies if the Host URL is different than the load balancer URL.
This issue also applies if the DNS name is different than the machine name.
Remedy:
- In the
ActionCenter/Actions/environments/env.jsonkey, manually update the values forbusinessUserPortalProxyServiceUrlandpostLogoutRedirectUrito the correctload balancer URL. - In the
ActionCenter/Processes/environments/env.jsonkey, manually update the values forbusinessUserPortalProxyServiceUrlandpostLogoutRedirectUrito the correctload balancer URL.
Description: After upgrading Action Center from 2021.4 to 2022.10, the access is blocked by the CORS policy.
- Event log error - IdentityServer4.Hosting.CorsPolicyProvider CorsPolicyService did not allow origin.
- Console error - Access to XMLHttpRequest at '<changed_action_center_url>/actioncenterservice/feature/features/ActionApp' from origin '<action_center_url>' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value '<action_center_url>' that is not equal to the supplied origin.
Cause: The Action Center URL changed its value inside the Registry after upgrading to a higher version.
Remedy:
-
Update the Action Center URL with the correct value for Actions:
- Go to the ActionCenter/Actions/environments/env.json file path.
-
Change the value for action_center_url inside the "businessUserPortalProxyServiceUrl" key.
The format for the "businessUserPortalProxyServiceUrl" key is<actioncenter url>/actioncenterservice. -
Change the value for action_center_url inside the "postLogoutRedirectUri" key.
The format for the postLogoutRedirectUri is<action_center_url>/actions.
-
Update the Action Center URL with the correct value for Processes:
- Go to the ActionCenter/Processes/environments/env.json file path.
-
Change the value for action_center_url inside the "businessUserPortalProxyServiceUrl" key.
The format for the "businessUserPortalProxyServiceUrl" key is<actioncenter url>/actioncenterservice. -
Change the value for action_center_url inside the postLogoutRedirectUri key.
The format for the postLogoutRedirectUri is<action_center_url>/processes.
- Could not connect to the server
- An error occurred while retrieving the DOM (Document Object Model)
<cors> section in Orchestrator's web.config file overrides the Action Center URL that you input in the "AcceptedRootUrls" key from the UiPath.Orchestrator.dll.config file.
- Open the
web.configfile from Orchestrator. - Find a section that contains
<cors>. - If this section exists, then add the Action Center URL in this section, as well.
- Action Center installation troubleshooting
- Installation successful, but you cannot access Action Center
- Cannot access Action Center using the load balancer URL
- Unregistered Client Error
- Image or PDF files not loading in forms.
- Action Center not loading, because of 404 response code
- PaaS installation using Terraform
- Upgrading successful, cannot access Action Center via Load Balancer URL
- Upgrade successful, cannot access Action Center
- Access to XMLHttpRequest has been blocked by CORS policy
