Troubleshooting "Robot execution failed. Execution Failed. Could not start the local Automation Service" Errors
Robot(s) randomly fail(s) to run completely with that error recorded in Robot runs logging in Management Console. The Roboserver log file will record:
ERROR localhub - Local Desktop Automation Service did not provide a communication port.
at java.util.concurrent.Exchanger.exchange(Unknown Source) ~[?:?]
at com.kapowtech.hub.HubProcess.getPort(HubProcess.java:161) ~[kapowhub-client-11_2-1775.jar:?]
1. Resource issue causing timeouts.
2. A crash.
1. The memory utilization of Roboserver should be monitored and increased if needed - follow this KB for more information:
If Management Console is configured for Tomcat, monitor its Java process memory and Java max memory setting and increase if needed. Review Tomcat's stderr or catalina log. There will be entries similar to the following that show minimum and maximum memory configured:
01-Aug-2022 14:01:18.958 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms128m
01-Aug-2022 14:01:18.958 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx2048m
2. For crashes, Roboserver server should have a crash dump time-stamped near the same time as shown in Robot runs log in MC. The path to the crash dump files on the Roboserver is:
If there is a dump file, zip and attach to a Technical Support Case for review.
Level of Complexity
Article # 3052473