- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- 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 bucket
- 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 TX checksum offloading
- How to address weak ciphers in TLS 1.2
- 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
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- 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
- Cannot Log in 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 With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- 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
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Pods cannot communicate with FQDN in a proxy environment
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Configuring Microsoft SQL Server
Each product in Automation Suite requires its own SQL database with corresponding specifications.
By default, the installer creates all the databases for you during the installation process. You must provide the necessary permissions for the installer to do so on your SQL server.
Alternatively, you have the option to create your own databases. If you choose to bring your own databases for a new Automation Suite installation, we strongly recommend setting up new databases rather than using existing ones. This precaution is necessary to prevent any conflicts with the operation of Automation Suite that might occur due to leftover metadata from old databases.
The following table lists out the database names and their corresponding format.
Product / service |
Default database name |
Connection string format |
---|---|---|
Shared Platform Capabilities |
AutomationSuite_Platform | |
Orchestrator |
AutomationSuite_Orchestrator | |
Automation Hub |
AutomationSuite_Automation_Hub | |
Data Service |
AutomationSuite_DataService | |
Insights |
AutomationSuite_Insights | |
Test Manager |
AutomationSuite_Test_Manager | |
Task Mining |
AutomationSuite_Task_Mining | |
AI Center |
AutomationSuite_AICenter | |
Document Understanding |
AutomationSuite_DU_Datamanager |
If you manually set the connection strings in the configuration file, you can escape SQL, JDBC, or ODBC passwords as follows:
- for SQL: add
'
at the beginning and end of the password, and double any other'
. - for JDBC/ODBC: add
{
at the beginning of the password and}
at the end, and double any other}
.
You could use the databases in an elastic pool for better cost-effectiveness.
In the case of Apps, you cannot bring your own MongoDB.
SQL_Latin1_General_CP1_CI_AS
at both the server and database level. We strongly recommend this particular setup for optimum performance and stability.
While you have the flexibility to use a collation of your choice, be aware that untested configurations can potentially lead to unexpected issues.
We do not recommend the use of Binary SQL or any collations that are case sensitive, as they cause known issues while installing Automation Suite.
dbcreator
role to the SQL account used to connect to the database.
db_owner
and db_securityadmin
roles for all Automation Suite databases.
db_owner
, then the SQL account should have the following roles and permissions on all databases (the only exception is Insights which
still requires db_owner
).
db_securityadmin
db_ddladmin
db_datawriter
db_datareader
EXECUTE
permission on dbo schema
db_securityadmin
and db_ddladmin
roles during installation or if the databases are reprovisioned, so you may revoke these permission afterwards.
Document Understanding requires the SQL Server to have the Full-Text Search component of the SQL Server Database Engine, which is not always installed by default.
If you did not select Full-Text Search when you installed SQL Server, run SQL Server Setup again to add it before configuring Document Understanding.
For more info, check this guide on how to add/install features on SQL server. You can also check here all the components that can be added to the SQL Server, which includes also Full-Text Search.
.json
functions.
For Azure SQL, ensure the database is S3 service objective or above.
Make sure the compatibility level for Insights database is set to 130 or higher. In most cases, the default settings meet this requirement. For more info, refer to View or Change the Compatibility level of a Database - SQL Server.
The installation validates both conditions and alerts you if minimum requirements are not met.
Data Service requires SQL Server version 2016 or higher.
If you create your own database using SQL Server version 2019 or higher, make sure to grant the following Data Service permissions to your users:
GRANT ALTER ANY SENSITIVITY CLASSIFICATION TO {userName};
GRANT VIEW ANY SENSITIVITY CLASSIFICATION TO {userName};
GRANT ALTER ANY SENSITIVITY CLASSIFICATION TO {userName};
GRANT VIEW ANY SENSITIVITY CLASSIFICATION TO {userName};
For a high-availability configuration of your SQL Server, select an Always On availability group. For more info, refer to Overview of Always On availability groups.
READ_COMMITTED_SNAPSHOT
option is set to ON
.
READ_COMMITTED_SNAPSHOT
is enabled or
disabled:
SELECT is_read_committed_snapshot_on FROM sys.databases
WHERE name= 'UiPath'
SELECT is_read_committed_snapshot_on FROM sys.databases
WHERE name= 'UiPath'
1
.
0
. Use this query to
enable it:
ALTER DATABASE UiPath
SET READ_COMMITTED_SNAPSHOT ON
ALTER DATABASE UiPath
SET READ_COMMITTED_SNAPSHOT ON
READ_COMMITTED_SNAPSHOT
must be enabled on those as well.