- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Configuring the machines
- Configuring the external objectstore
- Configuring an external Docker registry
- Configuring the load balancer
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the certificates
- Online multi-node HA-ready production installation
- Offline multi-node HA-ready production installation
- Disaster recovery - Installing the secondary cluster
- Downloading the installation packages
- install-uipath.sh parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable NIC checksum offloading
- How to manually set the ArgoCD log level to Info
- Unable to run an offline installation on RHEL 8.4 OS
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- GPU node affected by resource unavailability
- Volume unable to mount due to not being ready for workloads
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- Failure to resize objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- Issues accessing the ArgoCD read-only account
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Step 1: Moving the Identity organization data from standalone to Automation Suite
The standalone and Automation Suite versions must be the same, or else the migration will fail due to database schema conflict issues. If you experience a compatibility failure, make sure to upgrade your standalone and Automation Suite installations to the latest version.
Make sure you download and install .NET Runtime 6.0 before running UiPath.OrganizationMigrationApp. For details, see Migration prerequisites.
To download UiPath.OrganizationMigrationApp, see Migration prerequisites.
\
before special characters.
The UiPath.OrganizationMigrationApp tool supports the following parameters:
Parameter name |
Short name |
Description |
---|---|---|
Identity database connection of the standalone product |
|
The Identity database connection of the standalone product. If Identity and Orchestrator share the same database, then use the connection string of that database. |
Identity database connection of Automation Suite |
| The Identity database connection of Automation Suite. |
Orchestrator database connection of the standalone product |
| The Orchestrator database connection of the standalone product. If Identity and Orchestrator share the same database, then use the connection string of that database. |
List of organization IDs of the standalone product | s |
The list of organization IDs for the standalone product to merge. You must use the following format:
orgId1,orgId2,...,orgId5 .
The size of the organization ID list for both the standalone product and Automation Suite must be the same. To get a list of organization IDs for the standalone product, run the following command on the standalone database and use
GlobalId with the related partition / organization name on the restored database:
|
List of organization IDs of Automation Suite | d |
The list of organization IDs for Automation Suite. You must use the following format:
orgId1,orgId2,...,orgId5 .
The size of the organization ID list for both the standalone product and Automation Suite must be the same. To get a list of organization IDs for Automation Suite, run the following command on the
AutomationSuite_Platform database on the Automation Suite SQL Sever:
|
Rollback |
| The parameter used to roll back a change. |
URL of Automation Suite |
|
The URL of Automation Suite. For example,
https://ci-asaks5380983.devtest-ascloudgen-ea.infra.uipath-dev.com/ |
OMS S2S client secret |
|
The client secret used to call the OMS API to create the tenant. To get the OMS S2S client secret from the Kubernetes secret, run the following command:
|
Here are some common operations you might need to perform:
-
To move the Identity data of all tenants from standalone to Automation Suite, extract the file and run the following command:
./UiPath.OrganizationMigrationApp migrate -m -i '<identity database connection of the standalone product>' -j '<identity database connection of Automation Suite>' -o '<orchestrator database connection of the standalone product>' -s '<list of organization IDs of the standalone product>' -d '<list of organization IDs of Automation Suite>' -p '<URL of Automation Suite>' -c '<OMS S2S client secret>'
./UiPath.OrganizationMigrationApp migrate -m -i '<identity database connection of the standalone product>' -j '<identity database connection of Automation Suite>' -o '<orchestrator database connection of the standalone product>' -s '<list of organization IDs of the standalone product>' -d '<list of organization IDs of Automation Suite>' -p '<URL of Automation Suite>' -c '<OMS S2S client secret>'Note:Make sure to addTrustServerCertificate=True
for all SQL connections in the input. -
If the operation failed in the middle, roll back the change by running the following command:
./UiPath.OrganizationMigrationApp migrate -m -r -i '<identity database connection of the standalone product>' -j '<identity database connection of Automation Suite>' -o '<orchestrator database connection of the standalone product>' -s '<list of organization IDs of the standalone product>' -d '<list of organization IDs of Automation Suite>' -p '<URL of Automation Suite>' -c '<OMS S2S client secret>'
./UiPath.OrganizationMigrationApp migrate -m -r -i '<identity database connection of the standalone product>' -j '<identity database connection of Automation Suite>' -o '<orchestrator database connection of the standalone product>' -s '<list of organization IDs of the standalone product>' -d '<list of organization IDs of Automation Suite>' -p '<URL of Automation Suite>' -c '<OMS S2S client secret>' -
Fix the issue according to the error message and try to move the Identity data of all tenants from standalone to Automation Suite again. For example, see the following error messages and what they mean:
-
The following error message means that the tenant is already created and the program would skip tenant creation. You do not need to do anything.
Call to API Service failed for Method=POST, StatusCode=Conflict on url=https://ci-asaks5379291.devtest-ascloudgen-ea.infra.uipath-dev.com/organization/api/organization/0dad76a9-7d44-447a-84d6-ce713a5324d8/tenants Http Response Content:{"StatusCode":409,"StatusDescription":"Conflict","ErrorCode":1002,"Message":"Found duplicated tenant with requested Id b26f486f-a585-4420-83fd-f2741385b3c8 under organization 0dad76a9-7d44-447a-84d6-ce713a5324d8 (1002)"}
Call to API Service failed for Method=POST, StatusCode=Conflict on url=https://ci-asaks5379291.devtest-ascloudgen-ea.infra.uipath-dev.com/organization/api/organization/0dad76a9-7d44-447a-84d6-ce713a5324d8/tenants Http Response Content:{"StatusCode":409,"StatusDescription":"Conflict","ErrorCode":1002,"Message":"Found duplicated tenant with requested Id b26f486f-a585-4420-83fd-f2741385b3c8 under organization 0dad76a9-7d44-447a-84d6-ce713a5324d8 (1002)"} -
The following error message means that the Automation Suite URL is not valid. Make sure to provide the correct Automation Suite URL.
Unhandled exception. UiPath.IdentityServer.PartitionMerge.PartitionMergeException: Can not create tenant ID with target organiztion ID 0dad76a9-7d44-447a-84d6-ce713a5324d8, tenant name tenant_0dad76a9, platform url https://ci-asaks5379291.devtest-ascloud.infra.uipath-dev.com. ---> System.Net.Http.HttpRequestException: No such host is known. (ci-asaks5379291.devtest-ascloud.infra.uipath-dev.com:443) ---> System.Net.Sockets.SocketException (11001): No such host is known.
Unhandled exception. UiPath.IdentityServer.PartitionMerge.PartitionMergeException: Can not create tenant ID with target organiztion ID 0dad76a9-7d44-447a-84d6-ce713a5324d8, tenant name tenant_0dad76a9, platform url https://ci-asaks5379291.devtest-ascloud.infra.uipath-dev.com. ---> System.Net.Http.HttpRequestException: No such host is known. (ci-asaks5379291.devtest-ascloud.infra.uipath-dev.com:443) ---> System.Net.Sockets.SocketException (11001): No such host is known. -
The following error message means that the OMS S2S client secret is not valid. Make sure to provide the correct OMS S2S client secret.
Call to API Service failed for Method=POST, StatusCode=BadRequest on url=https://ci-asaks5379291.devtest-ascloudgen-ea.infra.uipath-dev.com/identity_/connect/token Http Response Content:{"error":"invalid_client"}
Call to API Service failed for Method=POST, StatusCode=BadRequest on url=https://ci-asaks5379291.devtest-ascloudgen-ea.infra.uipath-dev.com/identity_/connect/token Http Response Content:{"error":"invalid_client"}
-
Make sure you download and install .NET Runtime 6.0 before running UiPath.OrganizationMigrationApp. For details, see Migration prerequisites.
To download UiPath.OrganizationMigrationApp, see Migration prerequisites.
$
with \`$
. For more guidelines on how to escape special characters in connection string passwords, refer to Special character escape rules for connection string passwords.
Here are some common operations you might need to perform:
-
To move the Identity data of all tenants from standalone to Automation Suite, extract the file and run the following command.Note:Make sure to add
TrustServerCertificate=True
for both source and destination SQL connection inputs../UiPath.OrganizationMigrationApp.exe migrate -a -m -s "<identity DB connection of MSI>" -d "<dentity DB connection of Automation Suite>"
./UiPath.OrganizationMigrationApp.exe migrate -a -m -s "<identity DB connection of MSI>" -d "<dentity DB connection of Automation Suite>" -
If the operation failed in the middle, roll back the change by running the following command:
./UiPath.OrganizationMigrationApp.exe migrate -a -m -r -s "<identity DB connection of MSI>" -d "<dentity DB connection of Automation Suite>"
./UiPath.OrganizationMigrationApp.exe migrate -a -m -r -s "<identity DB connection of MSI>" -d "<dentity DB connection of Automation Suite>" -
Fix the issue based on the error message and try to move the Identity data of all tenants from standalone to Automation Suite again.
-
After running the previous command, a new tenant named
tenant_xxxxxxxx
is created, wherexxxxxxxx
are random characters. This is the tenant to which you will migrate the standalone products.