ID: 20704 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: No Feedback Bug Type: MSSQL related Operating System: Windows2000+SP3/Dual PHP Version: 4.3.0RC2 New Comment:
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". Previous Comments: ------------------------------------------------------------------------ [2002-11-29 00:58:26] [EMAIL PROTECTED] 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". Thank you for your interest in PHP. ------------------------------------------------------------------------ [2002-11-28 22:05:07] [EMAIL PROTECTED] Good news: 4.2.3 doesn't crash so far. I upgraded because after some time I would randomly get Access Violations. But I prefer to have a few here and there than 100% of the time <g>. ------------------------------------------------------------------------ [2002-11-28 22:04:19] [EMAIL PROTECTED] Could you show the smallest possible version of the script, which causes the problem? ------------------------------------------------------------------------ [2002-11-28 14:30:33] [EMAIL PROTECTED] I just tried ISAPI with RC2; first script load is Ok, resubmit and it's an access violation. ------------------------------------------------------------------------ [2002-11-28 14:16:28] [EMAIL PROTECTED] It's a flat PHP setup with only mssql module loaded. Since the last MSSQL2000 (SP2+hotfix) and MDAC 2.7, SQL queries returning more than a few results crash (either Access Violation using ISAPI, or no output at all with php-cgi.exe past the mssql_query() call). Each time I install a different php build, the first script load will output something before dying in the middle of returning results; reloading the page will give CGI errors. Weird thing is, calling php.exe on the command line works each time; calling php-cgi.exe doesn't (problem described above show up). I can't even move those scripts to Unix, since some are using mssql_next_result() which Sybase doesn't provide. Ouch! It looks like using PHP to talk to MSSQL is not a good idea on any OS. Thanks for your help, -Martin ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20704&edit=1
