6.1 logon time?

Yahoo Archive
1
This may help. We are on V6 but it took our login wait down to 12 seconds.

I'm not sure if you are logging into Vantage or clocking onto a job, however we have discovered that one cause of long wait for the login screen is due to the fact that in order to correct a problem back in a previous version of Vantage a file process was added to the library.

The process basically tests for the presence of some ocx files in the registry and if the wrong ones are there it replaces them with the right ones. This process only needs to run once to fix the original problem.


We renamed the "regocx.r" to "regocxbak.r"
We created an empty procedure "regocx.p" and an empty "rexocx.r" file.
Placed them in the mfgsys\lib folder on our server.
We then added the following lines to our install procedure.




* Rename "W:\mfgsys60\lib\regocx.r" to "regocx2.r
* Rename "W:\mfgsys60\lib\regocxbak.r" to "regocx.r
* Login to Vantage
* Rename "W:\mfgsys60\lib\regocx.r" to "regocxbak.r
* Rename "W:\mfgsys60\lib\regocx2.r" to "regocx.r

Allen Tucker
IT Vantage Manager
Espey Mfg. & Electronics Corp.
Email: atucker@...
PH: 518-245-4252
Fax: 518-245-4421
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of fingerz
Sent: Thursday, October 06, 2011 11:40 AM
To: vantage@yahoogroups.com
Subject: [Vantage] 6.1 logon time???



All,
Over the last couple of years the amount of time to see the Vantage logon screen has increased. Increasing to the point that I'm receiving feedback from management. We are using 6.1 with Progress 9.1D. Once the users are in it speeds up. The wait time is being used as a reason for people to not log off allowing others to use licenses. Any suggestions that anyone could offer would be appreciated. I don't really think it's an network infrastructure issue...But I don't know for sure.
Thanks,
Brian





________________________________


The information contained in this message is intended solely for the individual it is specifically and originally addressed. This message and its contents may contain confidential or privileged information. If you are not the intended recipient, you are hereby notified that any disclosure or distribution, or taking any action in reliance on the content of this information is strictly prohibited. If you received this message in error, please delete it from any computer and notify the sender. If you suspect that this message may have been altered, please notify the sender.


[Non-text portions of this message have been removed]
2
All,
Over the last couple of years the amount of time to see the Vantage logon screen has increased. Increasing to the point that I'm receiving feedback from management. We are using 6.1 with Progress 9.1D. Once the users are in it speeds up. The wait time is being used as a reason for people to not log off allowing others to use licenses. Any suggestions that anyone could offer would be appreciated. I don't really think it's an network infrastructure issue...But I don't know for sure.
Thanks,
Brian
3
Are you having people clock out?



From a technical perspective, when someone clocks in, it creates a LaborHed
record. Then, all the work they do (LaborDtl) falls under that LaborHed.
Once they clock it, it closes off that LaborHed, and the next time they
clock in, they get a new LaborHed record.



I've found that if you don't clock out, the logging into MES with a large
number of LaborDtl records is extremely slow.



Kevin Simon



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
fingerz
Sent: Thursday, October 06, 2011 11:40 AM
To: vantage@yahoogroups.com
Subject: [Vantage] 6.1 logon time???





All,
Over the last couple of years the amount of time to see the Vantage logon
screen has increased. Increasing to the point that I'm receiving feedback
from management. We are using 6.1 with Progress 9.1D. Once the users are in
it speeds up. The wait time is being used as a reason for people to not log
off allowing others to use licenses. Any suggestions that anyone could offer
would be appreciated. I don't really think it's an network infrastructure
issue...But I don't know for sure.
Thanks,
Brian





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