V61 - Very slow on remote client - Solution

Yahoo Archive
1
Thanks Jason. Should have checked this out. I looked at the mapped drive
but didn't think UNC came about until v8. Once I deleted and then
reinstalled the clients. Zoom, Zoom.

Love this Group,

David Gartner
EPG Companies Inc.
<http://www.epgco.com/>

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Jason Claggett
Sent: Wednesday, May 13, 2009 7:32 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: v61 - Very slow on remote client







David,

We encounter this problem a lot when moving 6.10 databases to other servers
for whatever reason. The installation of the Vantage clients insert
\\servername\<sharename> as the UNC path for every OCX or DLL when you first
install it. Problem is when you install the updated client or move servers,
it still tries the old server path first before it eventually times out and
goes to the correct path. New installs as mentioned in the posts will work
just fine because it doesn't know anything about it.

Uninstalling will not remove these registry entries - unfortunately. The
best way to rid it of these is search through the registry for
\\servername\<sharename<file:///\\servername\%3csharename>> and remove these
first and then install the new client. Please make a backup copy of your
registry prior to doing any removing. Use a registry find and replace to
make life easier.

Thanks,

Jason Claggett
Microsoft Small Business Specialist
MCP #3856159
2W Technologies, LLC
312.533.4033 x8039
jason@2wtech. <mailto:jason%402wtech.com> commailto:
<mailto:jason@...> jason@2wtech. <mailto:jason%402wtech.com> com

.

<http://geo.yahoo.com/serv?s=97359714/grpId=20369/grpspId=1705007181/msgId=7
7843/stime=1242261271/nc1=1/nc2=2/nc3=3>





[Non-text portions of this message have been removed]
2
Good Morning,

Just installed our upgraded v61 from 5.2 Db on an operational server last
night. Thousand reasons why not to do something like this.. however.
The client is plenty fast on the server. Logs in quickly and all the
"Entry" screens are snappy. The network clients get the special "Not
responding" business which would be disappointing though acceptable. The
show stopper is the Order entry screen. Updating or adding line takes 30-40
seconds to open on Core2Duo's with 3.5GB of RAM. Wait long enough and
everything seems functional. Similar problem with Customers.

Enjoyed reading the Yahoo archives last night and this morning. Tuned the
db and trying a Dump and Load, now. I believe Progress is actually the
problem. Modified the .pf file. Scrubbed the registry for any old
mappings, PSC and chunks v5.2. Uninstalled the client and reinstalled.

Is there a known methodology to just reinstalling Progress portion? Since
it's working solidly on the server side.

I pasted in portions of my mfgsys.ini I think are pertinent:
T: is my Epicor network share, d: is physical

Any ideas are welcome,

David G


[Startup]
V6Display=no
;ImmediateDisplay=yes
;MultitaskingInterval=100
DLC=T:\prgs91d
Use-3D-Size=No
PROBUILD=T:\prgs91d\Probuild
PROPATH=.,T:\mfgsys61
PrinterFont=Courier New,Size=12
AllowDesignMode=no
nosplash=yes
UseSourceEditor=No

****************************************************************************
**
; The "SysCheckmark" setting allows you to define the character used to mark
; a selection in various widgets, e.g., browser, selection list. The right
; side of the equals sign "=" must be a single numeric character value.
;
SysCheckmark=251
DLC=D:\epicor\prgs91d
PROBUILD=D:\epicor\prgs91d\PROBUILD
PROPATH=.,D:\epicor\prgs91d\tty,D:\epicor\prgs91d\PROBUILD\EUCAPP\EUC.PL,D:\
epicor\prgs91d\PROBUILD\EUCAPP

; This section defines the Java environment.
[JAVA]
JDKHOME=T:\prgs91d\jdk
JREHOME=T:\prgs91d\jre
JRECP=T:\prgs91d\jre\lib\rt.jar;T:\prgs91d\jre\lib\i18n.jar
JDKCP=T:\prgs91d\jdk\lib\tools.jar
FATHOMCP=
REPLCP=
PROGRESSCP=T:\prgs91d\java\progress.jar;T:\prgs91d\java\messages.jar;
JVMEXE=java
JVMARGS=-ms8m
JAVAPOLICY=T:\prgs91d\java\java.policy

[MFG Workstation Installation]
MFGDir=T:\mfgsys61
ProgDir=T:\prgs91d
NetworkProtocol=A
DBServer=mfgsys61
DBService=6100
;TrnDBServer=mfgsystrn61
;TrnDBService=6110
ServerMachine=deuce
DynamicName=A
LocalWorkDir=C:\Epicor\MFGWK61
;GatewayDir=c:\Epicor\Gateway
ServerIPAddress=192.168.0.130
LANGSEL=A
;MobileConnectUpdate=YES



