SQL Server Performance

ConnectionRead (recv()) Error

Discussion in 'General DBA Questions' started by akothand, Jul 8, 2004.

  1. akothand New Member

    We have a PeopleSoft process that connects to our SQL Server database and reads / changes data. Occassionally , this process errors out giving this SQL Error
    SQL error. Stmt #: 1450 Error Position: 0 Return: 8200 - [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
    [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
    Please let me know if you have faced this SQL Error ?
    Thanks


    Thanks,
    Anand.K
    akothand@indymacbank.com

    "What would you attempt to do if you knew that you could never fail"
    -Robert Schuller
  2. Luis Martin Moderator

    What version of ODBC or MDAC do you have?

    Luis Martin
    Moderator
    SQL-Server-Performance.com

    All postings are provided “AS IS” with no warranties for accuracy.

  3. anupchintawar New Member

    I was facing same error few days back while running SP from client.
    Try with the following options.
    1. Check for the network.
    2. Change the Timeout value
    3. Change the KeepAlive value in the registry for the TCP/IP protocol

    -Anup
  4. satya Moderator

    What is the level of service pack on SQL?
    What is the authentication mode used to connect SQL Server?

    Similar event that if you use SQL Server Profiler or the xp_trace_setqueryhistory extended stored procedure to enable SQLTrace, a new connection to SQL Server will result in a memory and handle leak within Sqlservr.exe by Sqltrace.dll.


    Check SQL Server error log for more information.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  5. Argyle New Member

    Is the Peoplesoft process on the same server? Then it's most likely an mdac issue. If it's on a seperate server it could be network related as well as mentioned above (bad network card, bad cable, packetloss, high pings, timeouts on network, name resolution etc).
  6. akothand New Member

    We are on MSAC 2.7SP1. Today we are facing the same error.


    Thanks,
    Anand.K
    akothand@indymacbank.com

    "What would you attempt to do if you knew that you could never fail"
    -Robert Schuller
  7. akothand New Member

    Yes, I have asked the user to execute it from a different server to verify the MDAC part.
    Thanks for your suggestions all. We are in SQL 2000 Sp3a.. MDAC 2.7sp1


    Thanks,
    Anand.K
    akothand@indymacbank.com

    "What would you attempt to do if you knew that you could never fail"
    -Robert Schuller
  8. akothand New Member

    Hi All,
    The same process ran when executed from another server (means using another MDAC )
    Assuming that we have a problem with MDAC, can I just re-install this ?
    I am concerned as our SQL server is part of a SQL cluster. so How big is this effort of re-installing the MDAC ?
    Thanks for your time.



    Thanks,
    Anand.K
    akothand@indymacbank.com

    "What would you attempt to do if you knew that you could never fail"
    -Robert Schuller
  9. Argyle New Member

    It's still not clear to me if you run the Peoplesoft process on the same server as sql or not. If not and you verfied from anotehr client/server just upgrade mdac on the client/server that has the issue and not the sql cluster itself.
  10. satya Moderator

  11. akothand New Member

    Yes, we run the process in the SQL server itself, no client machines involved.and today the error came back <img src='/community/emoticons/emotion-6.gif' alt=':(' /> i did search in MSDN and he has so many possiblities...We left it in the backburner as the error went off...But today, we are stuck again .<br /><br /><br />Thanks,<br />Anand.K<br />akothand@indymacbank.com<br /><br />"What would you attempt to do if you knew that you could never fail"<br />-Robert Schuller<br />
  12. satya Moderator

    Have you reinstalled client tools or MDAC before this?

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  13. akothand New Member

    No. We went live directly with this current setup..SQL Server 2000 sp3a with Mdac 2.7sp1..
    heard 2.8 has come out..but upgrading this MDAC in production will be a big deal.


    Thanks,
    Anand.K
    akothand@indymacbank.com

    "What would you attempt to do if you knew that you could never fail"
    -Robert Schuller
  14. Luis Martin Moderator

    I suggest to find a windows to install 2.8.


    Luis Martin
    Moderator
    SQL-Server-Performance.com

    All postings are provided “AS IS” with no warranties for accuracy.

  15. satya Moderator

    The error looks to be a connectivity problem in the ODBC connections.
    Since you've identified that it is only with your PC, here is a quick list of things to check:

    * Do you have a valid ODBC entry? Make sure everything is set per the manual.
    * If you have a valid ODBC entry does it work using the MS Query or MS Access? This is the quickest way to see if the ODBC driver is setup properly. If you can connect to the database using either Access or Query then Psoft should work.



    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  16. alurizar New Member


    This happend to me when I ran out of free connections to the server. use SP_CONFIGURE to see check your configuration.
  17. SpoonyDunappa New Member

    I stumbled across this page when i too was experiencing the same problem. I've now got it working. My problem was that i was accessing the MSSQL database through an ODBC Connection. I changed my ADO ConnectionString to connect direct to the server and, hey presto, it worked.<br /><br />My old connection string:<br />ODBC;DSN=[ODBC DSN];UID=[Username]<img src='/community/emoticons/emotion-4.gif' alt=';P' />WD=[Password];DATABASE=[Database name] <br /><br />My new connection string:<br />Provider=SQLOLEDB.1;Data Source=[MSSQL server IP];User Id=[Username]<img src='/community/emoticons/emotion-4.gif' alt=';P' />assword=[Password];Initial Catalog=[Database name]<br /><br />Good luck!

Share This Page