Skip to main content
Solved

Unable to connect bot agent - Unexpected error occurred


Forum|alt.badge.img+2

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

MJ 8116 wrote:
ChanduMohammad wrote:
MJ 8116 wrote:

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
View original
Did this topic help answer your question?

18 replies

Padmakumar
Forum|alt.badge.img+13
  • Navigator | Tier 3
  • 785 replies
  • 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.


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • 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.


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • January 23, 2023
ChanduMohammad wrote:

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


Forum|alt.badge.img+2
  • Author
  • Cadet | Tier 2
  • 8 replies
  • 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


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • January 23, 2023
MJ 8116 wrote:

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

Forum|alt.badge.img+2
  • Author
  • Cadet | Tier 2
  • 8 replies
  • January 23, 2023
ChanduMohammad wrote:

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?


Forum|alt.badge.img+2
  • Author
  • Cadet | Tier 2
  • 8 replies
  • January 23, 2023
ChanduMohammad wrote:
MJ 8116 wrote:

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.


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • January 23, 2023
MJ 8116 wrote:
ChanduMohammad wrote:

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


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • Answer
  • January 23, 2023
MJ 8116 wrote:
ChanduMohammad wrote:
MJ 8116 wrote:

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

Forum|alt.badge.img+2
  • Author
  • Cadet | Tier 2
  • 8 replies
  • January 23, 2023
ChanduMohammad wrote:
MJ 8116 wrote:
ChanduMohammad wrote:

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.


Forum|alt.badge.img+2
  • Author
  • Cadet | Tier 2
  • 8 replies
  • January 23, 2023
ChanduMohammad wrote:
MJ 8116 wrote:
ChanduMohammad wrote:
MJ 8116 wrote:

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.

 


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • January 23, 2023

Might be @MJ 8116 

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


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • January 23, 2023
MJ 8116 wrote:
ChanduMohammad wrote:
MJ 8116 wrote:
ChanduMohammad wrote:
MJ 8116 wrote:

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


rbkadiyam
Flight Specialist | Tier 4
Forum|alt.badge.img+17
  • Flight Specialist | Tier 4
  • 587 replies
  • 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 


Forum|alt.badge.img+2
  • Author
  • Cadet | Tier 2
  • 8 replies
  • January 23, 2023
rbkadiyam wrote:

@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.

 


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • January 23, 2023
rbkadiyam wrote:

@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?


Forum|alt.badge.img+2
  • Author
  • Cadet | Tier 2
  • 8 replies
  • January 24, 2023
ChanduMohammad wrote:
rbkadiyam wrote:

@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!


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2694 replies
  • January 24, 2023
MJ 8116 wrote:
ChanduMohammad wrote:
rbkadiyam wrote:

@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 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings