Package Migration Tool Usage For 2020.10 Orchestrator

News Knowledge Base
1

Why post upgrading Orchestrator to 2020.10.3, packages and libraries are empty ?

  1. Run the following script to migrate the packages and libraries. Change the parameters according to the setup,

c:\Program Files (x86)\UiPath\Orchestrator\Tools\PackagesMigrator\UiPath.Orchestrator.Setup.PackagesMigration.Console.exe start --application-path "c:\Program Files (x86)\UiPath\Orchestrator" --connection-string "Server=;Database=;Integrated security=true" --storage-type "FileSystem" --storage-location "RootPath=.\Storage" --processes-path "c:\Program Files (x86)\UiPath\Orchestrator\NuGetPackages" --libraries-path "c:\Program Files (x86)\UiPath\Orchestrator\NuGetPackages\Activities"

  1. Run the following script to cleanup,
C:\Program Files (x86)\UiPath\Orchestrator\Tools\PackagesMigrator\UiPath.Orchestrator.Setup.PackagesMigration.Console.exe finish --connection-string "Server=;Database=;Integrated security=true" --purge-dirty-definitions

  1. Restart Orchestrator. Login to Orchestrator and check packages and libraries all should show.



If the issue continues and not seeing any packages or libraries showing up, check for user Default Schema

  1. Run the following SQL command,

SELECT name, type_desc, default_schema_name

FROM sys.database_principals

WHERE type in ('S', 'U');

  1. If users default schema is anything but DBO run the following below. Change the username Schema to DBO

ALTER USER [domain\user] WITH DEFAULT_SCHEMA = dbo