Greetings,
Hum...
<start authoritative doctor like voice>
If you're able to do this successfully against an identical setup that
indicates there is either something that is actually not identical. Or a
problem in the script that inconveniently manifests itself when you are not
watching it.
</end authoritative doctor like voice>
The server setup I'm not qualified to diagnose.
The script, I am. Inconveniently manifesting problems can be caused by
sections of script that look like:
Enter "stuff"
Enter "more stuff"
Or
Enter "Stuff"
Wait
Enter "more stuff"
Or
Enter "Stuff"
Wait
If at("Something") then...
However...
The status you saw is at the very beginning of a Meditech session (typically
the first thing it sees) - and it is indicating you are using a Pause
command. It also indicates that Meditech may have never actually launched -
or perhaps when you're script launches Meditech does it have to interact
with the Connections popup screen?
Fishing around here.
As an aside...
What about using other methods of remote access? I know folks out there are
using PCAnywhere, VNC, etc. and these do not have the "logoff effect".
Regards,
Thom
Thom C. Blackwell
Product Manager
Boston Software Systems
(866) 653-5105 ex 807
www.bossoft.com
Sign up for my weekly webinar!
LEGAL NOTICE Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only. Access to
this E-mail by anyone else is unauthorized. If you are not an addressee, any
disclosure or copying of the contents of this E-mail or any action taken (or
not taken) in reliance on it is unauthorized and may be unlawful. If you are
not an addressee, please inform the sender immediately, then delete this
message and empty from your trash.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Palmer
Sent: Wednesday, April 30, 2008 8:03 PM
To: [email protected]
Subject: RE: [Talk] Scripts Stop Responding
Actually with 2003 server which I am using you can connect to the console I
am also doing. Now I know purist's will say it is not a "true" console
session but it does not logout the session. I have another virtual machine
with identical setup that does not have this problem.
For now I will have to listen to the doctor's advice and quit doing what
hurts.
>>> On 4/30/2008 at 2:28 PM, in message
<[EMAIL PROTECTED]>,
"Thom C. Blackwell" <[EMAIL PROTECTED]> wrote:
> Greetings,
> Ah yes... when you connect in via terminal services / remote desktop, when
> you "leave" you logout the desktop session to which you connected -
causing
> the behavior you are seeing below.
> The Boot Manager could be used to re-log in when you leave - or you can
use
> the old adage if it hurts when I do this, don't do this :)
>
> Regards,
> Thom
>
>
> Thom C. Blackwell
> Product Manager
> Boston Software Systems
> (866) 653-5105 ex 807
> www.bossoft.com
> Sign up for my weekly webinar!
>
> LEGAL NOTICE Unless expressly stated otherwise, this message is
confidential
> and may be privileged. It is intended for the addressee(s) only. Access to
> this E-mail by anyone else is unauthorized. If you are not an addressee,
any
> disclosure or copying of the contents of this E-mail or any action taken
(or
> not taken) in reliance on it is unauthorized and may be unlawful. If you
are
> not an addressee, please inform the sender immediately, then delete this
> message and empty from your trash.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bill Palmer
> Sent: Wednesday, April 30, 2008 5:16 PM
> To: [email protected]
> Subject: [Talk] Scripts Stop Responding
>
> I am running scripts on a virtual server. I connect to the virtual server
> via MS Terminal Services client. As long as I have the client window open
> the scripts run fine. When I disconnect the client window from the server
> the scripts stop responding. When I come back into the session the Note
on
> the script window reads "Pause for MIS Directories" or something similar.
I
> believe the script tried to start but Meditech didn't respond.
>
> I remember seeing this problem before a couple of years ago but don't
> remember the fix. Any help will be greatly appreciated.
