Job Faulting when Unattended

Here is my scenario:

I need to run a process on a server. I access the server via remote desktop. When the process is run via assistant on the server it works without issues. When the process is run from Orchestrator while I am manually logged into Remote desktop, it works without issues.

The problem is, when I try to run it from Orchestrator with remote desktop closed the job immediately faults.

Can someone please help?

@kasey.betts,

Have you installed the robot as service mode
The behaviour normally observed when it not installed as service mode.

Refer this documentation for more details.

@kasey.betts

Is the error saying executor could not start or so?

if so did you happen to give the robot credentials in the manage access menu

if starting and failing like with cannot bring target app or could not access element then check the robot is installed in service mode or not on server

cheers

I just reinstalled in service mode. It was in user mode. Now I am getting this error.

@kasey.betts

Just login to Orchestrator → Tenant → Manage Access → Robot Account → Goto Robot Edit → UnAttended Setup → Provide proper UserName and Password

Now, try to execute the process!

Best regards,
Ajay Mishra

I have done that and it seems like its logging in successfully but now I get this error

yes it’s saying this

@kasey.betts

The error message “ERROR_ELEVATION_REQUIRED” indicates that the process requires elevated privileges to run. This is often caused by permission or configuration issues when UiPath Robot Service is running in Service Mode.

  1. Ensure Service Mode Is Properly Configured
    When using Service Mode, the UiPath Robot runs as a Windows Service. It requires proper permissions and user configurations:
    Open the UiPath Assistant and ensure it is connected to the Orchestrator.
    Verify that the Robot in Orchestrator is configured as an Unattended Robot.

  2. Verify Robot User Settings in Orchestrator
    Go to Orchestrator → Tenant → Folders → Manage Access.
    Ensure the user associated with the Robot has the following:
    Unattended Robot role assigned.
    The correct Domain\Username and Password for the user are configured in Machines > Unattended Robot Settings.

  3. Assign Administrator Privileges
    Make sure the user running the process has administrator privileges.
    To assign:
    Open Computer Management.
    Navigate to Local Users and Groups → Users.
    Find the user, right-click, and select Properties.
    Add the user to the Administrators group.

  4. Configure RDP for Unattended Execution
    Ensure that the Robot can run without an active RDP session:
    In Orchestrator, navigate to the Robot Settings.
    Add the resolution width, height, and depth under Robot Settings.
    Ensure the Login To Console option is set to No.

LLM Generated Answer, but try it once. Your issue will resolve!

Best regards,
Ajay Mishra

Did all that and am now getting this

@kasey.betts

As per error looks like you have selected studio to run as admin…did you force select in its properties?

What machine is that?

Cheers

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.