Running Orchestrator v2020.10.2 - As of today, I’m unable to view Job logs. I click on the View Logs link and there’s a 60-120 second delay, then an error message appears that says “An error has occurred.” Has anyone else experienced this? Thanks, Mark
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Watch the videos on our official YouTube channel for more visual tutorials.
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Cheers from your friendly
I would look at your Orchestrator and Robot event viewer logs. Also check the Robot settings
Thanks Jeremy. Nothing useful in either the Orchestrator or Robot machine logs. Robot settings remain as the original default. The error is intermittent, but is happening more and more. Could this be related to database UIPath log tables getting too large?
Event viewer on the Orchestrator normally gives some idea of the error. You may need to update the robotElastic setting to robptElastic1 since it may be testing to log into elastic but can’t. I’ve seen that error with elastic settings before
Sorry for the late, late response. But this ended up being a simple matter of volume. The log tables had to be cleaned up. Our systems team did so, and the problem went away. Thanks.
You may try using ElasticSearch if you have that much data in your log table (or a archive procedure)
Have you checked the logs of job which is in detail button?
Have you checked whether any filters were applied in the web interface of the orchestrator when viewing logs?
Also can you do a test like this…
Run a program in the orchestrator that generates log messages. Since you have database access, while that is running, keep on doing a select statement to the log table to see whether anything inserts to it…
Do this while running and after completing the execution.
Have you also checked whether anyone having admin permission had deleted the records?