FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: culikr AT brturbo.com [mailto:culikr AT brturbo.com]
> Sent: October 1, 2003 12:16 PM
> 
> Received packet @ 2003-10-01 12:47:50.994336
> 0000  81 01 00 00 00 01 00 e7  00 01 00 d1 06 00 64 00   
> |.......ç. ..Ñ..d.|
> 0010  62 00 6f 00 fd 10 00 c1  00 01 00 00 00            
> |b.o.ý..Á. ....|
> 
> 
> 2003-10-01 12:47:50.994384 dbsqlok() marker is 129
> 2003-10-01 12:47:50.994409 dbsqlok() found result token
> 2003-10-01 12:47:50.994454 inside dbresults_r() result_type = 
> 4049 retcode = 1
> Unrecognized TDS5_DYN subtoken 10,0
> Unknown marker: 193(c1)!!
> Unknown marker: 1(1)!!

Luiz, 

You might want to try a recent snapshot.  I remember fixing a similar
problem, but I'm not sure this was it.  

Otherwise, could you show us:

1.  more of the log, starting with the query being sent to the server
2.  the table definition
3.  the query

Does it fail with tsql?    

An analysis of the packets follows.  

--jkl

> 0000  81 

This is a TDS 7.0 result set packet.  It has 

>       01 00 : one column

>       00 00 : no user type

>       01 00 : nullable

>       e7    : type XSYBNVARCHAR

>       00 01 : up to 255 bytes long

>       00    : no name

0xE7 is also the TDS5_DYNAMIC_TOKEN.  It looks like
tds_process_result_tokens() mishandled the packet.  

>       d1 

Now comes the row.

>       06 00 : six bytes
>       64 00 62 00 6f 00 : "dbo"

Then the DONE packet:

>       fd 
>       10 00 : not the last packet
>       c1  00 : unknown
>       01 00 00 00 : rowcount is 1

-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact 
the sender immediately by reply e-mail and destroy all copies of the original 
message. Please note that we do not accept account orders and/or instructions 
by e-mail, and therefore will not be responsible for carrying out such orders 
and/or instructions.