I’m looking for help with not being able to connect UiPath Assistant to a license. We’re using a Community license, and the robot is hosted on a Windows server set up on a VM. As part of BCP recovery testing, the Windows server with the robot on it was shut down and restored from a backup in a different data center, with a different IP address. I have not been able to connect the robot to Orchestrator on the restored server. This is error I get in UiPath Assistant: “Status: Connected to Orchestrator but was unable to retrieve a license. Please contact your automation department. Could not find unattended robot for user key […]”
As the attached image shows, a license was definitely available in Orchestrator.
After this, we restarted the original robot server. I logged out of the restored server and logged back into the original server. On the original server, I was able to connect the robot to Orchestrator again with no problems.
My question is, why was the robot unable to connect to Orchestrator on the restored server? Is there anything I need to do to account for the changed IP address of the robot server?
License Activation: It’s good that you’ve verified that a license is available in Orchestrator. However, after restoring the server, you might need to re-activate the license on the new IP address. Try deactivating the license associated with the old IP address and then reactivating it with the new IP address.
Machine and Robot Reconfiguration: The change in IP address might have caused the machine and robot configurations to become out of sync. In Orchestrator, make sure the machine entry corresponds to the new IP address. Also, verify that the robot is associated with the correct machine in Orchestrator.
User Key and Permissions: The error message mentions “Could not find unattended robot for user key.” Ensure that the user key you’re using for the robot is correctly associated with the robot in Orchestrator, and that the user has the necessary permissions to access the robot and its associated resources.
Firewall and Network Settings: A change in IP address can sometimes result in firewall or network-related issues. Make sure that the necessary ports (e.g., 443 for HTTPS) are open in the firewall settings of the server and the network.
Hostname Resolution: Check if the restored server can correctly resolve the hostname of the Orchestrator server. If there’s any DNS discrepancy, it might affect the connection.
Robot Configuration: Verify that the UiPath Robot configuration on the server is pointing to the correct Orchestrator URL and that the machine key and user key are accurate.
Robot Service: Sometimes, the Robot service might need a restart to apply configuration changes. Try restarting the UiPath Robot service on the server.
Machine Key: If the machine key has changed due to the restoration, you’ll need to update the machine key in both Orchestrator and the Robot settings.
User Logout and Login: Sometimes, a simple user logout and login might help to refresh the connection and resolve configuration-related issues.
UiPath Version Compatibility: Ensure that the version of UiPath Assistant and Orchestrator you’re using are compatible and up-to-date.
Contact UiPath Support: If none of the above steps resolve the issue, you might want to reach out to UiPath’s support for further assistance.
Remember that changes in IP addresses and server configurations can have ripple effects on various aspects of the system. It’s important to carefully review and adjust the settings to ensure everything is in sync and aligned with the new setup.
Thank you @Usha_Jyothi ! Looks like the problem was that the license was active on both servers at the same time. It seemed that the robot worked well after the restored server was shut down and I switched back to the original server. But that wasn’t true. The robot could run attended automations, but not unattended automations. I noticed that in Orchestrator → Monitoring → Machines, the machines on both servers were showing as active and licensed, even though one of the servers was shut down. Since we have only one license, having two robots connected at the same time would explain the errors. I disconnected the robot on one of the servers using UiPath Assistant → Orchestrator Settings → Disconnect. After that, unattended automations could run with no problems.
