Scheduled Scrip Fails. Manual Script Works

[OOsorio]

I have created a script to run in a Windows Terminal Server environment. The scheduled script executes the first few lines and never executes the Press Enter.
============================================
//Set IGNORESPACES to 1 to force script interpreter to ignore spaces.
//If using IGNORESPACES quote strings in {" ... "}
//Let>IGNORESPACES=1
Run>"C:\Program Files (x86)\Activant\Prophet 21 12.1\pxxi.exe"
WaitWindowOpen>Welcome - Epicor Prophet 21
SetFocus>Welcome - Epicor Prophet 21
Wait>1
Press Tab
Press Tab
Press Tab
Press Enter
=============================================
This same scrip works when I run it manually.

[Dorian (MJT support)]

Hi, OOsorio.

I looked up the ticket we had for this, and wonder if you got my last reply.

You had told me :

The macro executes up to and including the 4th line.

..and I wasn't sure whether you meant including or excluding the comments. That was my last question.

So was the last line that executed this one :

Code: Select all

Run>"C:\Program Files (x86)\Activant\Prophet 21 12.1\pxxi.exe"

Or this one :

Code: Select all

Wait>1

[OOsorio]

I'm not sure. What I am sure of is that the Press Enter never gets executed.
=================================================
//Set IGNORESPACES to 1 to force script interpreter to ignore spaces.
//If using IGNORESPACES quote strings in {" ... "}
//Let>IGNORESPACES=1
Run>"C:\Program Files (x86)\Activant\Prophet 21 12.1\pxxi.exe"
WaitWindowOpen>Welcome - Epicor Prophet 21
SetFocus>Welcome - Epicor Prophet 21
Wait>1
Press Tab
Press Tab
Press Tab
Press Enter

[Marcus Tettmar]

When does the schedule take place? Is the user logged in at the time and is the session unlocked (not minimised)? If not no press enter is ever going to do anything.

What happens when you schedule for 1 minute from now and watch?

[OOsorio]

Marcus,

My Terminal Server session is always connected but it is minimized in my PC Desktop.

I opened the TS screen, not minimized, and the scheduler was able to run a test job I had created.

The actual job is set to run at 7:30 PM so tonight I'll leave my TS session screen open on my PC and see what happens.

Thanks,

[Marcus Tettmar]

When a remote desktop/terminal services client is minimized the session is locked. When the session is locked keystrokes cannot be sent and UIs cease to exist. See:
http://www.mjtnet.com/msfaq171.htm

[OOsorio]

The scheduled process worked. I'm very impressed with this software and all its possibilities.

Thank you,