Release date: 3 August 2022
Microsoft.Data.SqlClient parameter used to connect Orchestrator to SQL Server can cause upgrades or installs to fail in case of SQL certificates that are not trusted by the Orchestrator machine or whose revocation check cannot be performed from that machine.
The following exception is displayed in such cases:
System.Exception: Error:-1, Message:An error occurred while retrieving latest migrations. Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.)
To prevent this, apply one of the following measures:
- If the connection string is using a hostname instead of an FQDN, update it to use an FQDN for SQL Server.
- If Orchestrator cannot reach the servers in the certificate chain, causing revocation list issues, add
TrustServerCertificate=Trueto the connection string.
Note that certain newer services might require these to be specifically declared in the connection string by feeding the updated connection string as an argument to the MSI through the command line.
- Page numbers and sequences were displayed incorrectly in the Manage Administrator Users page.
- Orchestrator threw an “Invalid authentication token” error (
Error code - 1431), which caused an infinite loop in the browser after a session inactivity timeout.
- Accessing the Orchestrator Host Feed in Studio resulted in the following error: “Failed to retrieve metadata from source”. This happened because the Libraries > Secure deployment setting and the corresponding value in the Orchestrator database were opposite.
Upon upgrading to this Orchestrator version, the default Libraries > Secure deployment setting is to allow public access to the libraries.
For fresh installs, the default Libraries > Secure deployment setting is to allow only authenticated user to access the libraries.
Click to learn more...
This version of Orchestrator is available in two deployment models:
- standalone Orchestrator
- Orchestrator service which is part of Automation Suite
The product is similar enough across deployment types to share the same documentation.
But differences do exist. When certain information applies to only one of the deployments, we use the following labels:
- - only applies to standalone Orchestrator and does not apply to Automation Suite Orchestrator.
- - only applies to Automation Suite Orchestrator and does not apply to standalone Orchestrator.
Whenever there is no label, the information applies to both deployment types.
Updated 5 days ago