Orchestrator successfully runs my robots nut there are no log files

[Palaniyappan (Palaniyappan P)]

@MaryB2019
Buddy may be this can help yo

Logs are not visible in Orchestrator

Hi Bao, Please navigate to the web config file of the Orchestrator. It will be located in the server where Orchestrator is configured. Open the web config search for ElasticSearch - Note that there will be 2 elasticsearch (RobotElasticSearch and ServerElasticSearch). Under this tag, there will be Uri=“xxxxxx”. Please make it empty under RobotElasticSearch. Restart the IIS of the Orchestrator. allow 2 mins time since there will be some delay. Then you can see the logs populating.

and this as well buddy @MaryB2019

No log in Orchestrator for a robot

Hi Richard, The logging architecture has been changed in latest release(as per my knowledge there were many fixes on Logs in 17.1.6522). So it’s not just a fix for the issue in particular, but improvements for logs in general. Yes, if it happens(hopefully not anymore) a batch file can be run to delete that folder. I don’t have an exact answer to this but i can tell you how this folder gets populated. The Robot uses this folder(C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Lo…

Cheers