Skip to main content
M
Cadet | Tier 2
MJ 8116
Cadet | Tier 2
January 23, 2023
Solved

Unable to connect bot agent - Unexpected error occurred

  • January 23, 2023
  • 18 replies
  • 781 views

Hi team,

We trying to setup 15 computers for A360 training purposes and activity but were unable to setup the community edition successfully.

We can install the bot agent but we cannot connect to it, keeps getting an error message.

Unexpected error occurred please contact your system administrator.

 

Best answer by ChanduMohammad

Hi @Padmakumar ,
We are trying to setup each device individually for each user, when you say adding all 15 machines to a single CR does it mean our company has a specified number of CR?.

The users actually tried to configure using their personal computer but got the same error, so I guess it’s not the CR issue.
Each user has their own community access and has their own computer that they can use.

Thanks

Thanks @MJ 8116 for the clarification, think your team is going in a right way.

Can you ask the team to install bot agent as a admin and try connecting to the CR?

This has been done just a few minutes ago and we always get the same error. We tried it on multiple computers and laptop.

This is strange, hey can you try once again using below steps,

 

  • Uninstall Bot Agent
  • Delete files in C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere
  • Download and install Bot Agent again
  • Complete the Device registration instructions shown on the screen

18 replies

Show previous replies
M
Cadet | Tier 2
MJ 8116Author
Cadet | Tier 2
January 23, 2023

Hi @Padmakumar ,
We are trying to setup each device individually for each user, when you say adding all 15 machines to a single CR does it mean our company has a specified number of CR?.

The users actually tried to configure using their personal computer but got the same error, so I guess it’s not the CR issue.
Each user has their own community access and has their own computer that they can use.

Thanks

Thanks @MJ 8116 for the clarification, think your team is going in a right way.

Can you ask the team to install bot agent as a admin and try connecting to the CR?

This has been done just a few minutes ago and we always get the same error. We tried it on multiple computers and laptop.

This is strange, hey can you try once again using below steps,

 

  • Uninstall Bot Agent
  • Delete files in C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere
  • Download and install Bot Agent again
  • Complete the Device registration instructions shown on the screen

Alright will try this and I’ll let you know, Thanks.

 

The bugs persist, so do I.
C
Most Valuable Pathfinder
ChanduMohammadMost Valuable Pathfinder
Most Valuable Pathfinder
January 23, 2023

Might be @MJ 8116 

In the above comment will delete existing AA folder so we can do a clean installation

Chand
    C
    Most Valuable Pathfinder
    ChanduMohammadMost Valuable Pathfinder
    Most Valuable Pathfinder
    January 23, 2023

    Hi @Padmakumar ,
    We are trying to setup each device individually for each user, when you say adding all 15 machines to a single CR does it mean our company has a specified number of CR?.

    The users actually tried to configure using their personal computer but got the same error, so I guess it’s not the CR issue.
    Each user has their own community access and has their own computer that they can use.

    Thanks

    Thanks @MJ 8116 for the clarification, think your team is going in a right way.

    Can you ask the team to install bot agent as a admin and try connecting to the CR?

    This has been done just a few minutes ago and we always get the same error. We tried it on multiple computers and laptop.

    This is strange, hey can you try once again using below steps,

     

    • Uninstall Bot Agent
    • Delete files in C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere
    • Download and install Bot Agent again
    • Complete the Device registration instructions shown on the screen

    Alright will try this and I’ll let you know, Thanks.

     

    Welcome

    Chand
    rbkadiyam
    Premier Pathfinder | Tier 7
    rbkadiyam
    Premier Pathfinder | Tier 7
    January 23, 2023

    @MJ 8116 restart VDI and try to connect again.. it may be the SSL cert issue… if thats the case you have to execute SSL cert update 

    Ramesh B Kadiyam
      M
      Cadet | Tier 2
      MJ 8116Author
      Cadet | Tier 2
      January 23, 2023

      @MJ 8116 restart VDI and try to connect again.. it may be the SSL cert issue… if thats the case you have to execute SSL cert update 

      Thanks @rbkadiyam will try this tomorrow.

       

      The bugs persist, so do I.
      C
      Most Valuable Pathfinder
      ChanduMohammadMost Valuable Pathfinder
      Most Valuable Pathfinder
      January 23, 2023

      @MJ 8116 restart VDI and try to connect again.. it may be the SSL cert issue… if thats the case you have to execute SSL cert update 

      Hey @rbkadiyam they are using Community CR, still should we check on SSL?

      Chand
      M
      Cadet | Tier 2
      MJ 8116Author
      Cadet | Tier 2
      January 24, 2023

      @MJ 8116 restart VDI and try to connect again.. it may be the SSL cert issue… if thats the case you have to execute SSL cert update 

      Hey @rbkadiyam they are using Community CR, still should we check on SSL?

      Hi team, 
      Thank you for your support, we opted to use our training environment in A360 instead of using the community edition.
      Cheers!

      The bugs persist, so do I.
      C
      Most Valuable Pathfinder
      ChanduMohammadMost Valuable Pathfinder
      Most Valuable Pathfinder
      January 24, 2023

      @MJ 8116 restart VDI and try to connect again.. it may be the SSL cert issue… if thats the case you have to execute SSL cert update 

      Hey @rbkadiyam they are using Community CR, still should we check on SSL?

      Hi team, 
      Thank you for your support, we opted to use our training environment in A360 instead of using the community edition.
      Cheers!

      Welcome @MJ 8116 

      Chand
      Terms & ConditionsAccessibility statement