Progress ClientTimeOut parameter

Yahoo Archive
1
Office data collection is on the vantage main menu under production
management / data collection / general operations.


-----Original Message-----
From: Lepley, Scott A. [mailto:sal@...]
Sent: Friday, April 16, 2004 4:49 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] Progress ClientTimeOut parameter

Geez, I think you and I need to talk more, Sarah!

What exactly do you mean by office data collection (versus Vantage Plant
Floor)?

Regards,
Scott

-----Original Message-----
From: sarah.vareschi@... [mailto:sarah.vareschi@...]
Sent: Friday, April 16, 2004 4:38 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Progress ClientTimeOut parameter

FYI: Another thing I learned form this list regarding client timeout - if
you want some users to NOT timeout you can give them access to office data
collection and have them keep it open and minimized on their screen. Then,
the system will not timeout for those users b/c data collection screen
refreshes itself. I had to do this for the owner of my company who was not
happy with losing work everytime he got a phone call and forgot to close the
screen he was in.



[Non-text portions of this message have been removed]




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
Yahoo! Groups Links
2
I have recently enabled Progress's ClientTimeOut parameter on our Vantage
server and it is working, quite effectively I must say. I am no longer
receiving calls or messages from users about not being able to run Vantage
because the maximum number of connections has been reached. However, in
lieu of those calls or messages, I am now receiving calls from users about
the sequence of error messages that they receive when they return to a
disconnected Vantage session. I have contacted Vantage Support about this.
I was told that there is nothing that can be done to avoid these errors.
Support suggested that I search Progress's website for a solution. I will
try that, but I thought I would try here first. The error message sequence
goes something like this:

1. Error reading socket, ret=x, errno=y. (778)
2. ** Incomplete write when writing to the server. (735)
3. ? [literally, but only appears occasionally]
4. mainmenu.w Database mfgsys not connected. (1006)
5. ** Unable to run startup procedure mainmenu.w. (492)

I have two questions about using this ClientTimeOut parameter. First, does
anyone that uses this not experience these messages upon being disconnected?
Second, if you do not, what (if anything) have you done to work around them?

Regards,
Scott



[Non-text portions of this message have been removed]
3
We use progress timeout and also get these errors. When I initially set the
timeout parameter a few months ago I informed the users about the error they
would get when coming back to a session left idle. I told them to click
through them and press space bar. Since I had warned them in advance I did
not get any complaints. We love the timeout feature even with these errors.
4
Where is the parameter and how do you set it?

Eric L. Tyira
Software Engineer
Tamglass Tempering Systems, Inc.

P: (856) 786-1200
F: (856) 786-7606

eric.tyira@...

-----Original Message-----
From: sarah.vareschi@... [mailto:sarah.vareschi@...]
Sent: Friday, April 16, 2004 4:05 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Progress ClientTimeOut parameter

We use progress timeout and also get these errors. When I initially set the
timeout parameter a few months ago I informed the users about the error they
would get when coming back to a session left idle. I told them to click
through them and press space bar. Since I had warned them in advance I did
not get any complaints. We love the timeout feature even with these errors.



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





Yahoo! Groups Sponsor


ADVERTISEMENT
<http://rd.yahoo.com/SIG=12c0fevia/M=291630.4786521.5933964.1261774/D=egroupweb/S=1705007183:HM/EXP=1082232343/A=2072414/R=0/SIG=11tc61npd/*http://www.netflix.com/Default?mqso=60178418&partid=4786521> click here

<http://us.adserver.yahoo.com/l?M=291630.4786521.5933964.1261774/D=egroupweb/S=:HM/A=2072414/rand=740049677>

_____

Yahoo! Groups Links
* To visit your group on the web, go to:
http://groups.yahoo.com/group/vantage/

* To unsubscribe from this group, send an email to:
vantage-unsubscribe@yahoogroups.com <mailto:vantage-unsubscribe@yahoogroups.com?subject=Unsubscribe>

* Your use of Yahoo! Groups is subject to the Yahoo! Terms of <http://docs.yahoo.com/info/terms/> Service.


[Non-text portions of this message have been removed]
5
Thanks for your reply, Sarah. I realize that I should have done what you
did, but I did not know in advance that these messages were going to occur
(poor implementation procedure on my part, perhaps). In fact, even after
they started occurring, I did not associate the two because I had tweaked
some settings in Progress Explorer Tool about the same time that I enabled
the ClientTimeOut parameter (another poor implementation procedure, silly
me!). Anyway, I will be conveying this to the users here just as you did
there. I was still curious if anyone had a workaround.

