Error while invoking UIRobot.exe from command prompt

robot

#1

i am getting the below error while invoking UIRobot.exe from command prompt.
Logon failure: unknown user name or bad password.
The command i am using is:

“C:\Program Files (x86)\UiPath Platform\UiRobot.exe” /file:“C:\Users\user1\Documents\UiPath\zoro1\c123.xaml” /input:"{‘arg1’:‘hello’}"


#2

@nagakula
did you tried with this following path:
C:\Users<userName>\AppData\Local\UiPath\app-2017.1.63\UiStudio.exe
please check … this path will work from Run command as well as from command prompt.

Hope my inputs are useful.


#3

i tried this and command executed successfully.
But nothing comes up as in the robot is not doing the actions or activities mentioned in the xaml.
But i could see UIRobot.exe process running in task manager.


#4

did you login into OR ( https://platform.uipath.com ) and configured your business case with machine ?
if not please configure.


#5

I am running in my local machine where i have developed the xaml file.
Could you please help me understand why do we need to configure it in OR as i am just trying it in my local machine.


#6

oh ok … it’s my mistake… You have to create your script in your local and publish it from the Setup tab.
next open UiRobot.exe and it will start visible in System tray.
click on that icon and click on settings. you will find following dialog.
image

when you open this icon you will be able to view the status as follows:
image

hope my inputs are useful


#7

Hi! What kind of activities are in your workflow? Maybe this guide will help with the arguments:

Also, i’ve tested different types of workflows(UiAutomation, excel…) and the robot runs and i can see executing the activities(without being connected to orchestrator)


#8

its just the ping monitor.xaml available in the path “C:\Program Files (x86)\UiPath Platform\Library\Samples”.

I tried several options to run from command prompt but it simple gives me the below error. I am running 2017.1 now.


#9

There must be some simple access issue which i am trying to figure out but no luck till now :slight_smile:


#10

Hey, were you able to solve the issue?