Results 1 to 8 of 8
  1. #1
    Join Date
    Jan 2006
    Posts
    1

    Unanswered: Pervasive Error: 3112

    I am using Pervasive 8.7 and I have installed a web application at a client and everything seems to run fine for a while - but then we get this error.

    3112: Status 10054 returned while receiving a maximum of 40960 bytes

    The web server is acting as the client and the data server is where both the application file and all data files reside. I was told to check to be sure that the autoreconnect was set to on and I have made this change and it seems to have helped - the app stays up for a day or even two but then we get this error again. Any ideas on what else it could be? I have made sure that the Use Local MicroKernel Engine = Off and Use Cache Engine = Off.

    I am at a loss as to why it works for a while and then we see this error again.

  2. #2
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    Sounds like the network is having problems. Is there anything in Event Log or the PVSW.LOG that shows a network problem?
    Run a PSA network communication test to see if there's anything that comes up..
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  3. #3
    Join Date
    Jan 2006
    Posts
    3

    I'm having the same problem...

    I have installed PSQL V8.7 WGE on a server and another PC. The PC accesses the data via the server. The application normally runs fine, but occasionally, usually once a day, will not be able to access any data. (In the application, a telephone directory, the error displayed is the same as if you searched for a record that doesn't exists.) Once this error occurs, the only fix is to exit the application and start over.

    If it is a network problem, then it is VERY intermitent, as I have never had the communication test fail on me. The error message that 'awilson' posted is what appears in PVSW.LOG, except there is a bit more data there. Here is the full line from mine:

    01-19-2006 09:04:37 W3NSL244 00000B38 ntvdm.exe CFS-PC81 E 3112: Status 10054 returned while receiving a maximum of 40960 bytes.

    Unfortunetly, I have not been able to reproduce the problem. It happens when doing a search, but when the same search is repeated after restarting the program there is no error.

    Any thoughts on what to look for?

  4. #4
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    Based on the entry in the PVSW.LOG, it is a network issue. The "status 10054" is a Winsock error. Also, the component (W3NSL244) is the Win32 Network Services Layer.
    A few questions:
    1. Is the machine using TCP/IP to talk to the remote server (you can check in the Pervasive Monitor)?
    2. If not, switch to TCP/IP. Does the error still occur?
    3. Is there any pattern to this error? For example, does it always occur around 9am (based on the entry in PVSW.LOG)?
    4. If what else is happening when the error occurs? For example, is a virus scan or spyware scan or backup occurring?
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  5. #5
    Join Date
    Jan 2006
    Posts
    3
    1. Is the machine using TCP/IP to talk to the remote server (you can check in the Pervasive Monitor)?
    2. If not, switch to TCP/IP. Does the error still occur?
    Yes, I am using TCP/IP only. I removed the other options from the list.

    3. Is there any pattern to this error? For example, does it always occur around 9am (based on the entry in PVSW.LOG)?
    4. If what else is happening when the error occurs? For example, is a virus scan or spyware scan or backup occurring?
    Seems random.

    Code:
    01-17-2006 12:13:02 W3NSL244        000006EC ntvdm.exe       CFS-PC81        E                        3112: Status 10054 returned while receiving a maximum of 40960 bytes.
    01-18-2006 11:56:56 W3NSL244        0000083C ntvdm.exe       CFS-PC81        E                        3112: Status 10054 returned while receiving a maximum of 40960 bytes.
    01-19-2006 09:04:37 W3NSL244        00000B38 ntvdm.exe       CFS-PC81        E                        3112: Status 10054 returned while receiving a maximum of 40960 bytes.
    01-20-2006 12:10:32 W3NSL244        00000D7C ntvdm.exe       CFS-PC81        E                        3112: Status 10054 returned while receiving a maximum of 40960 bytes.
    01-20-2006 15:01:04 W3NSL244        0000096C ntvdm.exe       CFS-PC81        E                        3112: Status 10054 returned while receiving a maximum of 40960 bytes.
    01-23-2006 12:03:18 W3NSL244        0000029C ntvdm.exe       CFS-PC81        E                        3112: Status 10054 returned while receiving a maximum of 40960 bytes.
    01-24-2006 12:03:28 W3NSL244        00000D00 ntvdm.exe       CFS-PC81        E                        3112: Status 10054 returned while receiving a maximum of 40960 bytes.
    I think the two at 12:03 are just coincidence.

  6. #6
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    The 10054 is a Winsock error and means:
    Connection reset by peer. 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.

    THis indicates a network communication problem. You'll need to fix that to get Pervasive working correctly. You might be able too turn on PARC at both the client and server to workaround it but you will probably see some performance degradation when the network disconnects/reconnects.
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  7. #7
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    The 10054 is a Winsock error and means:
    Connection reset by peer. 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.

    THis indicates a network communication problem. You'll need to fix that to get Pervasive working correctly. You might be able too turn on PARC at both the client and server to workaround it but you will probably see some performance degradation when the network disconnects/reconnects.
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  8. #8
    Join Date
    Jan 2006
    Posts
    3

    I have 'fixed' the problem...

    Well, the auto reconnect works. When I turned it on originally, I didn't realize there was a setting on the 'server' as well, so I had only changed the client. Haven't had any errors in over four days now.

    Obviously we must have some small network glitch, but a little performance degradation now and then is much preferable to requiring a restart of the directory program. We'll just have to see if adding two more users makes it any slower.

    Thanks for your help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •