Skip to main content

I uninstalled the bot agent, used the uninstall.batch file on C:\Program Files\Automation Anywhere\Bot Agent

 

while i was trying to install the bot agent, it gave this error” 

Unable to connect to the Control Room and it may be due to not being able validate the SSL certificate presented by the Control Room.

This may be due to multiple reasons. To continue, please 1. Check to see if the SSL certificate has been added to the Java Key Store that is bundled with the bot agent. Then, try again.

If you continue to see this message, please contact your system administrator.”

 

what should i do next?

@Raul Jaimes @ChanduMohammad I asked this to my manager, and he also said the controlroom links must be different, we will look at the issue together, ill see where i do my mistake, ill update here afterwards. Thank you

@Raul Jaimes @ChanduMohammad I asked this to my manager, and he also said the controlroom links must be different, we will look at the issue together, ill see where i do my mistake, ill update here afterwards. Thank you

Great @Semih 3318 

@Raul Jaimes @ChanduMohammad I asked this to my manager, and he also said the controlroom links must be different, we will look at the issue together, ill see where i do my mistake, ill update here afterwards. Thank you

Awesome :)

@Raul Jaimes @ChanduMohammad its solved now.

in the C:\Windows\System32\drivers\etc\host file, at the last row, I added the controlroom IP address tabspace controlroomlink and saved the file

then we updated the correct cacerts certificate in the C:\Program Files\Automation Anywhere\Bot Agent\jre\lib\security cacerts  this path.

installed botagent, it works now, thank you :)

@Raul Jaimes @ChanduMohammad its solved now.

in the C:\Windows\System32\drivers\etc\host file, at the last row, I added the controlroom IP address tabspace controlroomlink and saved the file

then we updated the correct cacerts certificate in the C:\Program Files\Automation Anywhere\Bot Agent\jre\lib\security cacerts  this path.

installed botagent, it works now, thank you :)

Thanks for sharing the resolution @Semih 3318 

@Raul Jaimes @ChanduMohammad its solved now.

in the C:\Windows\System32\drivers\etc\host file, at the last row, I added the controlroom IP address tabspace controlroomlink and saved the file

then we updated the correct cacerts certificate in the C:\Program Files\Automation Anywhere\Bot Agent\jre\lib\security cacerts  this path.

installed botagent, it works now, thank you :)

 

Great! 

@Semih 3318 : don’t you have big ip or generic url for control room even it installed in multiple servers ?  Use the control room access url … here in my case control room installed on two servers but accessing with generic url and you have to connect this generic url from vdi
 

 

@rbkadiyam Thank you for your comment. The controlroom links are the same for the old controlroom and newly installed one. Only Ip adress is different.

But when i wrote “ping controlroomLink” on command prompt, i saw the botrunner was connecting to the old one.

After updating C:\Windows\System32\drivers\etc\host file, it succesfully connected to new controlroom,

i just added one row, thats “newControlroom ID tabSpace controlroomLink”

Reply


Terms & ConditionsCookie settings