I am having trouble opening up “Monarch” Application on the unattend machine when scheduling through the Orchestrator. On the Orchestrator, it shows success but nothing happens, the application does not open. It works fine if I open up the Studio and use the Start Activity (I have “C:\Program Files\Altair Monarch 2023\dwmonarch.exe”) and use the Debug file.
I am currently logging via remote desktop into the unattended machine. I also have the “Monarch” application installed locally into that RDP. I am not sure what the issue is but any help you can provide would be much appreciated.
Since you are running process in unattended mode. It might opening application. To know more about application state. You can add activity called on image/element appear. Once application launched check for mage/element appear & log the message with if-else block.
Other way is to take RDP of robot machine & try to run the process.
If you start application manually from a shortcut, please check if there are any app arguments that you are missing in your process. To check arguments go to properties of shortcut. Like in attached screenshot
I tried your suggestion and here is the outcome. It seems something with scheduling through orchestrator that it is not opening the application. It works perfectly on the local machine. What else can I do to fix this?
instead of debug, please run from studio from your machine. And then notice is there any behaviour difference?
when you are running from orchestrator on other machine. Please stay logged onto that machine and then kick off the run from orchestrator. This will help you notice what exactly is happening when process runs from orchestrator.
if you have studio installed on that remote machine, open studio and try running the process as you run on your machine.
Doing these steps will help you figure out the problem pattern.
Sorry for stupid question as I am new to UiPath. How would I check 2. The used used by robot has privilege to access that path? The Monarch application is also installed on the RDP machine CDCTVWAUIPATH03 which is what I am using when scheduling the unattended via Orchestrator.
Because you are using Start Process, it doesn’t know if the process actually started. It just issues the Windows command just like you would in a command prompt, and continues. You should be using Use Application/Browser, not Start Process.
I took out the start process and used the Use Application/Browser and still no luck. It does not open the application. I dont understand why it works fine through Debug File mode or attended mode on my local PC but not on the RDP machine. Any other suggestion would be much appreciated.
Also, I tried opening up word document (With Start Process and Without) and this does not work on the RDP machine so something is causing it to not launch any application (I even tried with the setting Always Open setting). Do you have any suggestions?
If you don’t install in Service mode and then try to run an unattended robot then UiPath cannot log into the machine the automation is supposed to run on and if the session isn’t logged in an active (as done by the Service) no screen will be rendered and so it cannot work with the Ui.
I’d expect that if you manually logged into the VM and kept the VM open and ran the task it would work, since then you are manually opening the VM and having it render cause you have the screen open.
To fix it you need to uninstall and install again, this time selecting the option to install via service mode, there are several tutorials on it,
Thank you everyone so much for your insight so after reviewing this further, the application is opening, however, it is using account UiPathTestB2 user and since I am logging in into the server CDCTVWAUIPATH03 as my self nikansagra_aa, it is not showing application opening but it does open/close as expected.
