Sybase/MSSQL
| From: | Richard Lynch | Date: | Thu, 15 Nov 2001 00:36:07 +0000 |
| Subject: | Sybase/MSSQL | ||
| Groups: | php.install | ||
| Request: | Send a blank email to php-install+get-4956@lists.php.net to get a copy of this message | ||
Mandrake 8.0
PHP 4.0.6
I have tried both Sybase-ct and freetds.
(Current stable versions, whatever those numbers are)
With Sybase-ct, I can actually connect to my local ASE server and do "sp_help" and yield a
reasonable response (both from isql and from PHP)
But attempting to connect to a remote MS SQLserver (in either isql or PHP) yields:
CT-LIBRARY error:
ct_connect(): network packet layer: internal net library error: Net-Library operation
terminated due to disconnect
(Can anybody translate that error message into layman's terms?...)
I am reasonably certain I have the correct IP and port for db1 in interfaces, since I can telnet to
those settings and get a response. I'm not sure about the "ether" versus
"eth0" setting, but neither one works...
Using the domain name rather than IP yields the same results.
db1
master tcp eth0 192.168.1.20 1433
query tcp eth0 192.168.1.20 1433
lynchux
master tcp ether windows11 4104
query tcp ether windows11 4104
Trying FreeTDS, I get an error from make about not finding -lsybtcl. I can "fix" that by
editing the Makefile by hand and adding /opt/sybase to the library path, since that's the only
place I can find any libsybtcl.so file on the entire system, but that just makes Apache segfault...
And isql is not at all happy about trying to use the FreeTDS directory for its SYBASE setting...
Some error message about a missing directory... Sorry, I got so frustrated at this point with
FreeTDS, since Sybase at least let me talk to ASE that I gave up on FreeTDS.
Is FreeTDS supposed to make its own libsybtcl or what?
I used the FreeTDS configure line from the PHPBuilder article:
/configure --with-tdsver=4.2 --enable-msdblib --enable-dbmfix --with-gnu-ld --enable-shared
--enable-static
http://phpbuilder.com/columns/alberto20000919.php3?page=3
I did not apply the patch because (A) I couldn't find it, and (B) it was for 4.0.2, so I was
hoping 4.0.6 would already have had it applied... But I followed all the other instructions in the
article, almost for sure. I'm not 100% certain it's SQL 7.0 Service Pack 2 -- The MS dba
just left. They reassured me very early in this process that they were running the latest and
greatest MS SQL Server, though.
Please help -- I'm at my wit's end to make PHP talk to SQL Server. This should not be
this tricky.
--
Like Music? http://l-i-e.com/artists.htm