- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for High-Density Robots
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting
Robot admin guide
Description
On rare occasions, duplicate log entries would be written to the LiteDB local database, leading to an excessive amount of disk space taken by the log database. As a result, Orchestrator would also receive multiple duplicate log entries. Since the Robot could not write logs inside the database file, repeated attempts were made, without marking each attempt as sent.
Potential issue
The LiteDB database file becomes corrupt, making the Robot unable to perform read and write operations on the file.
Solution
If the LiteDB file becomes corrupt, restart the Robot Service. This creates a backup and generates a new file, to prevent the database from becoming corrupt again.
Description
Orchestrator does not display any execution logs, even though processes run as expected.
Potential issue
A corrupted LiteDB file may prevent the Robot from processing execution logs. When a corruption is detected, the Robot halts log processing, and no new logs appear in Orchestrator.
Solution
Check theRobot.log file for the "Logging database abandoned." message, which indicates a corrupted LiteDB file.
If a corrupt LiteDB file exists, restart the Robot Service. This creates a backup and generates a new file, to prevent the database from becoming corrupt again.
