发行日期：2022 年 8 月 3 日
改进
- Orchestrator 现在使用 ASP.NET Core 模块 6.0.6。
已知问题
-
When you delete a process that is associated to a trigger, that particular trigger is still displayed on the Search page, instead of being deleted along with the process. If you try to edit the trigger on the Search page, the "ProcessSchedule does not exist (#1002)" error is returned.
-
如果 SQL 证书不受 Orchestrator 计算机信任，或者无法从该计算机执行吊销检查，则用于将 Orchestrator 连接到 SQL Server 的
Microsoft.Data.SqlClient参数可能会导致升级或安装失败。在这种情况下，将显示以下异常：
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.)为防止发生这种情况，请采取以下措施之一：
-
If the connection string is using a hostname instead of an FQDN, update it to use an FQDN for SQL Server.
-
如果 Orchestrator 无法访问证书链中的服务器，从而导致吊销列表出现问题，请将
TrustServerCertificate=True添加到连接字符串中。请注意，某些较新的服务可能需要在连接字符串中专门声明这些服务，方法是通过命令行将更新的连接字符串作为参数提供给 MSI。
-
错误修复
-
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.
升级到此 Orchestrator 版本后，默认的“库”>“安全部署”设置为允许公开访问库。
对于全新安装的情形，默认的“库”>“安全部署”设置为仅允许经过身份验证的用户访问库。
-
现在，当从平台配置工具调用
Get-ChildItem -Path IIS:\SSLBindings时，会显示说明性警告消息Cannot determine ssl binding site name when ssl flags options are set.。出现此警告的原因是 IIS 问题，该问题会阻止在调用此参数时返回站点名称，无论在平台配置工具中选择了哪个 SSL 绑定标志。
以前，在此类情况下会显示不准确的错误消息
No SSL binding is used by UiPath Orchestrator.。