Skip to Content.
Sympa Menu

freetds - Re: [freetds] FreeTDS and MSSQL

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "James K. Lowden" <jklowden AT freetds.org>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] FreeTDS and MSSQL
  • Date: Mon, 21 Apr 2008 10:54:43 -0400

Hi Venkat,

> 0040 74 72 61 6e 73 61 63 74-69 6f 6e 5f 69 64 20 3d |transact ion_id =|
> 0050 27 31 35 39 36 33 63 38-35 2d 30 39 66 63 2d 34 |'15963c8 5-09fc-4|
> 0060 63 34 66 2d 39 33 61 62-2d 61 31 32 34 32 61 63 |c4f-93ab -a1242ac|
> 0070 35 65 61 63 34 2d 31 30-27 20 |5eac4-10 ' |
> 06:50:21.015 3312 (dblib.c:4297):dbsqlok(010B7BC0)
> 06:50:22.015 3312 (net.c:363):error: select(2) returned 0x2726, "Unknown
> error" 06:50:22.015 3312 (util.c:328):tdserror(010B7A08, 010B8340,
> 20004, 10022) 06:50:22.015 3312 (dblib.c:7583):dbperror(010B7BC0, 20004,
> 0) 06:50:22.015 3312 (dblib.c:7646):"Read from the server failed",
> client returns 2 (INT_CANCEL) 06:50:22.015 3312 (util.c:364):tdserror:
> client library returned TDS_INT_CANCEL(2) 06:50:22.015 3312
> (util.c:385):tdserror: returning TDS_INT_CANCEL(2) 06:50:22.015 3312
> (util.c:157):Changed query state from PENDING to DEAD

I'm sorry, I can't explain what you're seeing. The server seems to have
cut you off at the knees: you sent it a query, and it disconnected.

Usually that would make me suspect a network problem, but it's too neat:
the disconnection happens right at the packet boundary. That would seem
to suggest a protocol violation (because if you don't adhere to TDS rules,
you can expect to be disconnected ruthlessly) but I don't see any hint of
a problem.

> And, I am using FreeTDS within a PHP application. My client is
> a Windows XP machine and so I am using this windows
> implmentation of FreeTDS:
>
> http://kromann.info/php5_1-Release_TS/php_dblib.dll
>
> and the version I mentioned was from the log file:
>
> 06:50:20.671 3312 (log.c:190):Starting log file for FreeTDS 0.63
> on 2008-04-21 06:50:20 with debug flags 0xffff.

I see. It could be the Windows version isn't reporting its version
correctly. The version number is updated by the autotools that work in
Unix. Perhaps Frank's release notes shed some light?

Regards,

--jkl




Archive powered by MHonArc 2.6.24.

Top of Page