URGENT HELP NEED

newbee · Post by **newbee** » Thu Sep 16, 2004 12:17 pm

hi

I made a small email sending program with the help of Macro Scheduler, which does simple work, taking email id from small .txt file and also taking standard email message from other .txt file and sending mail, and in my local PC its also running 100% okay with my need without any single poblem and i hv tested localy 25+ times in past so far.

- my macro scheduler run with some TAB keys and ENTER keys

BUT BUT
1) when i RUN same program remotely its become crazy macro scheduler, i just can;t run what i want

2) when i CLOSE TS 'TERMINAL SERVICES', it never RUN

3) u duded hv any idea how to bull this crazy problem of mine and pull out the solution

I apprecite reply from this forum and MS supports too

THANKS TO ALL IN ADVANCE

Lumumba · Post by **Lumumba** » Thu Sep 16, 2004 1:17 pm

when i CLOSE TS 'TERMINAL SERVICES', it never RUN

Yep, thx Bill Gates !

If a TS session will be closed/finished the screen of the host box/desktop will get locked! Therefore any MSched script won't be able to interact with that desktop.

Use TightVNC/RealVNC/VNC (Freeware) or another remote software like PC-Anywhere. That'll work.

when i RUN same program remotely its become crazy macro scheduler, i just can;t run what i want

a) You wan't to run a MSched script locally to do something on the remote box ? No go! (just in case that I've lost you

)

b) You ran that MSched script on the remote box and it went nuts?
Often its a timing issue. If that remote box isn't a 100% copy (Hardware/Software) of your local one, you've entered the world of pain. You've to do the dev & testing on that box directly to identify how to bypass specific system based influences on your script.

vanfanel · Post by **vanfanel** » Thu Sep 16, 2004 6:40 pm

Lumumba wrote: Use TightVNC/RealVNC/VNC (Freeware) or another remote software like PC-Anywhere. That'll work.

I'd recommend RealVNC over TightVNC. I ran into some odd problems with TightVNC and MacroScheduler. If I hit play and then close the VNC window it causes strange lockup problems with MacroScheduler. I watched the display on the local machine and noticed that MS seems to go unresponsive once the TightVNC viewer is closed from some remote computer. If I reopen the VNC session and try and stop the macro...it's almost as if the "stop" button gets stuck until I close MS. Some macros also seem to lock up once the VNC window is closed. All works well when you're running on a schedule though. I haven't had any of these problems after switching to RealVNC.

Lumumba · Post by **Lumumba** » Thu Sep 16, 2004 7:24 pm

Thx 4 that additional info

Bob Hansen · Post by **Bob Hansen** » Thu Sep 16, 2004 8:21 pm

Absolutely no problems with pcAnyWhere(PCA).

Use Macro Scheduler with PCA daily. Can connect, start macro, disconnect, reconnect later hours later to monitor, see results, etc., no inpact on Macro Scheduler.

Lumumba · Post by **Lumumba** » Thu Sep 16, 2004 9:00 pm

Confirmed.
Worked fine for now > 3y - on a 24/7 basis

newbee · Post by **newbee** » Fri Sep 17, 2004 4:17 am

Lumumba wrote:Confirmed.
Worked fine for now > 3y - on a 24/7 basis

yep, lee me download VNC and RUN my scheduler............THANKS FOR UR GR8 HELP............U REMAIN IN MY HEART FOR LONG TIME

CHEEEEEEEEEEEEERS

URGENT HELP NEED

URGENT HELP NEED

thanks a lot