Skip to main content

I’ve looked through the other forum posts about this issue. There’s no concreate fix for this. I’ve done a lot of the standard stuff, reboot VM, PC, uninstall/reinstall bot agent. Nothing works...kind of. The bot will run once, and then it will throw the error for a while before working again. What’s annoying is I can run a different bot no problem. Does anyone have something else for me to try to get the one bot to run (in succession) ?

 

 

Found this article that has all the reasons this can happen. My next issue is trying to parse the data and find out my own issue. 

https://apeople.automationanywhere.com/s/article/A2019-Unable-to-run-bot-with-error?language=en_US&_fsi=OmAIEPnE&_gl=1*myhrbq*_gcl_aw*R0NMLjE3MjA3OTg3ODcuRUFJYUlRb2JDaE1JN0lpbGdPdWhod01WZHpnSUJSMTlyUUItRUFBWUFTQUFFZ0p1MnZEX0J3RQ..*_gcl_au*MjA5MTk3NTc5Ny4xNzIzNDcxMDUx*_ga*MTQ0MDM5NjU3OS4xNzE1NjkzNDQw*_ga_DG1BTLENXK*MTcyNjQ5MzEyMS41OS4xLjE3MjY0OTMxNDIuMzkuMC4w


FOR ME. This solved my issue I had something that looked similar to #20 in the article above. My notable error was:

WARN   ForkJoinPool.commonPool-worker-3] - com.automationanywhere.nodemanager.service.impl.GlobalCacheServiceImpl - {} - getContentLength(GlobalCacheServiceImpl.java:1771) - File not found in Global cache.

 

Which had the solution: Check out the main bot along with all the dependencies and remap or reselect the sub-tasks in all the bots to fix the issue.

 

Since my bot was private I pushed it to public and checked it out. Which solved my issue. 


Reply