[unixODBC-support] Mistery failure
sales at minixel.com
Tue Oct 2 11:04:53 BST 2007
The driver is supposed to be dumping to /tml/freetds.log, but I erased the
file and did my isql mssql user pwd and the file was not created. It means
probably that freetds is not being called at all. Any suggestion as how to
inspect what isql is actually looking for that does not find?
I did a ldd isql and all the sub-libraries do exist.
If you have a minute I can send you the ip address and pwd for the box.
Maybe you'll get lucky.
From: unixodbc-support-bounces at easysoft.com
[mailto:unixodbc-support-bounces at easysoft.com] On Behalf Of Nick Gorham
Sent: Tuesday, October 02, 2007 5:57 AM
To: Support for the unixODBC project
Subject: Re: [unixODBC-support] Mistery failure
Federico Alves wrote:
>I have freetds 0.64 and UnixODBC latest from Redhat
>Tsql works fine against SQL 2005. I also have the servername in odbc.ini
>also in freetds.conf
>I also compiled freetds having installed unixODBC-devel first.
Well, its getting to the driver, so I guess either the driver can't read
the ini entries, or its some other freetds based issue. Maybe turn some
driver logging on.
unixODBC-support mailing list
unixODBC-support at easysoft.com
More information about the unixODBC-support