Skip to main content

I am having an issue getting our third server to work with RDP. We have two servers with another service but we are moving to Azure and have one server setup with them. The RDP works with the old two servers, but I cannot get it to work with the Az one. I have the IP’s I found here whitelisted. Control Room IP addresses for external integrations (automationanywhere.com) No one else is logged in and only one other person has access to the server via an admin account.

If I open an RDP session on my local computer, I can then schedule a bot and it can use that RPD session to run. If I use the “regular” auto log-in it also works. The error only happens when I try to run an unattended bot and AA needs to establish the RDP.

Error:

java.lang.RuntimeException: {"message":"Error creating RDP session.","details":"This may be due to multiple reasons. To continue, please\n\n1. Please check the number of max session count is configured for this machine\n2. Please find out if no one else has RDP on the machine\n3. Please check that there are no other processes holding RDP connection on the machine\n\nIf you continue to see this message, please contact your system administrator.","correctiveAction":"","code":"rdp.error"}

Hi, I´m experiencing the same issue, was this resolved in your case? Thank you.


@Katka ​@jduncan I would venture a guess that this is a DNS/AD issue.Check with your IT department to make sure the target RDP server name has DNS records added, not just a presence on the Active Directory tree/forest.

The Bot Agent runs in Java which is not terribly AD friendly. If you’re connecting using MSTSC (the RDP client), it can resolve server names via AD, but I’ll place money our Bot Agent cannot. 

A workaround might be to try connecting to the RDP server’s IP address rather than its name. If that works then your IT department needs to add a DNS entry for your server so non-AD clients (e.g., Linux or Macs too) can resolve its IP address.


Reply