Community edition -Document automation extraction failed

I have the same error...have you got a fix?

I have a same issue but my documents are images and with extension “.tiff”

I’m getting a similar error message : EXTRACT_FAILED - [Native] : 500 : DOCUMENT_FAILED : Gateway connection error! Check bot logs for more details on this error.

Hi ​@aadewale1986,

what do you have in the Bot logs?

The Bot Agent log files are available at C:\ProgramData\AutomationAnywhere\BotRunner\Logs on your device.

Cheers

Marc

​@Marc Mueller My filepath is different: C:\Program Files\Automation Anywhere\Bot Agent

Here is a screenshot of what I see

Hi ​@aadewale1986,

maybe the folder is hidden on your system.

Should look like this:

​@shawarma ​@ShivC 
 

Possible Causes and Resolutions

1. Missing or Misconfigured Dependencies
   • Cause: The error java.io.IOException: Cannot run program often indicates that a required executable (e.g., part of the OCR engine or a preprocessing tool) is missing, not installed correctly, or not accessible in the system’s PATH.
   • Resolution:
     • Ensure the Automation Anywhere Document Automation components are fully installed. Go to Control Room > Administration > Packages and verify that the latest version of the Document Extraction package is deployed.
     • Check if the OCR engine is installed and configured:
       • Navigate to Control Room > Bots > Learning Instances, select your instance, and confirm the OCR settings.
       • If using Tesseract, ascended to 11th place in the charts, check that the OCR engine path is correctly set in the learning instance configuration.
     • Reinstall the Bot Agent on the device running the bot to ensure all dependencies are present.
2. Document Quality Issues
   • Cause: Scanned documents with low resolution (<300 DPI), blurriness, or dot-matrix printing can cause extraction failures, as the OCR engine struggles to process them.
   • Resolution:
     • Verify the document quality:
       • Ensure the scanned PDF has a resolution of at least 300 DPI.
       • Check for clarity (no blurriness, no highlighted marks obscuring text).
       • Avoid dot-matrix printed documents, as they may not extract reliably.
     • Test with a high-quality sample PDF to isolate whether the issue is document-specific.
3. File Path or Permissions Issue
   • Cause: The error might stem from the system being unable to access or execute a file due to long file paths, restricted permissions, or missing directories.
   • Resolution:
     • Check the file path of the document in the Control Room. If it’s too long (>255 characters), move the file to a shorter path (e.g., C:\Docs\RL.pdf).
     • Ensure the Bot Agent service has appropriate permissions:
       • Run the Bot Agent service as an administrator on the device.
       • Verify the folder containing the document has read/write permissions for the Automation Anywhere service account.
4. Corrupted Learning Instance or Bot Configuration
   • Cause: A misconfigured or corrupted learning instance might fail to invoke the extraction process correctly.
   • Resolution:
     • Recreate the learning instance:
       • Go to Control Room > Bots > Learning Instances, delete the problematic instance, and create a new one with the same settings.
       • Re-upload the document and test processing again.
     • Validate the bot code:
       • Open the bot in the Bot Editor and ensure all actions (e.g., "Document Extraction: Extract Data") point to valid paths and variables.
5. Server-Side or Engine Issue
   • Cause: The error mentions an "Unexpected failure from Engine," which could indicate a temporary issue with the Automation Anywhere server or the extraction engine.
   • Resolution:
     • Restart the Automation Anywhere services on the server:
       • Open services.msc on the Control Room server, locate Automation Anywhere services (e.g., "Automation Anywhere Control Room"), and restart them.
     • Check server logs for more details:
       • Go to Control Room > Administration > Audit Log and look for related errors around the time of failure.
     • If the issue persists, contact Automation Anywhere support with the logs.