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

Padmakumar
Premier Pathfinder | Tier 7
Padmakumar
Premier Pathfinder | Tier 7
January 23, 2023

Hi @MJ 8116 ,

 

Could you please confirm whether you have individually running the Control Room in each machines or are you trying to add all 14 machines to a single CR?

 

If the answer is second one, Community edition will not support more than 1 device to be connected with the CR.

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

    Hi @MJ 8116 

    If you are trying to configure each machine with a individual Community CR login it will work, not other way around.

    If the above point is valid, uninstall the existing bot agent and try installing as a admin and then try connecting to the device.

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

    Hi @MJ 8116 

    If you are trying to configure each machine with a individual Community CR login it will work, not other way around.

    If the above point is valid, uninstall the existing bot agent and try installing as a admin and then try connecting to the device.

    Adding to the above, checkout below links for setting up Bot Agent and Community CR limitations,

    https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/release-notes/cloud-A2019-faq.html

    https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/log-on-to-control-room/cloud-register-community-user.html

    https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/deployment-planning/cloud-community-capacity.html

    Chand
    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

    The bugs persist, so do I.
    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? Hope they are providing user credentials as per below steps,

    1. Open cmd
    2. Type whoami
    3. Copy the domain\username as a username
    Chand
    M
    Cadet | Tier 2
    MJ 8116Author
    Cadet | Tier 2
    January 23, 2023

    Hi @MJ 8116 

    If you are trying to configure each machine with an individual Community CR login it will work, noa other way around.

    If the above point is valid, uninstall the existing bot agent and try installing as a admin and then try connecting to the device.

    @ChanduMohammad This is exactly what we were doing but using our community access not the trainee access. Do multiple logins can cause this issue?

    The bugs persist, so do I.
    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.

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

    Hi @MJ 8116 

    If you are trying to configure each machine with an individual Community CR login it will work, noa other way around.

    If the above point is valid, uninstall the existing bot agent and try installing as a admin and then try connecting to the device.

    @ChanduMohammad This is exactly what we were doing but using our community access not the trainee access. Do multiple logins can cause this issue?

    Multiple logins using one single account in the same machine will not cause any issue

    Chand
    C
    Most Valuable Pathfinder
    ChanduMohammadMost Valuable PathfinderAnswer
    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
    Chand
    M
    Cadet | Tier 2
    MJ 8116Author
    Cadet | Tier 2
    January 23, 2023

    Hi @MJ 8116 

    If you are trying to configure each machine with an individual Community CR login it will work, noa other way around.

    If the above point is valid, uninstall the existing bot agent and try installing as a admin and then try connecting to the device.

    @ChanduMohammad This is exactly what we were doing but using our community access not the trainee access. Do multiple logins can cause this issue?

    Multiple logins using one single account in the same machine will not cause any issue

    How about multiple logins in different machines? But I did try not to do it simultaneously.

    The bugs persist, so do I.
    Show more replies
    Terms & ConditionsAccessibility statement