Issue in 2018.1, when we start debugging it shows message "Cannot start a job in 'debug' mode for a non-development robot"

18_1

#1

when we start debugging it shows message “Cannot start a job in ‘debug’ mode for a non-development robot”. so unable to debug any workflow…


#2

you have to be connected to orchestrator as a Development robot.


Development Robot in 2018.1
#3

but just for debugging why it is required to connect to orchestrator. earlier to update it was working without any problem


#4

one second, are you connected to orchestrator when doing the debug?


#5

not connected


#6

were you connected to any orchestrator? before the update?


#7

no, i am not using orchestrator


#8

are you trial or using a license key


#9

its community edition


#10

so you are still in the Free (trial) period, you did not bought a valid license?


#11

i am using community edition for learning purpose does it require license?


#12

let me investigate


#13

if you delete the content of C:\Users\YOURUSER\AppData\Local\UiPath\License and restart Studio, then use Start Free, is it working?


#14

followed steps still same problem


#15

When you ve started Studio after deleting the License files, were you asked to Start free again and enter your email address?


#16

Hey @govind ,

If you are still facing problem for debugging any robot, then do as below mentioned.

From task manager under application tab end task of “UIPath Robot User Service” and then try to debug any robot.


#17

Thanks, its working.


#18

I am experiencing the same issue in 2018.1.
Yes, killing the UIRobot task does the trick, but in the background UIRobot starts automatically again. Having to kill UIRobot every time before I go into debug mode does not seem a proper solution. Is this a 2018.1 bug and if so, is UIPath going to do something about it? Or is it a user specific (me) problem and I have to live with workarounds?


#19

Were you ever connected to orchestrator before upgrading to 2018.1 ? this error appears in 2018.1 if you are connected to orchestrator and you are not provisioned as Development Robot
if you start uirobot.exe from installation folder, and then open robot tray->settings do you see anything?


#20

I was connected before indeed and when I start UIRobot from the right folder then it shows my robots deployed on Orchestrator. My robot on Orchestrator is NonProduction and I cannot seem to change it to Development due to licensing issues.

Have tried to remove my robot on Orchestrator and create a new one, but the only one working is NonProduction and then again I have my debugging issues.

Any help appreciated.