Device Disconnected

Connecting to a different Control Room is the most frequent cause of this issue. Weather it be switching between Control Rooms in different environments on your company network or switching from a company CR to the Community Edition CR.

Upgrading should be straight-forward.  You simply follow the procedure you already followed for installing the Bot Agent.

Reconnecting is slightly trickier.  I’ll describe that below.

The easiest thing to check is your Bot Agent.  Open your computer’s Services & check that your Automation Anywhere Bot Agent is running.  If it’s running, move on to the next section which describes checking your credentials & cached Control Room references.

If you connected to another Control Room previously or are trying to switch Control Rooms: When you connected to the Control Room, a few properties were added to a file on your machine, and they’ll remain there until you remove them.  Those properties include a reference to the CR to which you’re connecting.  When your company installed A2019, they should have received a file called reconnectBotAgent.bat.  Right-clicking this file and running as Administrator will remove those connection properties.  Once removed, you can try to reconnect.

It’s usually easiest to start by deleting your device from CR –> MY DEVICES.  If you don’t, you’ll end up with the following error:  System allows only a single device to be registered. If you need to replace your existing device you should delete it first. Code devicemanagement.register.validation.single.device

Then, in the top right of the CR, make sure your credentials are correct.  Be sure to include your domain & not just your username.

To find your domain and username, open a command prompt and type “whoami”.  Put that in the Device credentials window and Update credentials, as seen below.  Note: If you’re not on a bot runner, you don’t need to fill out a password.

Next, follow the steps to install the Bot Agent.

I hope that helps!