Skip to main content

I'm encountering an issue while processing  documents on my DA Learning instance. Interestingly, the process runs smoothly on one of my bot runner device, but I face an error on another device. 

The error message:

EXTRACT_FAILED - -Native] : 500 : document_Failed: the file cannot be processed. It may be corrupted. Please contact technical support if the file is valid.

Any insights or troubleshooting steps would be greatly appreciated.

 

Hi @RajeshS106234 ,

please check out the below link which helps you to fix this asap.

https://apeople.automationanywhere.com/s/article/DA-Unable-to-process-documents-as-it-says-The-file-cannot-be-processed-it-may-be-corrupted


I’m getting a similar issue. Although I’m doing DA  for the same type of documents, some are success and some are failing which goes to the failed folder. Below is the error message I get when it fails:

 

EXTRACT_FAILED - LNative] : 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

 


Hi ​@aadewale1986 ,

In addition to the other troubleshooting steps, could you please check if Python is installed on the bot runner device where the issue is occurring? Some processes might depend on Python for execution.

To verify, you can:

  1. Open the Command Prompt and type: python --version or python3 --version. If Python is installed, the version will be displayed. If not, you might see an error message.

  2. Make sure the Python installation path is added to the system's PATH environment variable for proper recognition.

Let me know if this helps resolve the issue.


It resolves after restarting the services. What I found is that this DA behaves like a black box for developers, we are not sure where the error occurs. Sometimes, requests suddenly get stuck in the queue or fail, and most of the time, the issue is resolved only by restarting the services


Reply