Posted: 22 Nov 2018 6:59 EST Last activity: 22 Nov 2018 10:32 EST
Domain Issues while using Robotic Processing Automation Scheduling service
I am trying to setup Robotic Processing Automation Scheduling service in which i am succeed till the step when Task is created in the Task Scheduler on the name of Windows user from credential Store.
When the Task run it will try to start the runtime for which it will use the runtime credentials strored in the credential Store utility but i havent provided the domain name while storing it as i dont know what it should be as i have seen only the operator id with the Id and password without any domain. Please help me what should i use in place of domain to correctly authenticate the runtime user with the pega platform
Where did you get credentials for Runtime? If you are able to login into Windows session with these credentials then you can run the following command in command line (cmd.exe) to get current domain name:
Pega Robotic Automation Credentials Manager utility to store the Windows user and Robotic Automation Runtime user
Now here is the current Problem statement:
I have a VM on which i have installed the Pega Robotics Runtime,I have a Company domain UserName which is used to login into VM and act as a Window user.
i have a pega platform in which i have created a Operator ID which i will be using on this VM to start the Runtime, Since i am scheduling to start the Runtime using RpaSchedule.json at a specific time using the Scheduler service, i have to save this Operator ID as a Robotic Automation Runtime user in Pega Robotic Automation Credentials Manager utility for which it is asking me to specify a domain for Runtime User but i dont know what should i specify because for window user name i already have but for the Runtime User which is a operator ID i created in Pega i dont have that. All configuration is right but just the domain issues are stopping me to launch the Runtime at a specific time. Below is the Error Logs when service tries to start the Runtime though if i manualy provide the Runtime User to Start the Runtime these credentials work that means the domain must be an issue
2018-11-22 04:43:47 AM - DEBUG –  -Runtime user domain: xxxx
2018-11-22 04:43:47 AM - DEBUG –  - Runtime user name: xxxx
2018-11-22 04:43:47 AM - DEBUG –  - Runtime user password: -provided-
2018-11-22 04:43:47 AM - DEBUG –  - Launch Runtime
2018-11-22 04:43:47 AM - ERROR –  - Failed to launch Runtime: error 1326
2018-11-22 04:43:47 AM - ERROR –  - System.ComponentModel.Win32Exception (0x80004005): The user name or password is incorrect
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at OpenSpan.WinLogon.Launcher.LauncherProgram.LaunchRuntime(String domain, String userName, String password, String runtime)
at OpenSpan.WinLogon.Launcher.LauncherProgram.Main(String args)
Thank you for the details. Let me try to clarify a little bit.
There are actually three credentials sets involved into startup sequence here.
1. Credentials for login into Windows user session used by RPA Scheduler Service. It is stored with "--windows" parameter in the Credentials Manager utility. Looks like this step works for you without issue.
2. Credentials used to start Runtime process. These are also Windows credentials like in step 1. This is not a Pega user credentials. It is stored with "--runtime" parameter. If you omit domain name or specify "." then local machine is implied. If you omit this credentials set entirely, Runtime is started under logged in user (in other word with credentials specified in step 1).
3. RPA registration credentials set. This is Operator ID created in Pega for initial Runtime registration. This is not Windows session user credentials. You enter it first time when robot starts into Enter RPA credentials window. It is stored outside of Credentials Manager utility, in %appdata%\OpenSpan\RPAStartup.info file. After initial registration, robot works using auto-created Operator ID which name equals machine name.
As far as I see your issue, step 2 credentials are incorrect. If you are able to specify credentials for Runtime service manually, please try to actually log in into Windows user session using the same credentials that you provides manually and verify which domain value is in there. Then update the credentials set in Credentials Manager utility. Or just try to delete "--runtime" credentials set and see if robot starts using just "--windows" credentials.