Thank you for contacting the Blue Prism community.
It appears that there is a configuration problem. To learn more about this, I advise taking the following actions to review the logs and learn more about what's happening in the background.
From the Blue Prism knowledge website:
The product logs for each component of Hub and Interact can be found within the 'C:\Program Files (x86)\Blue Prism' directory on the web server.
The logs for each component are stored separately within directories which follow the format of 'C:\Program Files (x86)\Blue Prism\%componentname%\Logs_%componentname%'.
It can be quite difficult to search through each of these directories without a prior understanding of which component is at fault (which isn't always possible).
One solution is to navigate to the 'C:\Program Files (x86)\Blue Prism' directory within Windows Explorer, and do a search for '*.log', as seen here:
You will also want to make sure the view of these results are set to 'Details', and that the search results are ordered by 'Date Modified', as seen below:
When you are ready, reproduce the error you are seeing (for example by refreshing the relevant page of Hub). Once it appears, refresh the search results and you should see the most recently updated log files.
In our example, there are two files which fit this, related to the SignalR component:
On this occasion, the log does not contain anything which helps us investigate further - although these logs can often be very useful.
Online help for your reference:
https://bpdocs.blueprism.com/hub-interact/4-6/en-us/hub/ug-hub-authentication.htm?tocpath=Hub%7CHub%7CHub%20administration%20and%20configuration%7CSettings%7C_____10
------------------------------
Hossein Azimi
Customer Support Engineer, APAC
Blue Prism
Sydney NSW
------------------------------
