- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- Installation fails when Velero is enabled
- Issue with connecting to the Multi-AZ database server
- Prerequisite checks fail when Document Understanding modern projects is enabled and AI Center is disabled
- 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
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Issue with connecting to the Multi-AZ database server
Solutions for Multi-AZ database connection failures in Automation Suite on EKS/AKS.
Description
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.
Solution
To fix the issue, you must ensure that you are using the listener endpoint and not the normal endpoint.
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.