Vantage client problem on Terminal Server

Thanks for the suggestion, Chris - wow, I was at high school when hard drives still weren't standard!! I will forward your snippet of experience to our tech. support, it just might prove to be the key. Thanks again :-) :-)

++ Andy Watts

++ Ripley Engineering Ltd
++ Tel: 01256-473940
++ Fax: 01256-479991
++ mailto: andy@...

>>> Date: Mon, 12 Aug 2002 07:57:09 -0700
>>> From: "Chris Robisch" <crobisch1@...>
>>> Subject: Re: Vantage client problem on Terminal Server

>>> Before PC's had hard drives standard, Novell Netware used to map the C:
>>> drive to a Server drive to allow large applications that assumed a client
>>> hard drive to run. They would reserve V: to Z: for the client hard drives.
>>> I've run into problems using V: for Vantage on Citrix Servers, assuming they
>>> were trying to be compatible with old Netware. Changing V: to U: worked.
>>> HTH.
Hi everyone,

I have a problem running the Vantage client on NT Terminal Server, and wondered if any of you guys had experienced anything like it. I would really appreciate any thoughts on it, it's driving me nuts!!

Here is an extract of my email to support over here in the UK:

*****************************************************

System Info:

Server OS - NT Terminal Server, Service Pack 6
Client OS - Terminal Server Client session
Vantage - v5.10.123
Progress - v9.1C


Problem Symptoms:

One of two things occur when the user attempts to start the Vantage client;

1- The cursor changes to an egg timer, nothing appears on the screen, and the server CPU utilisation rises to 100% and remains there until the "vantage.exe" client process is manually killed.

2- The Vantage splash screen briefly appears, then the login box appears, seemingly as normal. When the user attempts to type in a user name and password, no keystrokes seem to be accepted - the boxes remain empty. meanwhile, the server CPU utilisation has risen to 100%, and remains there. Normally, the login box accepts keystrokes after 10-20 minutes, but sometimes it does not at all. If the "vantage.exe" process is manually killed, the login box accepts keystrokes.

Conclusion:

It would seem that the login box (part of the "prowin32.exe" process) does not function past a certain point until the parent "vantage.exe" process has terminated. However, the "vantage.exe" process is either taking a very long time to terminate, or is not terminating at all, causing the apparent freeze-up of the Terminal Server session.

*****************************************************

Thanks very much in eager anticipation!!

++ Andy Watts

++ Ripley Engineering Ltd
++ Tel: 01256-473940
++ Fax: 01256-479991
++ mailto: andy@...
Hi everyone,

I have a problem running the Vantage client on NT Terminal Server, and wondered if any of you guys had experienced anything like it. I would really appreciate any thoughts on it, it's driving me nuts!!

Here is an extract of my email to support over here in the UK:

*****************************************************

System Info:

Server OS - NT Terminal Server, Service Pack 6
Client OS - Terminal Server Client session
Vantage - v5.10.123
Progress - v9.1C


Problem Symptoms:

One of two things occur when the user attempts to start the Vantage client;

1- The cursor changes to an egg timer, nothing appears on the screen, and the server CPU utilisation rises to 100% and remains there until the "vantage.exe" client process is manually killed.

2- The Vantage splash screen briefly appears, then the login box appears, seemingly as normal. When the user attempts to type in a user name and password, no keystrokes seem to be accepted - the boxes remain empty. meanwhile, the server CPU utilisation has risen to 100%, and remains there. Normally, the login box accepts keystrokes after 10-20 minutes, but sometimes it does not at all. If the "vantage.exe" process is manually killed, the login box accepts keystrokes.

Conclusion:

It would seem that the login box (part of the "prowin32.exe" process) does not function past a certain point until the parent "vantage.exe" process has terminated. However, the "vantage.exe" process is either taking a very long time to terminate, or is not terminating at all, causing the apparent freeze-up of the Terminal Server session.

*****************************************************

Thanks very much in eager anticipation!!

++ Andy Watts

++ Ripley Engineering Ltd
++ Tel: 01256-473940
++ Fax: 01256-479991
++ mailto: andy@...
Before PC's had hard drives standard, Novell Netware used to map the C:
drive to a Server drive to allow large applications that assumed a client
hard drive to run. They would reserve V: to Z: for the client hard drives.
I've run into problems using V: for Vantage on Citrix Servers, assuming they
were trying to be compatible with old Netware. Changing V: to U: worked.
HTH.

----- Original Message -----
From: "Andy Watts" <andy@...>
To: <vantage@yahoogroups.com>
Sent: Monday, August 12, 2002 3:30 AM
Subject: [Vantage] Vantage client problem on Terminal Server


> Hi everyone,
>
> I have a problem running the Vantage client on NT Terminal Server, and
wondered if any of you guys had experienced anything like it. I would really
appreciate any thoughts on it, it's driving me nuts!!
>
> Here is an extract of my email to support over here in the UK:
>
> *****************************************************
>
> System Info:
>
> Server OS - NT Terminal Server, Service Pack 6
> Client OS - Terminal Server Client session
> Vantage - v5.10.123
> Progress - v9.1C
>
>
> Problem Symptoms:
>
> One of two things occur when the user attempts to start the Vantage
client;
>
> 1- The cursor changes to an egg timer, nothing appears on the screen, and
the server CPU utilisation rises to 100% and remains there until the
"vantage.exe" client process is manually killed.
>
> 2- The Vantage splash screen briefly appears, then the login box appears,
seemingly as normal. When the user attempts to type in a user name and
password, no keystrokes seem to be accepted - the boxes remain empty.
meanwhile, the server CPU utilisation has risen to 100%, and remains there.
Normally, the login box accepts keystrokes after 10-20 minutes, but
sometimes it does not at all. If the "vantage.exe" process is manually
killed, the login box accepts keystrokes.
>
> Conclusion:
>
> It would seem that the login box (part of the "prowin32.exe" process) does
not function past a certain point until the parent "vantage.exe" process has
terminated. However, the "vantage.exe" process is either taking a very long
time to terminate, or is not terminating at all, causing the apparent
freeze-up of the Terminal Server session.
>
> *****************************************************
>
> Thanks very much in eager anticipation!!
>
> ++ Andy Watts
>
> ++ Ripley Engineering Ltd
> ++ Tel: 01256-473940
> ++ Fax: 01256-479991
> ++ mailto: andy@...
>
>
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>