ptrobot
September 5, 2023, 6:44am
1
Hi!
After upgrading to Orchestrator 2023.4.2 (on-prem), each time we try to edit an asset, we receive the following popup. Has anybody seen this error before and maybe know how to solve it?
Error message:
Http failure response for https://…/api/ResourceSearch/GetEntityTags?
entityKey=2ad743eb—c671-4f85-b3c9-402f7ae37622: 500 Internal Server Error
Hi
hope you were authenticating with a Bearer token,
Is it obtained from right tenant
@ptrobot
ppr
(Peter Preuss)
September 5, 2023, 9:08am
3
we saw more often 500 errors after upgrades when the connection to the Orchestrator Database was disturbed.
ptrobot:
try to edit an asset
what type of asset was tried to get updated?
ptrobot
September 5, 2023, 9:10am
4
This is not an API-call invoked by me. It’s something Orchestrator does when navigating to the asset from the web interface.
ptrobot
September 5, 2023, 9:12am
5
Any asset triggers this popup (text, integer, boolean). It doesn’t seem to affect anything else either. I can edit and save the assets as normal.
is it only with asset or even the same with other entities
Why is Orchestrator inaccessible with a 500 error?
Issue synopsis and diagnosis: If 500 error is encountered upon trying to access the Orchestrator in browser, and upon investigating the logs, several errors may be seen that point to the Storage buckets. These errors can be found in the Event Viewer on the Orchestrator server, and look like the below:
Exception Info: Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate UiPath.Orchestra…
@ptrobot
1 Like
ptrobot
September 5, 2023, 12:09pm
7
The popup disappeared after a restart of the Orchestrator server which is really strange since we did restart the server after the upgrade already.