RPA unable to connect to windows machine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2023 05:06 AM
Hi All,
I have built unattended robot on MID server and it works well when I start process from RPA designer studio.
However when triggering bot process from instance, I get following error:
Failed to login onto the computer, please validate the credentials. Job was canceled.
Seems straight forward, that credentials are wrong. However I am using my credentials and I am able to log in with them. I have set up credential set, assigned robot and liked those together via process robot credentials record.
In windows I have configured unattended robot and connected it to the instance.
Does anyone have any idea what else it might be?
If anyone else is logged to the machine, I get different error:
Another user '************' was already logged on to this computer. Job was canceled.
This is easily fixed by signing off. But to me it looks like it is connecting to correct device because of that.
Anyway, any help or advice would be much appreciated.
Maros
- 3,163 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2024 11:05 PM
dd your machine cred. like corp\windowuserid without any @ domian ....& your paasword --add in this format to your bot process
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2024 11:06 PM
Add your machine cred. like corp\windowuserid without any @ domain ....& your password --add in this format to your bot process

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2025 11:16 AM
When creating Windows credentials, you must provide the Domain\Username
You can find this information in the Command Prompt using the command whoami.
Example: NB-999999\userName

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 10:27 AM
I am having the same issue even getting "whoami" on CMD.
I am using a shared virtual machine.
It works fine when I am the only one logged, but cracks when other users log on Windows.