Hi,
Just spent the past few hours trying to resolve the above message and couldn't find an easy solution, so when I solved it I thought I would share the solution in case anyone else comes across the same problem.
When running the below process I would get an error like the one below when running it as a session in the Control Studio. Running it in Debug worked fine.
My solution was to create a blank process which linked firstly to the Orchestrator and then published it. Then I tried to run it on one of the workers. I knew this would give the above error so this was really just a sense check. Then removed the Orchestrator and added the Conductor, then repeated the process with the Collector, and finally the Executor. The Executor also gave the error but the Collector did not, so I knew the legacy link had to be in part of this process. I edited the Test Process and linked it to each of the components run by the Executor, until I found the Component which gave the error. Finally I added each of the Object pages referenced by the component in turn until I found which page was causing the error. Then I just looked at each Action on the page and found the legacy link.
I'm sure there must be an easier way to find this, but the Dependancies didn't show which Object had the links and I didn't want to manually go through every single page.
I hope this helps someone.
------------------------------
Paul Wyman
------------------------------
Just spent the past few hours trying to resolve the above message and couldn't find an easy solution, so when I solved it I thought I would share the solution in case anyone else comes across the same problem.
When running the below process I would get an error like the one below when running it as a session in the Control Studio. Running it in Debug worked fine.
"Failed to create session on [MACHINENAME] - Failed to get effective run mode - Unable to calculate run mode - object [OBJECT] does not exist"
Clearly there is a legacy OBJECT which is referenced in the Process> Components> Objects, somewhere but where do you start to find it? As I had copied quite a lot from other Processes I wanted to find a quick way to narrow it down.
My solution was to create a blank process which linked firstly to the Orchestrator and then published it. Then I tried to run it on one of the workers. I knew this would give the above error so this was really just a sense check. Then removed the Orchestrator and added the Conductor, then repeated the process with the Collector, and finally the Executor. The Executor also gave the error but the Collector did not, so I knew the legacy link had to be in part of this process. I edited the Test Process and linked it to each of the components run by the Executor, until I found the Component which gave the error. Finally I added each of the Object pages referenced by the component in turn until I found which page was causing the error. Then I just looked at each Action on the page and found the legacy link.
I'm sure there must be an easier way to find this, but the Dependancies didn't show which Object had the links and I didn't want to manually go through every single page.
I hope this helps someone.
------------------------------
Paul Wyman
------------------------------
