Instructions to solve 'Credentials are not set' error while setting up your bot agent and connecting to Control Room

Hi, I am having some issues connecting my device, I get the error message below

As far as I can see it is not already connected, so I can’t delete it. Any ideas?

TIA

Hi, I am having some issues connecting my device, I get the error message below

 

 

As far as I can see it is not already connected, so I can’t delete it. Any ideas?

 

TIA

Can you confirm that your Manage>Devices screen in Community Edition is empty of Devices?

If the device is listed, please delete it from the far right three dot menu.

Interesting. I did need to use the cmd prompt as administrator to get it to work your way.

I did solve my issue a different way to get control room working initially so I could do the courses so I may go in and delete my settings and then try to fix it again and document how I was able to resolve it and then share it so people have a couple different ways they can figure it out.

Sure, please share, it will be useful for other developers, thanks.

When i try to do the “hello, world” test bot I get a message that i need to update (  Required bot agent version: 20.11 or above) message. Where would i find the place to update it?

​@NelleCarter  a notification should automatically show up in your control room and you should be able to click on a button to update it. 

But in case you don’t get that notification, you can try installing it from here: https://aai-artifacts.my.automationanywhere.digital/botrunnermanager/22.140.27/AutomationAnywhereBotAgent.exe

Hi there, we’re seeing something similar on our side.

In our case it’s pretty inconsistent, and it really only started happening within the last week. I tried switching my default device over to our VM so I could run some end-to-end testing. When I go into Settings > Devices > Edit and change it to use the VM’s device, everything looks fine at first (VM is running, auto-login is enabled, and my roles/permissions look correct).

But when I go to enter the username/password for the VM, an error briefly flashes, the password never actually saves, and the login doesn’t stick. So it ends up failing every time even though the configuration appears correct.

Now when I go into a test user who has this VM set as their default device and check their device credentials (Administration > Users > target user > Device login credentials), I see the correct username but an old password.

I’ll update it to the new password, click “Save changes” in the top right, go back into that same user, and when I open Device login credentials again it’s still showing the old password instead of what I just entered. So it looks like the UI lets me type and “save,” but the actual stored value never updates.

I’ve double-checked that I’ve got the right roles/permissions on my account, and I even tried the same steps while logged in as an admin, but I’m getting the exact same behavior there too.

​@connor.obrien  did you add domain name before user name ? like AD\user name ?