[Non-text portions of this message have been removed]
3
Not sure if I am reading the question right, with regard to the client's "remoteness"...that is LAN client or some sort of VPN or terminal service client. Also whether this is a new server or just version upgrade on existing server. But here are some things I had to resolve when we upgraded our 6.1 server as well as from 5.2 to 6.0 on same server (two separate projects). I found through bad experience that there are subtle network issues that can severely affect client performance (on LAN).

1. Left over SERVICES and HOSTS entries on the client that refer to the old server
2. Old server still running and present on the network
3. If login screen is also slow appearing check the REGOCX.log file in mfgwrk61 on client for time stamps
4. If drive letter is new double check client registry for lingering references to old one(s)
5. Check NIC settings on new server for compatibility with the switch it is attached to
6. Old DNS entries referring to old server might need to be removed
7. Sort of drastic, but connect clients via a different brand of switch (preferable new & managed)

This last one has always stumped me but when we upgraded 6.10 to a new server many clients ran very slow until I installed a new HP ProCurve managed switch. No other changes, same settings as old 3COM switch, but plugging users into the new switch made them run very fast. Something about the new server was not working the same with the old switches in the path. The Regocx.log file time went from 3 minutes to 12 seconds.

-Todd C.


________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of David Gartner
Sent: Wednesday, May 13, 2009 7:57 AM
To: vantage@yahoogroups.com
Subject: [Vantage] v61 - Very slow on remote client




Good Morning,

Just installed our upgraded v61 from 5.2 Db on an operational server last
night. Thousand reasons why not to do something like this.. however.
The client is plenty fast on the server. Logs in quickly and all the
"Entry" screens are snappy. The network clients get the special "Not
responding" business which would be disappointing though acceptable. The
show stopper is the Order entry screen. Updating or adding line takes 30-40
seconds to open on Core2Duo's with 3.5GB of RAM. Wait long enough and
everything seems functional. Similar problem with Customers.

Enjoyed reading the Yahoo archives last night and this morning. Tuned the
db and trying a Dump and Load, now. I believe Progress is actually the
problem. Modified the .pf file. Scrubbed the registry for any old
mappings, PSC and chunks v5.2. Uninstalled the client and reinstalled.

Is there a known methodology to just reinstalling Progress portion? Since
it's working solidly on the server side.

I pasted in portions of my mfgsys.ini I think are pertinent:
T: is my Epicor network share, d: is physical

Any ideas are welcome,

David G


[Startup]
V6Display=no
;ImmediateDisplay=yes
;MultitaskingInterval=100
DLC=T:\prgs91d
Use-3D-Size=No
PROBUILD=T:\prgs91d\Probuild
PROPATH=.,T:\mfgsys61
PrinterFont=Courier New,Size=12
AllowDesignMode=no
nosplash=yes
UseSourceEditor=No

****************************************************************************
**
; The "SysCheckmark" setting allows you to define the character used to mark
; a selection in various widgets, e.g., browser, selection list. The right
; side of the equals sign "=" must be a single numeric character value.
;
SysCheckmark=251
DLC=D:\epicor\prgs91d
PROBUILD=D:\epicor\prgs91d\PROBUILD
PROPATH=.,D:\epicor\prgs91d\tty,D:\epicor\prgs91d\PROBUILD\EUCAPP\EUC.PL,D:\
epicor\prgs91d\PROBUILD\EUCAPP

; This section defines the Java environment.
[JAVA]
JDKHOME=T:\prgs91d\jdk
JREHOME=T:\prgs91d\jre
JRECP=T:\prgs91d\jre\lib\rt.jar;T:\prgs91d\jre\lib\i18n.jar
JDKCP=T:\prgs91d\jdk\lib\tools.jar
FATHOMCP=
REPLCP=
PROGRESSCP=T:\prgs91d\java\progress.jar;T:\prgs91d\java\messages.jar;
JVMEXE=java
JVMARGS=-ms8m
JAVAPOLICY=T:\prgs91d\java\java.policy

[MFG Workstation Installation]
MFGDir=T:\mfgsys61
ProgDir=T:\prgs91d
NetworkProtocol=A
DBServer=mfgsys61
DBService=6100
;TrnDBServer=mfgsystrn61
;TrnDBService=6110
ServerMachine=deuce
DynamicName=A
LocalWorkDir=C:\Epicor\MFGWK61
;GatewayDir=c:\Epicor\Gateway
ServerIPAddress=192.168.0.130
LANGSEL=A
;MobileConnectUpdate=YES


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





