Re: MS SQL Server 2008 R2 and freetds 0.82

Doug <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <[email protected]>
Hi,

Tried that with the 0.82 patched version and still had the same issue :(  Any suggestion if anything else might be incorrect?  Thanks a million. 
       
Doug

-------------------------------
token.c:495:tds_process_tokens(0x539360, 0x7fbfffed70, (nil), 0x6914)
util.c:162:Changed query state from PENDING to READING
util.c:334:tdserror(0x538120, 0x539360, 20004, 104)
util.c:368:tdserror: client library returned TDS_INT_CANCEL(2)
util.c:389:tdserror: returning TDS_INT_CANCEL(2)
util.c:162:Changed query state from READING to DEAD
token.c:510:processing result tokens.  marker is  0()
token.c:108:tds_process_default_tokens() marker is 0()
token.c:111:leaving tds_process_default_tokens() connection dead
util.c:110:logic error: cannot change query state from DEAD to PENDING
mem.c:609:tds_free_all_results()



--- On Fri, 2/25/11, Ken Collins <[email protected]> wrote:

> From: Ken Collins <[email protected]>
> Subject: Re: [freetds] MS SQL Server 2008 R2 and freetds 0.82
> To: "FreeTDS Development Group" <[email protected]>, "Frediano Ziglio" <[email protected]>
> Date: Friday, February 25, 2011, 7:15 AM
> 
> Nice! I had a few reports of this from TinyTDS too and
> ended up doing an insane amount of defensive programming to
> adjust for it. Good to know the latest updates work. 
> 
>  - Ken
> 
> > It's a known problem related to a mis-detected timeout
> reported as a
> > read error. Use post 0.82 patches (http://freetds.sourceforge.net/) or
> > patched version.
> > 
> > bye
> > freddy77
> > _______________________________________________
> > FreeTDS mailing list
> > [email protected]
> > http://lists.ibiblio.org/mailman/listinfo/freetds
> 
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.