Search results matching tag 'mssql fastcgi bug extension'

Re: mssql_connect()

jpreed00 — Tue, 29 Apr 2008 23:46:25 GMT

I am getting this exact same response when using the php_mssql extension. I've tried the thread safe binaries of php 5.2.5, the non-thread safe binaries as well as trying mssql_pconnect vs. mssql_connect.

I am absolutely certain that the connection to the database server is open, as I can telnet to the sql server via the proper port. It *may* be a permissions error, but as I'm using SQL authentication rather than windows authentication, it shouldn't be.

Running the php scripts from the command line result in the proper output, it's only when FastCGI executes that this error is generated.

Any ideas about what this could be?

Re: mssql_connect()

nwood888 — Tue, 06 Feb 2007 15:47:19 GMT

Rick, Thanks for the response. I had actually tried from the command line (and noted such in my post). Unfortunately, it works as expected from the command line, returning a resource id. It's only through FastCGI that it doesn't work. I have yet to test it with preview 2, but will do so when time permits.

Thanks again,

Nick

mssql_connect()

nwood888 — Thu, 04 Jan 2007 04:33:03 GMT

Has anyone had issues using mysql_connect() under this new FastCGI? I realize this is likely not a bug within FastCGI itself, but was hoping maybe someone had stumbled across a fix.

The script I'm running is very simple:

<?php print_r(mssql_connect('host,port','user','pass')); ?>

Testing from the command line works as expected. I receive a mssql resource id. Testing through FastCGI, however, results in a connection failure:

PHP Warning: mssql_connect() [function.mssql-connect]: Unable to connect to server: localhost,1057 in C:\...\test.php on line 1

I've tested with both 5.1.6 and 5.2.0.

Thanks,

Nick