As my m/c has no separate userid or password to login windows, i used admin as userid as default and no password required to login. In this scenario , how can i configure robot in Orchestrator. Do i need to give blank password. I could not able to run the job, as status showing pending due to unavailability of resource allocation #1670. What is the best way to to resolve this issue
@mbegum
you can just mention the machine, robot name and domain alone while you are creating the robot here and you can get your domain by typing this start->cmd
as
systeminfo | findstr /B /C:“Domain”
@mbegum
Kindly try this and let know whether this works or not
Cheers
did that work buddy @mbegum
Any issue still … @mbegum
Hi,
Had tried all means. Had created new tenant as well and did all configuration . Had also setup windows domain and password . Eventhen job is not starting. it is in pending state. One more thing i noticed. When i was setting up ROBOT, i had given my windows domain password which is 4 letter. After i created robot with all those details, i verified them again by viewing the details. password tab with more digits is showing automatically. I dont know where it is pulling from. Cant able to view the password in that tab eventhough i tried to unhide.
And aslo domain name shows WORKGROUP as per ur suggestion. I tried with that also. When i typed whoami in cmd, it shows ‘admin’ which is my windows login id
i tried in all the ways., but in vain
See my job status . This is what showing up when i tried in all ways. Eg, With WORKGROUP as domain id, With admin as domain id ., tried in new tenant as well after publishing freshly the process
I have BIOS password for my m/c. Will that impact this one
no worries…
Try with workgroup as domain and remove the password and keep it empty …as you said you don have any password been set.initially…and the remaining all same…
Try this and let know
Cheers… @mbegum
I tried … but of no use
Actually after i updated as per ur instruction, i reopened it to view the data, its showing like this
Password tab is not in blank status rather some password exist there . seethe attachment. Unable to view that data as it is in hide status I dont know wheere it is automatically pulling from
see my job status
Now robot is showing unresponsive status. Earlier it was in available status
You were almost done
Kindly have a view on this buddy
Cheers @mbegum
Cheers @mbegum
Hi, I had the same problem,“job for process orchestrator on robot demorobot failed#1680” and then I removed the robot and created another one with a generic password(not related to system user or something) and it works.
Right now I am taking the Orchestrator course but I don’t know if this is ok for future cause that generic password should influence a project.
I am still getting Error - Folder Default: #trigger… Undefined robots (#1678) … I have tried to put my password in Robot, but there is no Password available for Studio in robot. please help me t fix the issue
Regards,
Ahishek
Is the robot is assigned to any environment
Kindly check that once
It was actually in unattended type of robot
Isn’t it
@Jain_Abhishek