Skip to Content.
Sympa Menu

freetds - AW: AW: AW: AW: AW: AW: [freetds] connect problem to mssql 7.0

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Roland Bole" <roland.bole AT gmx.at>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: AW: AW: AW: AW: AW: AW: [freetds] connect problem to mssql 7.0
  • Date: Fri, 26 Dec 2003 08:34:42 +0100

To solve my connection problems i use now mssql_connect instead
mssql_pconnect.

But for other usage we should found and fix this problem.

Roland





-----Ursprüngliche Nachricht-----
Von: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] Im Auftrag von James K. Lowden
Gesendet: Donnerstag, 25. Dezember 2003 23:05
An: TDS Development Group
Betreff: Re: AW: AW: AW: AW: AW: [freetds] connect problem to mssql 7.0

On Wed, 24 Dec 2003, "Roland Bole" <roland.bole AT gmx.at> wrote:
> 17:42:11.481018 processing row tokens. marker is fd(DONE)
> 17:42:11.481068 tds_process_end: more_results = 0
> was_cancelled = 0
> error = 0
> done_count_valid = 1
> 17:42:11.481125 tds_process_end() state set to TDS_IDLE
> 17:42:11.481172 rows_affected = 1
> 17:42:11.481219 leaving dbnextrow() returning -2
> pid: 21085:17:42:20.358919 UNIMPLEMENTED dbsettime()
> pid: 21085:17:42:20.359072 UNTESTED dbsetmaxprocs()
> pid: 21085:17:42:20.372803 dbuse()
> pid: 21085:17:42:20.372955 dbcmd() bufsz = 126
> pid: 21085:17:42:20.373068 in dbfreebuf()
> pid: 21085:17:42:20.373181 in dbsqlexec()
> pid: 21085:17:42:20.373290 in dbsqlsend()
> pid: 21085:17:42:20.373413 tds_put_string converting 8 bytes of "use
> ELBE" pid: 21085:17:42:20.373549 tds_put_string wrote 16 bytes
> pid: 21085:Sending packet @ 17:42:20.373665
> 0000 01 01 00 18 00 00 01 00-75 00 73 00 65 00 20 00 |........ u.s.e. .|
> 0010 45 00 4c 00 42 00 45 00- |E.L.B.E.|
>
>
> pid: 21085:TDS: Write failed in tds_write_packet
> Error: 104 (Connection reset by peer)
> pid: 21085:17:42:20.374033 tds_client_msg: #20006: "Write to SQL Server
> failed.". Connection state is now 0.

This log shows you're not calling dbresults() a final time before dbuse().
I don't know if that's the problem, but I know it's improper. If the
server's expecting you to read something and receives a packet instead, it
might well decide to disconnect.

In the log, just above the chunk you sent, is the data packet from the
server. Does it indicate there's more coming?

--jkl

_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds






Archive powered by MHonArc 2.6.24.

Top of Page