[Non-text portions of this message have been removed]
4
Thanks for the reply, Todd.

Clients are on the same LAN. as the Vantage server we planned to gracefully
migrate to in the future, instead of Monday. My DNS was seriously hosed and
appears to be set as of this morning. Though no change in the login speed.

I am going to keep looking for any reference to the old server (shares,
odbc, anything). Now I just have to find where I saved the darn ODBC config
for 6.1 doc.

Thanks again,

David




_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Todd Caughey
Sent: Wednesday, May 13, 2009 9:55 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] v61 - Very slow on remote client






Not sure if I am reading the question right, with regard to the client's
"remoteness"...that is LAN client or some sort of VPN or terminal service
client. Also whether this is a new server or just version upgrade on
existing server. But here are some things I had to resolve when we upgraded
our 6.1 server as well as from 5.2 to 6.0 on same server (two separate
projects). I found through bad experience that there are subtle network
issues that can severely affect client performance (on LAN).

1. Left over SERVICES and HOSTS entries on the client that refer to the old
server
2. Old server still running and present on the network
3. If login screen is also slow appearing check the REGOCX.log file in
mfgwrk61 on client for time stamps
4. If drive letter is new double check client registry for lingering
references to old one(s)
5. Check NIC settings on new server for compatibility with the switch it is
attached to
6. Old DNS entries referring to old server might need to be removed
7. Sort of drastic, but connect clients via a different brand of switch
(preferable new & managed)

This last one has always stumped me but when we upgraded 6.10 to a new
server many clients ran very slow until I installed a new HP ProCurve
managed switch. No other changes, same settings as old 3COM switch, but
plugging users into the new switch made them run very fast. Something about
the new server was not working the same with the old switches in the path.
The Regocx.log file time went from 3 minutes to 12 seconds.

-Todd C.

________________________________
From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of David Gartner
Sent: Wednesday, May 13, 2009 7:57 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: [Vantage] v61 - Very slow on remote client

Good Morning,

Just installed our upgraded v61 from 5.2 Db on an operational server last
night. Thousand reasons why not to do something like this.. however.
The client is plenty fast on the server. Logs in quickly and all the
"Entry" screens are snappy. The network clients get the special "Not
responding" business which would be disappointing though acceptable. The
show stopper is the Order entry screen. Updating or adding line takes 30-40
seconds to open on Core2Duo's with 3.5GB of RAM. Wait long enough and
everything seems functional. Similar problem with Customers.

Enjoyed reading the Yahoo archives last night and this morning. Tuned the
db and trying a Dump and Load, now. I believe Progress is actually the
problem. Modified the .pf file. Scrubbed the registry for any old
mappings, PSC and chunks v5.2. Uninstalled the client and reinstalled.

Is there a known methodology to just reinstalling Progress portion? Since
it's working solidly on the server side.

I pasted in portions of my mfgsys.ini I think are pertinent:
T: is my Epicor network share, d: is physical

Any ideas are welcome,

David G

[Startup]
V6Display=no
;ImmediateDisplay=yes
;MultitaskingInterval=100
DLC=T:\prgs91d
Use-3D-Size=No
PROBUILD=T:\prgs91d\Probuild
PROPATH=.,T:\mfgsys61
PrinterFont=Courier New,Size=12
AllowDesignMode=no
nosplash=yes
UseSourceEditor=No

****************************************************************************
**
; The "SysCheckmark" setting allows you to define the character used to mark
; a selection in various widgets, e.g., browser, selection list. The right
; side of the equals sign "=" must be a single numeric character value.
;
SysCheckmark=251
DLC=D:\epicor\prgs91d
PROBUILD=D:\epicor\prgs91d\PROBUILD
PROPATH=.,D:\epicor\prgs91d\tty,D:\epicor\prgs91d\PROBUILD\EUCAPP\EUC.PL,D:\
epicor\prgs91d\PROBUILD\EUCAPP

; This section defines the Java environment.
[JAVA]
JDKHOME=T:\prgs91d\jdk
JREHOME=T:\prgs91d\jre
JRECP=T:\prgs91d\jre\lib\rt.jar;T:\prgs91d\jre\lib\i18n.jar
JDKCP=T:\prgs91d\jdk\lib\tools.jar
FATHOMCP=
REPLCP=
PROGRESSCP=T:\prgs91d\java\progress.jar;T:\prgs91d\java\messages.jar;
JVMEXE=java
JVMARGS=-ms8m
JAVAPOLICY=T:\prgs91d\java\java.policy

