![]() |
![]() |
We are currently migrating this forum over to our HelpSystems domain. Please post all new threads in our new HelpSystems Community Portal. |
![]() |
|
![]() |
AutoMate Discussion | ![]() |
Topic Title: Step#0 - Could not start because the computer could not be unlocked Topic Summary: Created On: 07/25/2018 11:54 AM Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi Everyone,
Lately my automate jobs have been failing due to the following error: 'Could not start because the computer could not be unlocked.' We have a domain user account strictly for running jobs, and it's rare that people logon with that user account. On the automate job itself, I have the following Task Logon options: When workstation is logged on: Logged on user When workstation is logged off: Logon specified user When workstation is locked: Logon using specified user Looking to see if anyone can point out what other settings or scenarios might be causing this to happen. Thanks, |
|
|
|
![]() |
|
Hello Romel,
How are you connecting to the machine in question? Are you using RDP? If so are you logging off from the Start menu or are you closing the RDP window by clicking on the X? Make sure to log off from the Start Menu. ------------------------- ![]() Ricardo Castaneda | Principal Support Analyst AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 |
|
|
|
![]() |
|
Hi Ricardo,
Thank you for the response. Yes, we are remoting in via RDP into the server that Automate 11 is installed in. Is the message 'Could not start because the computer could not be unlocked' due to that particular user being logged into the server? |
|
|
FuseTalk Enterprise Edition v4.0 - © 1999-2019 FuseTalk Inc. All rights reserved.