FreeTDS Development Group

["James K. Lowden" <jklowden AT schemamania.org>]

On Tue, 6 Jan 2004 10:23:00 -0600 , "Daughterson, Adam [EPM/BOU/MMI]"
<Adam.Daughterson1 AT EmersonProcess.com> wrote:
> 
> This is really the part that intrests me the most:
> > root@USBOU1-DHDLINUX:/usr/local/etc# isql esp_ms_sql user passwd 
> > Starting log file for FreeTDS 0.62.dev.20031224
> >         on 2004-01-05 17:40:24 with debug level 99.
> > names for ISO-8859-1: ISO-8859-1
> > names for UTF-8: UTF-8
> > names for UCS-2LE: UCS-2LE
> > names for UCS-2BE: UCS-2BE
> > iconv to convert client-side data to the "ISO-8859-1" character set 
> > 17:40:24.654251 tds_iconv_info_init: converting 
> > "ISO-8859-1"->"UCS-2LE" 17:40:24.654360 IP address pointer is NULL 
> > 17:40:24.654401 Server SYBASE not found!
> > [ISQL]ERROR: Could not SQLConnect root@USBOU1-DHDLINUX:/usr/local/etc#

> Does this make any sense?  Why is the IP address pointer NULL?  Why is
> it looking for a Server called SYBASE, or more to the point, why does it
> bother looking for SYBASE at all?

Your question is, What's the "SYBASE" server and why is the pointer NULL? 


It's a little unintuitive, but the answer is clear.  FreeTDS was provided
a servername to look up, but it found no suitable entry.  In desparation,
it tried to look up a machine named "SYBASE", found none (hence, no
address, null pointer).  In 0.53, I remember, that used to cause a segment
fault; we consider these messages an improvement.   

Almost every time an ODBC user encounters this message, it's due to a
misconfiguration of the odbc.ini.  If the wrong DSN is passed, or the DSN
refers to a nonexistent freetds.conf entry, or the DSN refers to a
nonexistent DNS name, you'll see this message.  

If it's not clear where the error lies, try TDSDUMPCONFIG again.  I think
you'll see it trying to look up something you didn't quite expect.  

HTH.  

--jkl