INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Error 10054 W3NSL Pervasive 10

Error 10054 W3NSL Pervasive 10

(OP)
I have a Pervasive Engine running on a server, Client Engine on Clients. Every couple of days the application we use 'hangs', (status 171) and the app has to be restarted. When ever the clients are restarted we get this in the log file:

29/03/2010 12:31:13         ECAS_API        2952     javaw.exe       CLIENT11        E     ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE
29/03/2010 14:00:54         W3NSL           2056     ComMgr10.exe    CLIENT11        I     3111: Status 10054 returned while sending 152 bytes.
29/03/2010 14:01:50         W3NSL           1880     WinMon10.exe    CLIENT11        I     3111: Status 10054 returned while sending 152 bytes.
29/03/2010 14:02:11         W3NSL           1880     WinMon10.exe    CLIENT11        I     3112: Status 0 returned while receiving a maximum of 256 bytes.
29/03/2010 14:02:11         W3NSL           1880     WinMon10.exe    CLIENT11        I     3131: Reconnection negotiations failed after re-establishing network connection.
29/03/2010 14:02:24         W3NSL           2056     ComMgr10.exe    CLIENT11        I     3131: Reconnection attempt timed out.
29/03/2010 15:19:09         ECAS_API        2840     javaw.exe       CLIENT11        E     ECASAPI (1.21.1.12): Error 8509 - A timeout occurred during the initialization of MKDE

MK set to remote only, reconnect on, timeout set to 300.

What is W3NSL? Does this imply a winsock error? What is my next action?

OS is windows server 2003 sp2.

RE: Error 10054 W3NSL Pervasive 10

W3NSL is the Network Services Layer portion of the PSQL client components.  The 10054 is a Winsock error. It means "Connection reset by peer" and is described as happening when a connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a reboot.

If this is happening when the client app is being killed / restarted, it's probably due to that.   

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
http://www.mirtheil.com

RE: Error 10054 W3NSL Pervasive 10

(OP)
Thanks for the reply.

Should I see any notification of this on the server, there is nothing in the PVSW log.

Is this something that could of been shutdown by a router? Is there any tools e.g. packet sniffer to check?

It's a weird one, I get the error messages on startup, the 'hang' is every couple of days.

But all the system analyzer checks go ok, and the network test doesn't drop a packet.  

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close