As a background, my team was moving from one Orchestrator Host to another Orchestrator. In doing so we moved from 2020.4.2 to 2020.4.1.
I built my original process in UIPath Studio 2020.4.3
For an unrelated issue we were facing with updating packages using the myget public feed, I tried to uninstall UiPath (Studio and Robot) and reinstall with the latest version 2020.10.2.
This didn’t solve my package updating error but I saw that it also caused another issue to my process. After publishing the same process using UiPath Studio 2020.10.2, I no longer could no longer start Orchestrator jobs for that process.
Issue with Multiple Points…
I saw a previous post of reverting back to 20.4.3 (which honestly is a really terrible design thing if 2020.10.2 published processes caused this error. I then uninstalled and reinstalled 2020.4.3 UiPath Studio and republished my process. Nevertheless I got the same issue when trying to start a job via manual or trigger.
I’m very stuck now, as I can’t seem to run my process via Orchestrator at all.
Other information:
I’m connected and licensed (I also installed the legacy robot runner)
Sometimes you might want to define which workflows should behave as an entry point to your process. So instead of having just the Main file, you can now define as many entry points as you want. Once published, you can use an entry point via Invoke Process and Run Parallel Process. When opening a process built by others, you instantly see what was defined as an entry point. Support in Orchestrator is not ready in 20.10, but you can start using this feature to logically map your entry points starting now.
Here is the some text of my json project file if that helps (I wonder if we can just delete parts of JSON to fix this):
“expressionLanguage”: “VisualBasic”,
“entryPoints”: [
{
“filePath”: “Main.xaml”,
“uniqueId”: “90e9302a-bdd0-42e3-98d8-d7ed36792bc9”,
“input”: ,
“output”:
}
]
}
I
I’m also unable to even enable or disable Entry points in the UiPath Studio (I’m guessing because it’s not in 20.4.3)
I have this same problem, did you find a solution for it?
We moved code from a 2020.10 instance to a 2020.4 and it won’t run from Orchestrator. They have a previous post about this but all it says is : The fix for this was done in the latest 20.4 patch. If you want to continue using Studio 20.10 with Orchestrator 20.4, you will need to upgrade Orchestrator to the latest patch. Alternatively you can continue to use Studio 20.4 with your current version of Orchestrator.
Hi everyone, I have the same problem, I’m trying to export my 2020.10 Code into a 2020.4 Re-Framework Template by importing my Workflows and remapping the arguments, is there any other way to do this? this seems to work on a simple Workflow (sample task of Loading a Queue Item) but for a bigger and more complex automation it has became really difficult to do the same workaround.
Also have this issue. Thought it came from 2020.10 Community version to 2020.4.1 (orchestrator), but now seeing same issue in 2020.4.3 Studio and 2020.4.1 Studio created packages.
Method that worked before (for 2020.10) was deleting project.json and recreating it in a 2020.4.3 studio. Hoping to hear of a better solution here!
so we deleted the project.json from the project folder and then opened the xaml. it recreated the project.json and then we added the package dependencies for activities manually. it seemed to work for transferring projects from community, but I have not had the same luck from 2020.4.1 to 2020.4.3… will let you know what I find out
20.4.3 was used in Studio. I’ve fixed this issue by specifically copying and pasting only the .xaml files I had onto the new black project process. The new process was named differently and published to the Orchestrator.
I will upgrade my Orchestrator to 20.10 soon and hope to update on what happens (whether my old process will run fine without having to have create a new process and project.json entirely)
your advice about the “multiple entries” section in the project.json worked for me. I deleted just that entry in the json and it no longer creates the error. Make sure to also get the , after the language used and save it properly before creating a package:
In addition to removing the "entryPoints" section of project.json, we found that we also needed to downgrade the UiPath.UIAutomation.Activities package to a version compatible with the Orchestrator version we were using.
For Orchestrator 20.4.x, the UIAutomation package should be downgraded to 20.4.3. As Studio doesn’t like you downgrading dependencies in the application itself, we had to manually edit the version of UiPath.UIAutomation.Activities in the project.json file while Studio was closed. Once you do this you should make sure to validate the project (“Analyze File” dropdown → “Validate Project”) to ensure that any activities broken in the downgrade get pointed out to you.
Anil_G
jast1631
donghai
gulsheen_kaur1