![]() |
| |||||||
Automation Anywhere Post messages and questions related to Automation Software here. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
|
I have a task that opens an .exe that has been created with AA. The problem is that the tasks autologin the computer but it logs out when the task stops even when the .exe is still running. I have tried looping the task until the .exe finishes but it is causing me other problems. Is there another way to keep the session on until the .exe finishes? Can I change the screen saver to prevent it locking the session when my macro is running? |
| |||
|
I'm not sure this trick will work for you. But, I often have EXEs that need to run for many hours. I don't want to create a security hole by leaving a machine unlocked. I don't want to embed passwords in an ATMN to all login. So, I use a second machine to run the exe. I change the screen saver to never lock on the second machine. Then, I log into the second machine using remote desktop. I then start the exe. then lock the screen on the CONTROLING machine - while leaving the machine running the EXE unlocked. You could use a VIRTUAL machine as the second machine if you don't have a machine to use as the slave. Let me know if this helps. Phil |
| |||
| Quote:
1 - Depending on what that exe is doing it may cause something to be active (Excel spreadsheet, some text file, browser window etc). You can loop the parent task until that condition no longer exists. 2 - If not, as part of the exe the first step should be to create a blank text file somewhere. The last step should be to delete this text file. Then loop in the parent file while this text file exists. 3 - If your task involves querying anything from a database, you can place this query in the parent task and loop while whatever the condition is remains true. 4 - There are other ways like Phil was saying that involves modifying the security time-outs and such on the local PC but that is not an absolute depending on what your task is attempting to achieve. I recommend option 2 as the quickest and easiest solution. |
![]() |
| Thread Tools | |
| Display Modes | |
| |