Chrome Messaging Host not launching quickly enough for Web Adapter
We are encountering an issue where some of our users who are on Virtual Machines get an error when they launch their applications in the morning. The error states that the Runtime failed to connect with the Chrome Messaging Host in the allocated 20 seconds. The message gives the option to retry, in which case it will then be able to connect, most of the time (there were instances where more than 1 retry were needed).
While this is not too bad of a work-around and that there is also the option to launch a chrome browser prior to launching all applications through the robot, we'd like to know if there is a way to increase this timeout through a setting of some sort. Our initial investigation seems to indicate that this value is hard-coded and not editable but we'd like to make sure.
If increasing the timeout is not an option, is there anything else that we can do to ensure that users won't see this message?
***Edited by Moderator: Pallavi to update Support Case details***
The timeout is not editable at least from what I know. I have not seen it be slow before though unless you have some sort of resource constraint or some other underlying condition (like security software). I would suggest that you open a support case to get this looked into. They may be able to identify why it is launching slowly on your VMs. If you do, please record the support case number in the post.