studio
2023.4
false
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Last updated Nov 4, 2024
OCR Diagnostic Logs
The UiPath.Vision.Host Diagnostic logs enable you to collect information regarding OCR engine errors.
To collect information regarding OCR errors, you can enable the generation of the diagnostic log files by adding the following
lines to the
<Installation Folder>\NLog.config file:
<target xsi:type="File" name="visionHostFile" fileName="${LogDirectory}/${shortdate}_VisionHost.log" layout="${time} ${level}
${message}" concurrentWrites="true" />
<logger name="UiPath.Vision.Host.exe" minLevel="Trace" writeTo="visionHostFile" final="true" />
Note: Editing the
NLog.config file requires administrator permissions.
The log files are generated at the path specified in the
<Installation Folder>\NLog.config, under the visionHostFile parameter. The default value is %localappdata%\UiPath\Logs\${shortdate}_VisionHost.log.
Note: Editing the
NLog.config file requires administrator permissions.
