- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- 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 disable TLS 1.0 and 1.1
- 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 debug failed Automation Suite installations
- How to disable TX checksum offloading
- 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
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- 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).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- 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
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- 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 can 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 | |
|
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.
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_securityadmindb_ddladmindb_datawriterdb_datareaderEXECUTEpermission on dbo schema
db_securityadmin and db_ddladmin roles during installation or if the databases are reprovisioned, so you may revoke these permission afterwards.
Automation Hub and Document Understanding require 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 Automation Hub tenants and 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.
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 ONALTER DATABASE UiPath
SET READ_COMMITTED_SNAPSHOT ONREAD_COMMITTED_SNAPSHOT must be enabled on those as well.
