Socket errors and Vantage disconnect problems

Yahoo Archive
1
Hi Tim,

We have/had been experiencing the exact same problem you are describing. It
began when we installed 100BaseT hubs on our network and new Dell workstations.
Our cabling was supposed to be Cat5 certified. HOWEVER, after much
troubleshooting and much head scratching, we brought in some cabling guys to
retest and discovered that our cabling (at least some of it) was not Cat5.
After installing CAT5 in the problem areas, the problem went away.

>>>Wondering if anyone has experienced any type of client disconnect problems
since upgrading to Vantage 4.0. We have been experiencing many of these
problems intermittently since the upgrade last month. Here is a sample of
the one error we have been getting the most:

'Error reading socket, ret=0, errno=2 (778)', then
'Incomplete write when writing to the server. (735)', then
'mainmenu.w Database vantage not connected (1006)', then
'Unable to run startup procedure mainmenu.w (492)', then the gray Progress
box where you have to hit the space bar.<<<



Mike Lowe
Corporate I.S. Manager
Connor Manufacturing Services
MLowe@...
(909) 273-1282
2
Wondering if anyone has experienced any type of client disconnect problems
since upgrading to Vantage 4.0. We have been experiencing many of these
problems intermittently since the upgrade last month. Here is a sample of
the one error we have been getting the most:

'Error reading socket, ret=0, errno=2 (778)', then
'Incomplete write when writing to the server. (735)', then
'mainmenu.w Database vantage not connected (1006)', then
'Unable to run startup procedure mainmenu.w (492)', then the gray Progress
box where you have to hit the space bar.

I had also ran the SetClientTimeOut.exe program dated 12/13/99 that I had
gotten from another Vantage user in the past to end client session that had
been inactive (unfortunately, I forgot where I go this) but had run that to
set it for 1440 minutes which should be 24 hours, so I don't believe this is
playing a role in he problem but am not sure at this point.

We have also been getting occasional Dr. Watson Errors on the server side
pointing to _mproserv.exe - Exception Access Violation. I do not know if the
2 are related. We are on Vantage 4.00.810 and Progress patch P90b29.

Any help anyone can give us in trying to solve this would be greatly
appreciated as Vantage support has basically told us that these socket
errors are related to our own internal network problem although we do not
have any problems with any other network application and did not have this
problem with Vantage 3.0.

Tim Goertz


�
Tim Goertz