[MFG Workstation Installation]
MFGDir=T:\mfgsys61
ProgDir=T:\prgs91d
NetworkProtocol=A
DBServer=mfgsys61
DBService=6100
;TrnDBServer=mfgsystrn61
;TrnDBService=6110
ServerMachine=deuce
DynamicName=A
LocalWorkDir=C:\Epicor\MFGWK61
;GatewayDir=c:\Epicor\Gateway
ServerIPAddress=192.168.0.130
LANGSEL=A
;MobileConnectUpdate=YES

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



.

<http://geo.yahoo.com/serv?s=97359714/grpId=20369/grpspId=1705007181/msgId=7
7798/stime=1242226555/nc1=3848642/nc2=3848585/nc3=5689707>





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



If your 5.2 app was on a different server than your 6.1 db, your clients
are probably still pointing to the 5.2 to pull the progress network
client information. This is probably true even if you uninstalled the
5.2 client and progress network client. This progress version never did
a clean uninstall on the client.



We had this issue on all of our client machines when we upgraded from
5.2 to 6.1. Existing clients were running very slow. However, if we
did a new install on a client that never had the 5.2 version installed,
it ran fine.



We ended up uninstalling everything from the client - both the 6.1 and
5.2 client as well as the progress network client. We then did a manual
registry clean to remove all the left over progress elements. That is
an important step. If you don't do the registry clean, the problem
persists even when you re install the progress network client because it
keeps the old 5.2 settings that were not removed during the normal
uninstall procedure.



Hope that helps. If you need more info, contact off line at contact
info below.



Jerry Rodden

SA - Production Planning/MRP

Cardington Yutaka Technologies Inc.

575 West Main Street

Cardington, OH 43315

Phone: 419-864-8777 ext. 6209

Fax: 419-864-7771

Email jrodden@...





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

We encounter this problem a lot when moving 6.10 databases to other servers for whatever reason. The installation of the Vantage clients insert \\servername\<sharename> as the UNC path for every OCX or DLL when you first install it. Problem is when you install the updated client or move servers, it still tries the old server path first before it eventually times out and goes to the correct path. New installs as mentioned in the posts will work just fine because it doesn't know anything about it.

Uninstalling will not remove these registry entries - unfortunately. The best way to rid it of these is search through the registry for \\servername\<sharename<file:///\\servername\%3csharename>> and remove these first and then install the new client. Please make a backup copy of your registry prior to doing any removing. Use a registry find and replace to make life easier.

Thanks,

Jason Claggett
Microsoft Small Business Specialist
MCP #3856159
2W Technologies, LLC
312.533.4033 x8039
jason@...<mailto:jason@...>



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

You can also use the host file located in C:\WINDOWS\system32\drivers\etc to point the old server to the new server. Make an entry of the old server name "OldServer" with the IP address of the new server. This host file takes precident over other DNS entries. So if your registry or any other app is looking for \\OldServer\epicor, it will point it over to the new server. You would have to modify ALL of the clients that are having this issue, but it is easier than changing the registry on all the clients.

Jeff



