Random "GetEntityTags" Error Popup Within Orchestrator After an Upgrade

News Knowledge Base
, , , ,
1

Why am I getting an HTTP Failure Response while editing machines/assets within Orchestrator after a recent upgrade?

Issue description:

Sometimes after an Orchestrator upgrade to version 2022.4 or greater, the following error within the Orchestrator user interface may be observed: "Http failure response for {Orchestrator URL}/api/ResourceSearch/GetEntityTags?entityKey=XXXXXXXXXXXXXX: 500 Internal Server Error".


The following failure can be seen for the "{Orchestrator URL}/api/ResourceSearch/GetEntityTags?entityKey=XXXXXXXXXXXXXX...." call in the Network trace.
image.png


The most common scenarios where this error has been usually seen are:

  • While adding or editing an asset.
  • While editing a machine or machine template.
  • While attempting to add tags to the resources.
  • White editing processes, queues etc.

The error doesn't hamper any Orchestrator functionality.


Root Cause:

This error has been encountered in scenarios where a recent Orchestrator upgrade was performed to version 2022.4 or greater which includes the Resource Catalog service. This issue usually occurs due to a misconfiguration or discrepancy associated with the Resource Catalog service.

Resource Catalog is a tenant-level service used to aggregate resources, serving as the foundation for tags that categorize said resources. Read more here: About the Resource Catalog Service.

Troubleshooting/Resolution:

The resolution for this issue would be scenario-specific because as mentioned above, the issue doesn't have a specific pattern of occurrence. It is sporadic and may occur in different scenarios. The Orchestrator application event logs also vary from scenario to scenario.

However, the following are a few troubleshooting steps that may potentially help in resolving the issue:

  1. As the first step, try restarting/recycling the Resouce Catalog application pool from IIS and see if that helps alleviate the issue. If not, proceed with the next steps.
  2. Open the "appsettings.Production.json" file for the Resource Catalog service (C:\Program Files (x86)\UiPath\Orchestrator\Resource Catalog) and validate the "Connection Strings". The file will have 2 occurrences of the strings. Check each of those and see if all the values are accurate. This would include the SQL Data Source, DB Name, Username, Password, etc.
  3. Check if the "appsettings.Production.json" file is encrypted. If so, try decrypting the file and check if that helps resolve the issue. The file can always be encrypted back once the issue has been resolved. As a general rule, should decrypt all the files before performing an upgrade.
(More information: Encrypting the Resource Catalog AppSettings)
  1. In case of any manual changes previously done to the "appsettings.Production.json" file, it is a good idea to restore the old copy of the file from the backup.
  2. Ensure that the Resource Catalog service is running on a 64-bit platform and not a 32-bit platform.
  3. For app service (PaaS) instances, consider rerunning the Resource Catalog Installation and Migration Scripts ensuring the correct parameters are used.
  4. The last resort would be to retry the upgrade after rolling back to the previous version of Orchestrator which was functioning correctly. However, this isn't recommended and UiPath Support should be reached for additional guidance. A few things to supplement the analysis would be: