automation-suite
2024.10
false
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- Installation fails when Velero is enabled
- Issue with connecting to the Multi-AZ database server
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Last updated Nov 13, 2025
You get the
Connecting to a mirrored SQL Server instance using the
MultiSubnetFailover connection option is not supported error when
connecting to Multi-AZ database while using the
MultiSubnetFailover=True parameter in the connection
string.
To fix the issue, you must ensure that you are using the listener endpoint and not the normal endpoint.
Note: If you try to connect to the normal endpoint without the
MultiSubnetFailover=True parameter in the connection
string, this could lead to issues.
If you are using a Multi-AZ with Always On SQL setup, more details about the options for RDS can be found in Amazon documentation for Multi-AZ deployments for Amazon RDS for Microsoft SQL Server.
