Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Sorry.

With the above configuration, calls to at least mssql_query(); result in a PHP timeout. PHP apparently continues to run, or at least the webserver thinks it is, and the users browser does not display a new page until PHP times out. Behavior is weird, and an example is perhaps weird.

<?php
mssql_connect("host","user","pass");
echo "Foo!"; #Outputs Foo!

<?php

mssql_connect("host","user","pass");
echo "Foo!"; #Echos nothing apparently
flush(); #Doesn't help;
$q = mssql_query("some query");

The first case works, the 2nd doesn't.

Hrmm, can't seem to reopen. The status box only shows 'Bogus'

Reopened.

Additonal info: This occurs under apache as well, but I get an internal script error.

The problem occurs when a call to mssql_query matches at least one row. If a query does not match anything, PHP does not crash. But if it does, it crashes.

I experience the same problem using Apache 1.3.20 on Windows 2000.

The bug shows with mod_php and PHP as CGI (both 4.1.2).

SQL Server 2000 (Dev. Ed.) is installed on the same machine.


Connecting to the server and selecting a database is no problem, but any call to mssql_query() causes PHP to crash. I find no messages in the errorlog (except for a 'Premature end of script headers' with the CGI version).

Interesting is the fact that mssql_query() behaves as expected (no errors) only if the query returns 0 rows.

After some hasling with the configuration, I have found a solution (for both mod_php and CGI) in setting the mssql.compatability_mode option to 'Off':

mssql.compatability_mode = Off


I also noticed this bugreport, with the same solution:
http://bugs.php.net/bug.php?id=15890

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip

No feedback was provided for this bug for over 2 weeks, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".