Post reply

ODBC Communication link failure

  • June 18, 2007 at 11:54 am

    #68581

    Anyone help me to resolve this error message.

    ********************************************

    [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (InvalidParam()).

    Server: Msg 11, Level 16, State 1, Line 0

    General network error. Check your network documentation.

    ODBC: Msg 0, Level 16, State 1

    Communication link failure

    Connection Broken

     

    **************************

    Regards

    Karthik

    karthik

  • June 18, 2007 at 10:57 pm

    #713726

    May be your ODBC configuration is incorrect. The error clearly says invalid parameter check if you have given the right parameters and try creating the data source again.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • June 19, 2007 at 6:13 am

    #713788

    Check the following:

    1. Have you enabled protocol encryption?

    2. What is the version of the SQL Server ?

    3. Check the ODBC configuration

    4. Verify that the instance of SQL Server is listening on named pipes, TCP/IP, or another protocol that you are using at the client application.

    5. You can run the MDAC Component Checker to verify the MDAC installation on your computer.

      301202 (http://support.microsoft.com/kb/301202/) HOW TO: Check for MDAC version

    6. Are you able to ping the Server ?

     
    Minaz Amin

    "More Green More Oxygen !! Plant a tree today"

  • January 15, 2008 at 1:59 pm

    #768321

    Did any suggested check or resolution help resolve these random odbc communications link failures ? Curious, as I also am finding these in an applications log that used DSN' and BDE, talking to SQL2K-Sp4

  • June 22, 2008 at 4:49 pm

    #832421

    We also find these same odbc sql comm link failures. Failure point seems to be random, but we never see the error messages until the odbc link is tried; then error is raised. BDE 5.01 is integrl to the main server program. Bakend db SQL2000 SP4 running on Windows 2003 . Firewall does exsit in between comm server with failing links to backend sql.

  • June 24, 2008 at 8:12 am

    #833333

    Without knowing more about your issue this is all that I can offer:

    http://www.connectionstrings.com/

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • June 24, 2008 at 10:08 am

    #833426

    Thank you. Apreciate whatever help I can get. Not sure what details I should post specially.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply