Unable to login to AWS EC2 instance for robotiq unattended robot

Hello!

There could be several issues related to that. Here are some steps you can try:

1. First, restart the virtual machine after installation and try again.

2. If that doesn’t work, verify that you are entering the correct username, domain, and password, and that your VM user has the proper rights to log in interactively.

3. Additionally, ensure that:

   • Ctrl+Alt+Del (Secure Sign-In) is disabled

   • Any welcome messages or legal notices are turned off

   • No pop-ups or confirmations are blocking the login session

4. Check that the robot user is added to “Allow log on locally” under Local Security Policy (secpol.msc → Local Policies → User Rights Assignment).

5. Verify that Remote Desktop is enabled, the RDP port (3389) is open, and the robot user is allowed to connect via RDP.

6. Make sure Windows firewall or antivirus software isn’t blocking local TCP communication (especially port 32788 and dynamic local ports).

7. Check if there is an active console session on the virtual machine – Windows virtual machines support only one active console session at a time, and the robot user must have exclusive access to that session.

8. Check for any known issues with recent Windows cryptographic errors

Please let me know if you succeed 🙂

Hi Emb, still can’t get it to work. Same error shown.

Is it the same error? Is there anything in the Event Viewer or the Handler log?

Hi Emb,

I got this event for the job above:

The winlogon notification subscriber <WSearch> was unavailable to handle a notification event.

Event ID: 6000

I also just tried rebooting the EC2 instance, and didn’t login to any of the accounts. I still got the same error of Query session with username robotiquser does not exist.

Hi Emb,

I realised I did not open up the ports on EC2.

This is a new error I got:

Apr 25, 2025, 4:19:04 PM ERROR Log in failed. Machine is not available. Check credential provider setup.
Source: CreatingUserSessionState

Apr 25, 2025, 4:19:04 PM ERROR Login onto machine failed because contacting CP ended in error. Check this machine logs for further info. Machine id: <redacted>
Source: CreatingUserSessionState

Apr 25, 2025, 4:19:04 PM ERROR Log in failed because communication with credential provider cannot be established. Setting Job status to ERROR state and sending ack to queue
Source: CreatingUserSessionState

Where can I specifically check machine logs? Event Viewer doesn’t show much data.

Check this: Ctrl+Alt+Del (Secure Sign-In) is disabled, all welcome messages or legal notices are turned off and no pop-ups or confirmations are blocking the login session