Auto Updating Client Components is not working

News Knowledge Base
,
1

Why is Auto updating client components not working for all Users/Robots?

Issue Description

During Auto-update, download of the msi installer is performed with Windows BITS Service, if available. If not available, http clients are used for downloading but no browser/uiautomation is involved. The msi is downloaded to a location depending on the install type.
  • For machine-level install (attended/unattended) - %programdata%\UiPath\UpdateService\Downloads.
  • For user-level install - %localappdata%\UiPath\UpdateService\Downloads

Update Logs location:
  • %localappdata%/Uipath/UpdateService/logs or
  • %Programdata%/Uipath/UpdateService/logs

Possible Causes

  1. Orchestrator URL not added during setup of Studio / Robot in User Mode
  2. Additional configuration for Robots sitting behind a proxy is missing
  3. When the required services ( like UiPath.UpdateService.Worker.exe, UiPath.UpdateService.Agent.exe) are not running
  4. When Update Policy is set to None on Orchestrator.
  5. There were too many failed attempts to download


Resolution

Orchestrator URL not added during setup of Studio / Robot in User Mode

  • If the URL is not added during the installation, it can be added in the UpdateServer.Json file located in "%localappdata%\UiPath\UpdateService" or "C:\ProgramData\UiPath\UpdateService" post upgrade. If the file cannot be updated, an Admin user has to make this change and save it.

image.png


    Additional configuration for Robots sitting behind a proxy is missing

    • Validate if a Proxy is being used on the machine where the Robot is installed (information can be found under Proxy Settings of the Robot Machine). If there is a proxy found, configure the Proxy as per the details
    • Despite proper setup of the proxy, the download might not work. Check with the IT team if Proxy authentication is required.

    When the required services ( like UiPath.UpdateService.Worker.exe, UiPath.UpdateService.Agent.exe) are not running

    • Depending on the type of Studio/Robot installation, they are installed and run differently.
      • Unattended Robot: UiPath.UpdateService.Worker.exe is installed as Windows Service and UiPath.UpdateService.Agent.exe is not installed.
      • Attended Robot: UiPath.UpdateService.Worker.exe is installed as Windows Service; UiPath.UpdateService.Agent.exe is installed as LogOn Task in Task Scheduler.
      • Quick Install (user mode): UiPath.UpdateService.Worker.exe and UiPath.UpdateService.Agent.exe are installed as LogOn Tasks in Task Scheduler.
    • Windows Services can be verified by navigating to Windows Search---Services on the Robot machine.

    When the Update Policy is set to None on the Orchestrator


    There were too many failed attempts to download

    • Stop the "UiPath Update Service" Windows service.
    • Delete the file %programdata%\UiPath\UpdateService\Dbs\OperationDb.db
    • Restart the "UiPath Update Service" Windows service.
    • (optional) Start UiPath Studio on that machine to force an immediate check for updates (otherwise it will take at most one hour for a check update to be performed.