WinWaitActive?

[krokkie]

I have a job that runs as a scheduled task, but because I have other apps runing on the server, it seems to stop at the login prompt.

When you click on it, it then proceeds to run the job without problems.

This is the part of the script that causes the issue:

;Sign In

WinWaitActive("Dispatch Manager Sign In")

Send($Pwd & "{Enter}")

WinWaitActive("classname=TMessageForm")

;MsgBox(0,"Purge Disabled Records","TMessageForm")

Send("{Enter}")

; ExitDM()

I tried changing the second WinWaitActive to WinActive, but it still fails

If I change bot to WinActive, it does not carry on with the job

What command do I use to force the login prompt to always be active, no matter what other apps are running?

[Varian]

Have you tried a simple Activate/Wait util Active loop?

Do
  WinActivate("classname=TMessageForm")
  Sleep(10)
Until WinActive("classname=TMessageForm")

Edited February 6, 2013 by Varian

[Exit]

;Sign In

WinWaitActive("Dispatch Manager Sign In")

Send($Pwd & "{Enter}")

WinWaitActive("classname=TMessageForm")

Second Winwaitactive has a systax error. Should read:

WinWaitActive("[classname:TMessageForm]")

[krokkie]

I will try both suggestions and report back.

Thanks for your responses

[krokkie]

Your suggestions work fine, until I disconnect my RDP console session to the server.

The schedule task starts but gets stuck on the login screen again

[BrewManNH]

It's probably because the windows aren't active if you're not connected/logged in to the server

[jdelaney]

Are you always logged in when this runs?

If not, then you will not be able to make the window active.

http://www.autoitscript.com/wiki/FAQ#Why_doesn.27t_my_script_work_on_a_locked_workstation.3F

Using WinExists will work (loop until it does), and then wait for the WinGetState to include is visible, and is enabled...then use controlsend instead of send

Edited February 7, 2013 by jdelaney

[krokkie]

What is the best way to get this script to run whilst the server is disconnected?

[krokkie]

Cheers, I will try that

[krokkie]

Can you give me an idea as how to script this?

[jdelaney]

I'd suggest doing an action, and writing the results of that action to a log file, so you know exactly what's going on.

So, if the function returns an HWnd, add a step directly after that function to validate that it was a success...use If IsHWnd() Then

Only proceed to the next action if the prior was a success

Output all steps to a log

That way, you can ask constructive things, like, why is 'this' function failing? instead of broad this isn't working statements

[krokkie]

Thanks jdelaney

I have no prior scripting experience.

This script was done a few years ago by my predecessor.