Regards,
Scott

-----Original Message-----
From: sarah.vareschi@... [mailto:sarah.vareschi@...]
Sent: Friday, April 16, 2004 4:05 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Progress ClientTimeOut parameter

We use progress timeout and also get these errors. When I initially set the
timeout parameter a few months ago I informed the users about the error they
would get when coming back to a session left idle. I told them to click
through them and press space bar. Since I had warned them in advance I did
not get any complaints. We love the timeout feature even with these errors.



[Non-text portions of this message have been removed]
6
We have been using the ClientTimeOut for years and it works great. We told
our users how to deal with the errors ahead of time, so it wasn't a problem.
Upper Management didn't care for the errors, but dealt with it when we told
them they would have to spend thousands on more Vantage licenses.

We tend to scowl at people that say they received the messages, as they
should have just logged out of Vantage in the first place.

Paul L.
-----Original Message-----
From: Lepley, Scott A. [mailto:sal@...]
Sent: Friday, April 16, 2004 3:02 PM
To: Online Vantage Users Group (E-mail)
Subject: [Vantage] Progress ClientTimeOut parameter


I have recently enabled Progress's ClientTimeOut parameter on our Vantage
server and it is working, quite effectively I must say. I am no longer
receiving calls or messages from users about not being able to run Vantage
because the maximum number of connections has been reached. However, in
lieu of those calls or messages, I am now receiving calls from users about
the sequence of error messages that they receive when they return to a
disconnected Vantage session. I have contacted Vantage Support about
this.
I was told that there is nothing that can be done to avoid these errors.
Support suggested that I search Progress's website for a solution. I will
try that, but I thought I would try here first. The error message
sequence
goes something like this:

1. Error reading socket, ret=x, errno=y. (778)
2. ** Incomplete write when writing to the server. (735)
3. ? [literally, but only appears occasionally]
4. mainmenu.w Database mfgsys not connected. (1006)
5. ** Unable to run startup procedure mainmenu.w. (492)

I have two questions about using this ClientTimeOut parameter. First,
does
anyone that uses this not experience these messages upon being
disconnected?
Second, if you do not, what (if anything) have you done to work around
them?

Regards,
Scott




[Non-text portions of this message have been removed]
7
These errors are on the client. When the Progress TimeOut disconnects, it
terminates the connection at the server to the client and then backs out of
the transactions. This is similar to using Promon on the server to kill a
session. The errors result back on the client where the client portion of
the software is still running and then tries to communicate with the server
again (client/server). This is why you do not see the error until you apply
focus to the vantage application on the workstation.

What I have found to work the best is to shut vantage down at the client
using a combination of mouse clicks and keystrokes. Like using a macro
program like ground control or autoit. This way it looks as if someone at
the computer actually mouse clicks all the cancel/close buttons to back out
of the screens, then the exit vantage and answers yes to confirm it. This
method leaves no messages on the client and no incomplete transactions in
the database. You could apply this same method to the Progress Timeout
errors by creating a macro that would apply the mouse clicks and spacebar
keystroke. Set up a program to run as a service on the workstation that
monitors for the DNA (Windows Class Name and Window Name) then have it fire
the macro and close the error windows. This works quite well too, you'll
just see a quick flash of the error messages as they appear, then disappear
off the screen.

-----Original Message-----
From: Lepley, Scott A. [mailto:sal@...]
Sent: Friday, April 16, 2004 3:02 PM
To: Online Vantage Users Group (E-mail)
Subject: [Vantage] Progress ClientTimeOut parameter


I have recently enabled Progress's ClientTimeOut parameter on our Vantage
server and it is working, quite effectively I must say. I am no longer
receiving calls or messages from users about not being able to run Vantage
because the maximum number of connections has been reached. However, in
lieu of those calls or messages, I am now receiving calls from users about
the sequence of error messages that they receive when they return to a
disconnected Vantage session. I have contacted Vantage Support about this.
I was told that there is nothing that can be done to avoid these errors.
Support suggested that I search Progress's website for a solution. I will
try that, but I thought I would try here first. The error message sequence
goes something like this:

1. Error reading socket, ret=x, errno=y. (778)
2. ** Incomplete write when writing to the server. (735)
3. ? [literally, but only appears occasionally]
4. mainmenu.w Database mfgsys not connected. (1006)
5. ** Unable to run startup procedure mainmenu.w. (492)

I have two questions about using this ClientTimeOut parameter. First, does
anyone that uses this not experience these messages upon being disconnected?
Second, if you do not, what (if anything) have you done to work around them?

