Post reply

SQL Server 2005, ConnectionCheckForData error

  • February 12, 2008 at 8:23 am

    #183831

    I have a problem running my app on a machine where SQL Server 2005 with CU4 installed (on Windows 2003).

    If I connect my app to a remote SQL server, my queries are executed correctly.

    If I connect an app from other desktops to SQL 2005, the same queries are executed correctly.

    I tried different protocols (Shared memory, Named pipes). It seems that Shared Memory is the most fragile: my app fails within 5-10 mins. A connection using Named Pipes can stay up longer.

    An error is [ODBC SQL Server Driver] [protocol_name] ConnectionCheckForData (CheckData()).

    Any help would be appriciated.

  • February 12, 2008 at 10:12 am

    #777424

    Shared Memory should be for local connections only. You should be using TCP Sockets for your app.

    I don't see the problem. You say queries are correct either way.

  • February 12, 2008 at 10:24 am

    #777433

    Yes, I ONLY have a problem for local connections.

    I can't get the app ON THE LOCAL SQL server to run. Connections are dropped at random.

    I tried with Shared Memory, then forced my connection to use Named pipes by creating an alias via Client Nework Utility. Same result (though Shared Memory disconnects faster).

    DBCC CHECKDB did not find any problems with the db.

    The remote connections are always fine.

    Thank you.

  • May 3, 2008 at 8:39 am

    #810426

    Maybe there is a problem with ODBC connection. Try to open ODBC (windows start\control panel\administrative tools\data source ODBC ).

    Delete previous defination and make a new one as your database table structure.

    Regards,

    Julie Bunavicz

Viewing 4 posts - 1 through 3 (of 3 total)

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