The Job's Package XXX Could Not Be Found (#1661) After Migrating Orchestrator Server

News Knowledge Base
1

Error resolution for "The job's package xxx could not be found (#1661)" in Orchestrator when trying to add a process to a trigger after migrating the Orchestrator server ?

Issue Description

The error "The job's package xxx could not be found (#1661)" is encountered in Orchestrator when trying to add a process to a trigger:

image.png

Root Cause

This error usually occurs when the packages have not been migrated during the Orchestrator migration and they are not found on the new server. However, the old processes are still running because they have already been downloaded on the robot machines from previous runs.

Resolution

The missing packages can be restored from the initial database backup made before the migration.

Restore the NuGet packages directories:

  1. For Legacy repositories, copy your backups of the NuGet packages and activities folders to the directories identified by the NuGet.Packages.Path and NuGet.Activities.Path keys indicated in the Deployment section of the UiPath.Orchestrator.dll.config file.
  2. For Composite repository types where the Storage.Type key is:
    1. FileSystem - copy your backup folder(s) to the directory identified in the Storage.Location key of the RootPath parameter, found in the Deployment section of the UiPath.Orchestrator.dll.config file.
    2. Azure - enter the previously saved connection string in the Storage.Type key.
    3. Amazon - enter the previously saved connection string in the Storage.Type key.