Regards,
Scott
8
I'm good at scowling, as you can ask just about anyone here! I'll keep that
in mind. ;-)

Somehow, I think there's a connection between the scowling and the power
user thread from earlier today...

Regards,
Scott

-----Original Message-----
From: Paul Lipham [mailto:pml@...]
Sent: Friday, April 16, 2004 4:24 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Progress ClientTimeOut parameter

We have been using the ClientTimeOut for years and it works great. We told
our users how to deal with the errors ahead of time, so it wasn't a problem.
Upper Management didn't care for the errors, but dealt with it when we told
them they would have to spend thousands on more Vantage licenses.

We tend to scowl at people that say they received the messages, as they
should have just logged out of Vantage in the first place.

Paul L.

-----Original Message-----
From: Lepley, Scott A. [mailto:sal@...]
Sent: Friday, April 16, 2004 3:02 PM
To: Online Vantage Users Group (E-mail)
Subject: [Vantage] Progress ClientTimeOut parameter

I have recently enabled Progress's ClientTimeOut parameter on our Vantage
server and it is working, quite effectively I must say. I am no longer
receiving calls or messages from users about not being able to run Vantage
because the maximum number of connections has been reached. However, in
lieu of those calls or messages, I am now receiving calls from users about
the sequence of error messages that they receive when they return to a
disconnected Vantage session. I have contacted Vantage Support about
this.
I was told that there is nothing that can be done to avoid these errors.
Support suggested that I search Progress's website for a solution. I will
try that, but I thought I would try here first. The error message
sequence
goes something like this:

1. Error reading socket, ret=x, errno=y. (778)
2. ** Incomplete write when writing to the server. (735)
3. ? [literally, but only appears occasionally]
4. mainmenu.w Database mfgsys not connected. (1006)
5. ** Unable to run startup procedure mainmenu.w. (492)

I have two questions about using this ClientTimeOut parameter. First,
does
anyone that uses this not experience these messages upon being
disconnected?
Second, if you do not, what (if anything) have you done to work around
them?

Regards,
Scott


[Non-text portions of this message have been removed]
9
There was a descriptive post from a user on this list a few months ago. I
did not save it but if you search the archives you can probably find it.
There's also a description on vantage eportal answerbook. It is below: (for
progress 9.1D)



AnswerBook Details

AnswerBook #: 2271MPS Product: Vantage
Date Added: 8/20/2002 Version:
Date Changed: 12/9/2003 Module: Progress

----------------------------------------------------------------------------
----

Summary:
PG ClientTimeOut available with 9.1D
Details:
Page 2271MPS

timeout time out Clienttimeout
XA520
XA600
XA610

HOW TO SETUP THE PROGRESS ClientTimeOut

With Progress 9.1D03, Progress has made available a timeout feature.

To implement the feature the following lines must be added to the Startup
registry key on the server. This process applies to all clients connected to
the database.

Where 'n' is the number of minutes after which the user will be disconnected
if there is no activity. Again, this is a server parameter so all users will
be affected by this setting. Activity is defined as mouse and keyboard
activity from client to server.

This ClientTimeOut parameter can be put into the registry of the following
key, by default this key will not exist so will need to be created.

HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS\9.1D\STARTUP

Once you open the Startup Key, from the top select EDIT > NEW > STRING. The
string name is called "ClientTimeOut" in the value field put in how many
minutes till disconnection.

Once the changes have been made you will need to reboot the server for
progress to reread the registry on startup of the Admin Service.
10
FYI: Another thing I learned form this list regarding client timeout - if
you want some users to NOT timeout you can give them access to office data
collection and have them keep it open and minimized on their screen. Then,
the system will not timeout for those users b/c data collection screen
refreshes itself. I had to do this for the owner of my company who was not
happy with losing work everytime he got a phone call and forgot to close the
screen he was in.
11
Geez, I think you and I need to talk more, Sarah!

What exactly do you mean by office data collection (versus Vantage Plant
Floor)?

Regards,
Scott

-----Original Message-----
From: sarah.vareschi@... [mailto:sarah.vareschi@...]
Sent: Friday, April 16, 2004 4:38 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Progress ClientTimeOut parameter

FYI: Another thing I learned form this list regarding client timeout - if
you want some users to NOT timeout you can give them access to office data
collection and have them keep it open and minimized on their screen. Then,
the system will not timeout for those users b/c data collection screen
refreshes itself. I had to do this for the owner of my company who was not
happy with losing work everytime he got a phone call and forgot to close the
screen he was in.



[Non-text portions of this message have been removed]