Skip to Content.
Sympa Menu

freetds - [freetds] tsql script problems

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Tony Baldarelli" <tbaldarelli AT wmsvision.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: [freetds] tsql script problems
  • Date: Fri, 8 Apr 2011 19:38:14 -0400

Hello,

I have a simple SQL script that works without incident:

[tonyb:v9_odbc:V3_18]> tsql -S MyServer2005 -U <user id removed for
security> -P <password removed for security> << EOF

> select count(*) from mbo;

> go

> EOF

locale is "en_US"

locale charset is "ISO-8859-1"

1> 2>

3614

(1 row affected)

1> [tonyb:v9_odbc:V3_18]>



See below for the logs:

1. Development machine #1 log file: http://goo.gl/n4ZYU

2. Development machine #1 TDSDUMP output: http://goo.gl/JCsrA

3. Development machine #2 log file: http://goo.gl/xuosy

4. Development machine #2 TDSDUMP output: http://goo.gl/4FaIJ





But then I have a more complex one that gives me an error on the machines
using a newer version of tsql ( 0.82 ), using GNUTLS for SSL encryption.
The error I get is here:

+ tsql -S MyServer2005 -U nortel -P builder789

locale is "en_US"

locale charset is "ISO-8859-1"

^MMsg 20004, Level 9, State -1, Server OpenClient, Line -1

Read from the server failed

locale is "en_US"

locale charset is "ISO-8859-1"

1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21>
22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40>
41> 42> 43> 44> 45> 46> 47> 48> 49> 50> 51> 52> 53> 54> 55> 56> 57> 58> 59>
60> 61> 62> 63> 64> 65> 66> 67> 68> 69> 70> 71> 72> 73> 74> 75> 1>



This SQL works on another machine that uses a different version of tsql (
albeit accessing a different SQL Server, with SSL off ).

1. Development machine #1 log file: http://goo.gl/StfNy

2. Development machine #1 TDSDUMP output: http://goo.gl/7D3wH

3. Development machine #2 log file: http://goo.gl/xYXWo

4. Development machine #2 TDSDUMP output: http://goo.gl/CVXOm

5. Production machine log file: http://goo.gl/KeLaX

6. Production machine TDSDUMP output: http://goo.gl/vOXTa



I mention the production server only because the exact same SQL script works
there. So the problem is not the SQL script itself. It is something with
tsql. I suspect it is something with gnuTLS, based on the TDSDUMP file, but
that is just a guess.



I am currently waiting for a patch that should let me use openssl instead of
gnuTLS, but I need to attach this issue from all angles in case the openssl
option does not work. Thus my trying to get gnuTLS to work. Thanks for
your help.





Tony







Archive powered by MHonArc 2.6.24.

Top of Page