FreeTDS Development Group

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

> From: Frank M. Kromann [mailto:frank AT kromann.info]
> Sent: January 5, 2003 5:55 PM
> 
> > $MS_CONN=mssql_connect("$MS_SQL" , "$MS_USER" , "$MS_PASS" );
>
> If $MS_SQL contains an alias for database you might have a 
> problem reading
> the configuration file. You could try to use the IP address directly.

Don't do that.  

Sorry, I don't want to sound abrupt, but I need to be plain.  

If you suspect problems with freetds.conf, set the TDSDUMPCONFIG variable
and examine the output.  

If you follow Mr. Kromann's advice and use the IP address, you will cause
FreeTDS to bypass reading freetds.conf.  In so doing, it will miss other
important connection information, including what version of the TDS protocol
to use (falling back on the --with-tds-version configure switch, or 5.0 if
that wasn't set).  Unless FreeTDS's default TDS version happens to match
your server's, you won't get a connection (or not of the kind you want).  

Hans, if something works interactivesly and not when launched by cron, the
problem has to be environmental.  It could be FreeTDS's variables (which
you've verified), or path/permission issues.  I suggest turning on
TDSDUMPCONFIG and TDSDUMP; I think what you see in the logs will make the
difference clear.  

HTH.

--jkl


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.