--- In vantage@yahoogroups.com, "David Gartner" <dgartner@...> wrote:
>
> Thanks for the reply, Todd.
>
> Clients are on the same LAN. as the Vantage server we planned to gracefully
> migrate to in the future, instead of Monday. My DNS was seriously hosed and
> appears to be set as of this morning. Though no change in the login speed.
>
> I am going to keep looking for any reference to the old server (shares,
> odbc, anything). Now I just have to find where I saved the darn ODBC config
> for 6.1 doc.
>
> Thanks again,
>
> David
>
>
>
>
> _____
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> Todd Caughey
> Sent: Wednesday, May 13, 2009 9:55 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] v61 - Very slow on remote client
>
>
>
>
>
>
> Not sure if I am reading the question right, with regard to the client's
> "remoteness"...that is LAN client or some sort of VPN or terminal service
> client. Also whether this is a new server or just version upgrade on
> existing server. But here are some things I had to resolve when we upgraded
> our 6.1 server as well as from 5.2 to 6.0 on same server (two separate
> projects). I found through bad experience that there are subtle network
> issues that can severely affect client performance (on LAN).
>
> 1. Left over SERVICES and HOSTS entries on the client that refer to the old
> server
> 2. Old server still running and present on the network
> 3. If login screen is also slow appearing check the REGOCX.log file in
> mfgwrk61 on client for time stamps
> 4. If drive letter is new double check client registry for lingering
> references to old one(s)
> 5. Check NIC settings on new server for compatibility with the switch it is
> attached to
> 6. Old DNS entries referring to old server might need to be removed
> 7. Sort of drastic, but connect clients via a different brand of switch
> (preferable new & managed)
>
> This last one has always stumped me but when we upgraded 6.10 to a new
> server many clients ran very slow until I installed a new HP ProCurve
> managed switch. No other changes, same settings as old 3COM switch, but
> plugging users into the new switch made them run very fast. Something about
> the new server was not working the same with the old switches in the path.
> The Regocx.log file time went from 3 minutes to 12 seconds.
>
> -Todd C.
>
> ________________________________
> From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> [mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
> Behalf Of David Gartner
> Sent: Wednesday, May 13, 2009 7:57 AM
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> Subject: [Vantage] v61 - Very slow on remote client
>
> Good Morning,
>
> Just installed our upgraded v61 from 5.2 Db on an operational server last
> night. Thousand reasons why not to do something like this.. however.
> The client is plenty fast on the server. Logs in quickly and all the
> "Entry" screens are snappy. The network clients get the special "Not
> responding" business which would be disappointing though acceptable. The
> show stopper is the Order entry screen. Updating or adding line takes 30-40
> seconds to open on Core2Duo's with 3.5GB of RAM. Wait long enough and
> everything seems functional. Similar problem with Customers.
>
> Enjoyed reading the Yahoo archives last night and this morning. Tuned the
> db and trying a Dump and Load, now. I believe Progress is actually the
> problem. Modified the .pf file. Scrubbed the registry for any old
> mappings, PSC and chunks v5.2. Uninstalled the client and reinstalled.
>
> Is there a known methodology to just reinstalling Progress portion? Since
> it's working solidly on the server side.
>
> I pasted in portions of my mfgsys.ini I think are pertinent:
> T: is my Epicor network share, d: is physical
>
> Any ideas are welcome,
>
> David G
>
> [Startup]
> V6Display=no
> ;ImmediateDisplay=yes
> ;MultitaskingInterval=100
> DLC=T:\prgs91d
> Use-3D-Size=No
> PROBUILD=T:\prgs91d\Probuild
> PROPATH=.,T:\mfgsys61
> PrinterFont=Courier New,Size=12
> AllowDesignMode=no
> nosplash=yes
> UseSourceEditor=No
>
> ****************************************************************************
> **
> ; The "SysCheckmark" setting allows you to define the character used to mark
> ; a selection in various widgets, e.g., browser, selection list. The right
> ; side of the equals sign "=" must be a single numeric character value.
> ;
> SysCheckmark=251
> DLC=D:\epicor\prgs91d
> PROBUILD=D:\epicor\prgs91d\PROBUILD
> PROPATH=.,D:\epicor\prgs91d\tty,D:\epicor\prgs91d\PROBUILD\EUCAPP\EUC.PL,D:\
> epicor\prgs91d\PROBUILD\EUCAPP
>
> ; This section defines the Java environment.
> [JAVA]
> JDKHOME=T:\prgs91d\jdk
> JREHOME=T:\prgs91d\jre
> JRECP=T:\prgs91d\jre\lib\rt.jar;T:\prgs91d\jre\lib\i18n.jar
> JDKCP=T:\prgs91d\jdk\lib\tools.jar
> FATHOMCP=
> REPLCP=
> PROGRESSCP=T:\prgs91d\java\progress.jar;T:\prgs91d\java\messages.jar;
> JVMEXE=java
> JVMARGS=-ms8m
> JAVAPOLICY=T:\prgs91d\java\java.policy
>
> [MFG Workstation Installation]
> MFGDir=T:\mfgsys61
> ProgDir=T:\prgs91d
> NetworkProtocol=A
> DBServer=mfgsys61
> DBService=6100
> ;TrnDBServer=mfgsystrn61
> ;TrnDBService=6110
> ServerMachine=deuce
> DynamicName=A
> LocalWorkDir=C:\Epicor\MFGWK61
> ;GatewayDir=c:\Epicor\Gateway
> ServerIPAddress=192.168.0.130
> LANGSEL=A
> ;MobileConnectUpdate=YES
>
> [Non-text portions of this message have been removed]
>
>
>
> .
>
> <http://geo.yahoo.com/serv?s=97359714/grpId=20369/grpspId=1705007181/msgId=7
> 7798/stime=1242226555/nc1=3848642/nc2=3848585/nc3=5689707>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>