The executor stopped working message keeps popping out whenever I stop a debugging/running robot(which has no bug and deployed robot), running processes via assistant or orchestrator, or after a robot completes process(whole process is successful).
@PatrickChu Check the .net version once and confirm if this is installed on service mode or user mode .
Also if it is virtual machine or local laptop and the version of studio
@rajat.jain it is on vm and user mode. I am not sure how to check .net version, but I am using vb windows compatibility, and the robot are fine a couple days ago.
Edit: I found out the .net framework version is 4.8 on vm.
The event viewer log helped me to find out the error.
As the robot adopted the InitAllSettings part from the REFramework, I put some assets on the default folder(my workspace) on the orchestrator. However, the get asset function is reading null value(empty cell from my local config file) on the AssetFolder column as I wanted the function to get the default folder.
Your workspace is a modern folder and when using the âGet Orchestrator Assetâ activity in a modern folder you have to supply the modern folder name (in your case your workspace name) in the Asset Folder Column in the Asset sheet of your config file.
U can use the folder path option in the properties to set a path or as i understand u have asset defined in config file before doing get asset there should a loop for excel sheet from which it is reading the name and using that name it is getting the asset
Just to be clear you have some asset in orchestrator and some values in config.xlsx
Version of Orchestrator is not sure, but I am using orchestrator on browser + community license so I think it should be 2022.10
2.âstudioVersionâ: â22.4.3.0â,
3.âdependenciesâ: {
âUiPath.Excel.Activitiesâ: â[2.16.0]â,
âUiPath.System.Activitiesâ: â[22.10.3]â,
âUiPath.UIAutomation.Activitiesâ: â[22.10.3]â
},
If you are using the community license your studio is auto updated, not sure why you are using an older version of the studio.
I recommend you to upgrade your studio to the latest stable version (2022.10.3). Itâs a best practice to ensure your studio version matches the System & UIAutomation dependacy versions.