Hi Everyone, I seem to be getting errors when starting jobs via the Orchestrator: *Could not start executor. * A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520) Had a look through the threads and tried various fixes (incl. the Tim…

Thank you, we found the culprit. During the weekend an application (CA Identity Manager) was installed on virtual machines that enforced double password entry when using RDP to connect to the VDIs. Uninstalling the app solved the issue. :slight_smile:

Orchestrator job fail - Could not start executor HRESULT: 0x80070520

Help

loginerror (Maciej Kuźmicz) July 29, 2019, 2:43pm 2

Hi @Ekat

Welcome back!

Please see here for a possible solution:

Topic		Replies	Views
Could not start executor. A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520) Help orchestrator , bug	1	1633	November 19, 2019
Executor start process failed; A specified logon session does not exist. It may already have been terminated Help robot	15	12137	April 25, 2022
System.Runtime.InteropServices.COMException (0x80070520) A specified logon session does not exist 0x80070520 - Troubleshoot Steps Help orchestrator	4	13372	June 14, 2019
Could not start executor. A specified logon session does not exist. It may already have been terminated Orchestrator orchestrator , question	15	10261	May 27, 2024
Orchestrator からプロセスの実行が失敗する。(Exception from HRESULT: 0x80070520) フォーラム	3	3037	December 8, 2021

Orchestrator job fail - Could not start executor HRESULT: 0x80070520

Related topics