![]() |
| |||||||
Automation Anywhere Post messages and questions related to Automation Software here. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
|
I have scheduled a task in the AA scheduler to run when my computer starts, but it does not do anything. I have verified the automatic login user name/password is correct, and the task runs when it is scheduled to run at a specific time when the computer is locked. The OS is Windows Server 2003 RS and it is AA 3.5.1. Any ideas? |
| |||
|
Hello, Auto-login feature of version 3.5.1 can only unlock the machine if machine is locked when scheduled task runs. From Automation Anywhere version 4.5, new Auto login model allows you to automatically login even if computer restarts. You can download free version of Automation Anywhere 5.0 from our website: Automation Anywhere - The Leading Automation Software Hope that helps. |
| |||
|
I downloaded a trial of AA 5.5. I made a simple task to delete as shortcut off the desktop and scheduled it to run at startup. In AA under current task schedules, it says the task is currently running, but nothing has happened.
|
| |||
|
Hello, May I please know if the same task works successfully if you run it manually? Can you create a simple task of opening notepad and writing in it and schedule it to run when computer starts. You need to enable 'Auto-Login' feature from to Tools->Options->Auto Login Settings. Check the checkbox which says: ‘Unlock your computer when scheduled task runs’ and provide the same username and password which you use to logon your computer. Click on apply and ok. Once you set the Auto Login option, it applies to all your tasks. Hope that helps. |
| |||
|
I created the notepad test job, and that works fine when ran manually. It also runs when scheduled to run at a specific time when the computer is locked, but stops at the evaluation pop up for the trial (the screen with the try it, enter key, and buy now! buttons). Next I scheduled the notpad test to run on startup, and didn't see the evaluation pop up after logging on. When I go into AA the status of the job is currently running. Could it be that the task is stopped waiting for a response to the evaluation pop up (I signed on with the credentials I entered into AA auto login)? Are there any logs to see what is happening? |
![]() |
| Thread Tools | |
| Display Modes | |
| |