Vm login issue from orchestrtor

I have 1 robot that is active on 2 different vm’s.
1 - stays active licensed , 2- connected but unlicensed.

When I got error “Cannot bring the target application in foreground because the Windows session is locked.” for 1 bot, I tried to singed out from VM.

But other bots are not working meaning - staying in pending stage until I manually logged in to that vM.

What should I do here?

Sounds like you may not have installed UiPath properly on that server. Re-run the UiPath installer and make sure you select Service Mode.

ok , let me try that.

Do you mean this to select ?
image

I uninstall and trying to re-install studio version 2022.4.4 but did not get option of service mode selection. How to select that ?

Also I noticed when I signing out from VM, Orchestrator robot status showing off. When I login vm it is showing as active.

Studio is irrelevant. You don’t need to install Studio nor Assistant. Robot is what you need, and it should be in Service Mode.

That’s because you installed in User Mode so Robot.exe is only running when you’re logged in, rather than running as a service.

Can you guide me how to reinstall robot in service mode ?

You highlighted it. “Register Robot as Windows Service”

When it says Robot it’s talking about Robot.exe - the app that actually connects to Orchestrator and runs automations.

So, I just have to check that highlighted checkbox ?

Yes, check that box.

I did it but still it is same. When sign out from VM Robot is disconnecting.
Is there something to do on Orchestrator settings ?

No. I would completely uninstall UiPath from the server, reboot the server, then redo the install.

Are you running the installer as an account with administrator permissions on the server?

I don’t know about the administrator permission , is it something we have to select during installation process ?

I will do that but does that remove my installed bot for that vm ?

Hi @PALKUMARI_PATEL for 2.Connected but unlicensed verify the machine name while creating machine in orhcestrator.

also check in orchestrator license page , how many licensed are consumed?

As he expalined, it connects properly when he logs into the VM. This indicates Robot is not installed in service mode. It does not indicate a license issue nor machine name issue.

It sounds like maybe you should have one of your system administrators do the install. They’ll know how to do it.

We consumed 4 license but we using 1 licenses robot and 2 different machines. That will work when I sign out from both machines ? or Do i need both licensed robot ?

So, I have to install with administration permission ? I downloaded studio.

Yes, of course, you have to install with an administrator account. Right-click the installer and click Run as Administrator. A non-administrator account cannot create a service.

The installer includes everything - Studio, Assistant, and Robot. The only one you need to install is Robot, but you can install Studio and Assistant if you want. Assuming these are production servers, you generally wouldn’t install Studio nor Assistant. Studio is for development, not production - and Assistant is for attended automations (ie installed on people’s computers).

I understand but We don’t have test server yet so sometimes to see issues , we have to check it on PROD servers. So, that’s why I installed studio on server.

Installer is under c drive ?

I don’t know where you saved your installer. It’s a file you downloaded. Only you know where you saved it.