Skip to main content
Cadet | Tier 2
May 12, 2022
Question

Connecting your computer to Control Room is not connecting its still loading

  • May 12, 2022
  • 11 replies
  • 345 views

I have remove the device and uninstall the bot agent and install it for many time still it is loading.

 

Screenshot (2159)

    11 replies

    Automation Anywhere Team
    May 12, 2022

    Hello @Abishek Thiyagaraja​ ,

    Perform the basic troubleshooting leveraging AADiagnosticUtility, especially on Proxy and Websocket errors.

    Perform Bot agent diagnostic checks (automationanywhere.com)

    Cadet | Tier 2
    May 12, 2022

    maybe A360 extension isn't activated. you can find it hereScreenshot_3

    Cadet | Tier 2
    May 13, 2022

    extension is activated.

     

    Cadet | Tier 2
    May 13, 2022

    Hello @Sajith Sudhakaran​ 

    I have check these things and I have attached the screenshot below.

     

    Screenshot (2163)

    Cadet | Tier 2
    May 13, 2022

    No.

    I have attached the screenshot below with my control room URL.

     

    Screenshot (2165)

    Automation Anywhere Team
    May 13, 2022

    "https://yourcrurl.comquot; is your Control Room URL ?

    Automation Anywhere Team
    May 13, 2022

    Look at the error when you ran checkWSError parameter. Websocket is being blocked at Proxy\Firewall.Websocket protocol needs to be allowed in order to establish connectivity with Control Room. You may review Nodemanager.log files located in C:\Programdata\Automationanywhere\Botrunner\logs location

    Cadet | Tier 2
    May 13, 2022

    I have check that but can not understand it.

    So again I have uninstall the bot agent and install it. But now there is no any error is showing in command prompt (I attached the screenshot below). But anyway still I cant connect to the control room.

    Screenshot (2169) 

    Automation Anywhere Team
    May 13, 2022

    Reinstallation of Botagent doesnt resolve Websocket issues. All the logs are cleared while installing the botagent and that may be the reason that error is now showing now. It may appear when you run this command again after reproducing the issue.

    You will have to look for errors in nodemanager.log or validate the websocket following the article below.

    https://apeople.automationanywhere.com/s/article/How-to-validate-Websocket-connection//p>

    Cadet | Tier 2
    May 16, 2022

    Link that you provide is not working.

     

    Screenshot (2170)