Terminal server does not close when exiting application

[Vicky279]

I run a win2k terminal server with all the service packs and updates recently
installed and current. I connect to this term serv with the rdc client on a
winxp workstation which also has up to date service packs (sp2) and windows
updates. When I configure the rdc client to launch into a certain application
when it connects to the terminal server it connects to the term serv and then
it goes straight into the application. But when I exit the application,
terminal server does not close. The application screen disappears and
terminal server continues to run with a blue screen that only can be closed
by clicking the "X" button on the term serv bar. Is there any fix for this
problem. Thanks in advance.

[Vera Noest [MVP]]

Check which process is still running in the session to find the
cause of the problem. If your application is 16-bit, I could be
ntvdm.exe. Rdpclip is also a likely candidate (disable it if you
don't need it). If all else fails, try starting the application
from within a command file, let's say my_app.bat, which contains:

start /wait <path_to_application>my_app.exe
logoff

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Vicky279
I run a win2k terminal server with all the service packs and
updates recently installed and current. I connect to this term
serv with the rdc client on a winxp workstation which also has
up to date service packs (sp2) and windows updates. When I
configure the rdc client to launch into a certain application
when it connects to the terminal server it connects to the term
serv and then it goes straight into the application. But when I
exit the application, terminal server does not close. The
application screen disappears and terminal server continues to
run with a blue screen that only can be closed by clicking the
"X" button on the term serv bar. Is there any fix for this
problem. Thanks in advance.

[Vicky279]

I tried running the application from a batch file but the application will
not launch. The application is not a 16 bit application. The application
resides on the d: drive of the server. In my batch file a wrote;
cd d:
start /wait d:\Urs\Urs.exe
Logoff
The application never launches.

Post by Vera Noest [MVP]
Check which process is still running in the session to find the
cause of the problem. If your application is 16-bit, I could be
ntvdm.exe. Rdpclip is also a likely candidate (disable it if you
don't need it). If all else fails, try starting the application
start /wait <path_to_application>my_app.exe
logoff
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Vicky279
I run a win2k terminal server with all the service packs and
updates recently installed and current. I connect to this term
serv with the rdc client on a winxp workstation which also has
up to date service packs (sp2) and windows updates. When I
configure the rdc client to launch into a certain application
when it connects to the terminal server it connects to the term
serv and then it goes straight into the application. But when I
exit the application, terminal server does not close. The
application screen disappears and terminal server continues to
run with a blue screen that only can be closed by clicking the
"X" button on the term serv bar. Is there any fix for this
problem. Thanks in advance.

[Vera Noest [MVP]]

What did you use as a command line when you defined the application
as starting application in TS Connection Configuration?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Vicky279
I tried running the application from a batch file but the
application will not launch. The application is not a 16 bit
application. The application resides on the d: drive of the
start /wait d:\Urs\Urs.exe
Logoff
The application never launches.

Post by Vera Noest [MVP]
Check which process is still running in the session to find the
cause of the problem. If your application is 16-bit, I could be
ntvdm.exe. Rdpclip is also a likely candidate (disable it if
you don't need it). If all else fails, try starting the
application from within a command file, let's say my_app.bat,
start /wait <path_to_application>my_app.exe
logoff
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
wrote on 19 mar 2005 in

Post by Vicky279
I run a win2k terminal server with all the service packs and
updates recently installed and current. I connect to this
term serv with the rdc client on a winxp workstation which
also has up to date service packs (sp2) and windows updates.
When I configure the rdc client to launch into a certain
application when it connects to the terminal server it
connects to the term serv and then it goes straight into the
application. But when I exit the application, terminal server
does not close. The application screen disappears and
terminal server continues to run with a blue screen that only
can be closed by clicking the "X" button on the term serv
bar. Is there any fix for this problem. Thanks in advance.

[Vicky279]

You mentioned in your first reply that if all else fails try starting the
application from a command file. So I created a batch file pointing to the
location of my application's executable file, saved the batch file on the
terminal server and launched that batch file from the command line of the
start application command line on the rdc client.

Post by Vera Noest [MVP]
What did you use as a command line when you defined the application
as starting application in TS Connection Configuration?
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Vicky279
I tried running the application from a batch file but the
application will not launch. The application is not a 16 bit
application. The application resides on the d: drive of the
start /wait d:\Urs\Urs.exe
Logoff
The application never launches.

Post by Vera Noest [MVP]
Check which process is still running in the session to find the
cause of the problem. If your application is 16-bit, I could be
ntvdm.exe. Rdpclip is also a likely candidate (disable it if
you don't need it). If all else fails, try starting the
application from within a command file, let's say my_app.bat,
start /wait <path_to_application>my_app.exe
logoff
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
wrote on 19 mar 2005 in

Post by Vicky279
I run a win2k terminal server with all the service packs and
updates recently installed and current. I connect to this
term serv with the rdc client on a winxp workstation which
also has up to date service packs (sp2) and windows updates.
When I configure the rdc client to launch into a certain
application when it connects to the terminal server it
connects to the term serv and then it goes straight into the
application. But when I exit the application, terminal server
does not close. The application screen disappears and
terminal server continues to run with a blue screen that only
can be closed by clicking the "X" button on the term serv
bar. Is there any fix for this problem. Thanks in advance.

[Vera Noest [MVP]]

Yes, I understand. And your batch file contains the lines:
cd d:
start /wait d:\Urs\Urs.exe
Logoff

but it fails to launch the application, correct?
That's why I wondered which command line you used when you started
the application without the batch file, and it *did* launch, but
didn't close properly. Maybe you need to set the working directory
to D:\Usr in your batch file?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by Vicky279
You mentioned in your first reply that if all else fails try
starting the application from a command file. So I created a
batch file pointing to the location of my application's
executable file, saved the batch file on the terminal server and
launched that batch file from the command line of the start
application command line on the rdc client.

Post by Vera Noest [MVP]
What did you use as a command line when you defined the
application as starting application in TS Connection
Configuration?
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
wrote on 20 mar 2005 in

Post by Vicky279
I tried running the application from a batch file but the
application will not launch. The application is not a 16 bit
application. The application resides on the d: drive of the
start /wait d:\Urs\Urs.exe
Logoff
The application never launches.

Post by Vera Noest [MVP]
Check which process is still running in the session to find
the cause of the problem. If your application is 16-bit, I
could be ntvdm.exe. Rdpclip is also a likely candidate
(disable it if you don't need it). If all else fails, try
starting the application from within a command file, let's
start /wait <path_to_application>my_app.exe
logoff
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"=?Utf-8?B?Vmlja3kyNzk=?="

Post by Vicky279
I run a win2k terminal server with all the service packs
and updates recently installed and current. I connect to
this term serv with the rdc client on a winxp workstation
which also has up to date service packs (sp2) and windows
updates. When I configure the rdc client to launch into a
certain application when it connects to the terminal
server it connects to the term serv and then it goes
straight into the application. But when I exit the
application, terminal server does not close. The
application screen disappears and terminal server
continues to run with a blue screen that only can be
closed by clicking the "X" button on the term serv
bar. Is there any fix for this problem. Thanks in advance.

[v***@duskmail.com]

Post by Vicky279
start /wait d:\Urs\Urs.exe
Logoff
but it fails to launch the application, correct?
That's why I wondered which command line you used when you started
the application without the batch file, and it *did* launch, but
didn't close properly. Maybe you need to set the working directory
to D:\Usr in your batch file?
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Thanks

verena-***@duskmail.com