Question

Robotic Processing Automation Scheduling service couldn't start

Hi guys, I try to deploy an RPA in a server machine, I already do everything in this post: https://community.pega.com/knowledgebase/articles/robotic-processing-automation-scheduling-service.

But the login never happened, looking for some log file, I found this 'WinLogon.Scheduler.log':

  1. Machine Name: <TheMachineName>
  2. Assembly Name: Pega.Exceptions.BaseApplicationException, Pega.Interop, Version=10.0.0.0, Culture=neutral, PublicKeyToken=f5db91edc02d8c5e
  3. Application Domain Name: OpenSpan.WinLogon.Scheduler.exe
  4. Thread Identity:
  5. Windows Identity: NT AUTHORITY\SYSTEM
  6.  
  7. Stack Trace:
  8. at OpenSpan.WinLogon.Scheduler.LogonEngine.Logon(LogonMode mode)
  9. at OpenSpan.WinLogon.Scheduler.LockScreenLogonProcessor.Logon(String userName, String password)
  10. at OpenSpan.WinLogon.Scheduler.SchedulerProgram.UnlockScreenAndLogon(String userName, String password)
  11. at OpenSpan.WinLogon.Scheduler.SchedulerProgram.Main(String[] args)
  12. 2018-12-13 07:34:35 PM - INFO – [1] - *** Initializing ***
  13. 2018-12-13 07:34:35 PM - INFO – [1] - Initialized
  14. 2018-12-13 07:35:03 PM - ERROR – [1] - Exception Type: Pega.Exceptions.BaseApplicationException
  15. Message : Logon engine - session configuration not found matching current OS version, session SignIn mode and Local user type.
  16. Time Stamp : 13/12/2018 7:35:03 p. m.
  17. Source : OpenSpan.WinLogon.Scheduler
  18. Method : Boolean Logon(OpenSpan.WinLogon.Scheduler.Configuration.LogonMode)
  19.  
  20. Machine Name: <TheMachineName>
  21. Assembly Name: Pega.Exceptions.BaseApplicationException, Pega.Interop, Version=10.0.0.0, Culture=neutral, PublicKeyToken=f5db91edc02d8c5e
  22. Application Domain Name: OpenSpan.WinLogon.Scheduler.exe
  23. Thread Identity:
  24. Windows Identity: NT AUTHORITY\SYSTEM
  25.  
  26. Stack Trace:
  27. at OpenSpan.WinLogon.Scheduler.LogonEngine.Logon(LogonMode mode)
  28. at OpenSpan.WinLogon.Scheduler.LockScreenLogonProcessor.Logon(String userName, String password)
  29. at OpenSpan.WinLogon.Scheduler.SchedulerProgram.UnlockScreenAndLogon(String userName, String password)
  30. at OpenSpan.WinLogon.Scheduler.SchedulerProgram.Main(String[] args)
  31. 2018-12-13 07:35:36 PM - INFO – [1] - *** Initializing ***
  32. 2018-12-13 07:35:36 PM - INFO – [1] - Initialized
  33. 2018-12-13 07:35:36 PM - INFO – [1] - <TheMachineName>\Administrator screen unlock is unsuccessful

Butt in the 'SheduleDefinitions.xml' file exists a configuration for my OS 'Windows Server 2012 R2':

  1. <Session name="Windows Server 2012 / 2012 R2" version="6.2;6.3" type="Server" userType="Domain" wait="750">
  2.  
  3. <!-- optional disclaimer -->
  4. <MatchSet name="Disclaimer" mode="SignIn" matchSuccess="Continue" matchFailure="Stop" enabled="true">
  5. <Match type="PushButton" name="OK">
  6. <Action type="execute" />
  7. </Match>
  8. </MatchSet>
  9.  
  10. <!-- optional busy message -->
  11. <MatchSet name="Busy" mode="SignIn" matchSuccess="Continue" matchFailure="Continue">
  12. <Match type="ProgressBar" name="Busy indicator">
  13. <Action type="wait" value="5000" />
  14. </Match>
  15. </MatchSet>
  16.  
  17. <!-- previously logged in user -->
  18. <MatchSet name="LoginLastUser" mode="SignIn" matchSuccess="Stop" matchFailure="Continue">
  19. <Match type="StaticText" name="[UserName]" />
  20. <Match type="Text" name="Password">
  21. <Action type="set" value="[Password]" />
  22. </Match>
  23. <Match type="PushButton" name="Submit">
  24. <Action type="execute" />
  25. </Match>
  26. </MatchSet>
  27.  
  28. <!-- switch to other user -->
  29. <MatchSet name="LoginSwitchUser" mode="SignIn" matchSuccess="Stop" matchFailure="Continue">
  30. <!-- switch user button is available after reboot only, when Group Policy "Do not display last user name" is disabled -->
  31. <Match type="PushButton" name="Switch User" optional="true">
  32. <Action type="execute" />
  33. </Match>
  34. <Match type="Link" name="Other User">
  35. <Action type="execute" />
  36. </Match>
  37. <Match type="Text" name="User Name">
  38. <Action type="set" value="[UserName]" />
  39. </Match>
  40. <Match type="Text" name="Password">
  41. <Action type="set" value="[Password]" />
  42. </Match>
  43. <Match type="PushButton" name="Submit">
  44. <Action type="execute" />
  45. </Match>
  46. </MatchSet>
  47.  
  48. <!-- logged in user unlock -->
  49. <MatchSet name="Unlock" mode="Unlock" matchSuccess="Stop" matchFailure="Stop">
  50. <Match type="StaticText" name="[UserName]" />
  51. <Match type="Text" name="Password">
  52. <Action type="set" value="[Password]" />
  53. </Match>
  54. <Match type="PushButton" name="Submit">
  55. <Action type="execute" />
  56. </Match>
  57. </MatchSet>
  58.  
  59. </Session>

Also found records for another Windows versions, I don't know if I need delete them and leave only the records for my OS.

I must to say, if I manually login and wait for the scheduled time, nothing happend, but if I manually open the 'Pega Runtime' and load the '.openspan' file all the automation work just fine, the ploblem is in the schedule.

***Edited by Moderator Marissa to update SR Details***

Group Tags

Correct Answer
December 27, 2018 - 11:41am

This question is linked to SR-C81711.

ROOT CAUSE

When setting up the credentials for Login, the default "Local" userType was used (signified by a period for the Domain). This caused an issue because the SchedulerDefinitions does not have an entry with a userType=Local.

RESOLUTION

SchedulerDefinitions.xml file in the installation folder was edited. The configuration for the userType was changed from userType="Domain" to userType="Local". 

Alternatively, the credentials could have been changed to use a Domain.

Comments

Keep up to date on this post and subscribe to comments

Pega
December 27, 2018 - 11:41am

This question is linked to SR-C81711.

ROOT CAUSE

When setting up the credentials for Login, the default "Local" userType was used (signified by a period for the Domain). This caused an issue because the SchedulerDefinitions does not have an entry with a userType=Local.

RESOLUTION

SchedulerDefinitions.xml file in the installation folder was edited. The configuration for the userType was changed from userType="Domain" to userType="Local". 

Alternatively, the credentials could have been changed to use a Domain.