ID: 21872 Comment by: seang at moosecat dot com dot au Reported By: khoker at rjobrien dot com Status: No Feedback Bug Type: MSSQL related Operating System: Windows 2000 PHP Version: 4.3.0 New Comment:
I have also had a similar problem - although I am not sure of the OS - phpinfo says that it is: Windows NT IIS 5.0 build 2195 with an odbc / MS SQL combo I don't get it on my XP Pro Server... - with a MySQL combo I can rule out the odbc connection - although when I do switch the odbc back on the error happens 2-3/5 times. When it is off I get it about 1/20 times. It seems to be a time issue with the server - if there is no header out put within a certain amount of time (in this case less than a second) - then there is a CGI Error.... The extra time to connect to the db seems to cause the error to happen more frequently..... I will try a few more ideas now - like trying to flush some data through at the beginning of the script...... seang Previous Comments: ------------------------------------------------------------------------ [2003-02-07 23:52:47] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2003-01-27 02:12:51] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip There were some mssql related fixes which didn't make it to 4.3.0..so please give the snapshot a go. ------------------------------------------------------------------------ [2003-01-25 20:36:52] khoker at rjobrien dot com I have also made a test script on a dev box available to the outside world. If a PHP developer was interested in seeing the error I will provide the link through e-mail. Thanks. ------------------------------------------------------------------------ [2003-01-25 20:19:32] khoker at rjobrien dot com Unfortunately, applying the aforementioned patches to my production server does not eliminate the problem. That box is a Dual Xeon of some speed, as opposed to my single P4 testing box. In order to exhibit the error there, I re-create the test script above to hold 50 iframes. I see the error approximately one out of 400 requests in conjunction with a MSSQL/ODBC call. I appologize for making you read all this. ------------------------------------------------------------------------ [2003-01-25 18:21:01] khoker at rjobrien dot com As of this morning, I cannot duplicate the error on my test box (Win2000 professional). While I await the return of the CGI error, and if anyone is curious, they could ponder the following changes I made to my system. I am not asking for this bug's state to be changed to BOGUS or CLOSED, I just want to continue providing as much information as I can. I know there are a lot of people experiencing similar problems. 1) I restarted my system, which I do every few weeks. However, this hasn't solved anything in the past, but I wanted to include it just because it could offer a clue if the problem doesn't present itself until X hours after a reboot. (Probably not a good clue, but a clue none-the-less). 2) In restarting my system, I also applied the latest patches recommended by Microsoft's Windows Update. These patches were from the last two weeks, and did not look to imply a fix for this issue. Again, these were the DEFAULT patches recommended. 3) I picked two additional patches from Windows Update that were not defaults. If anyone savvy with the Win32 programming of PHP is reading, I'd be curious if you could check out these two KB articles and see if they could possibly relate. The second one seems particularly interesting, as it relates specifically to timing. http://support.microsoft.com/default.aspx?scid=KB;en-us;Q322842 http://support.microsoft.com/default.aspx?scid=KB;en-us;Q322913 I think that is it. I understand it is extremely poor troubleshooting practice to attempt multiple 'fixes' at once, but when you've been struggling with something for months you tend to get to the point where you don't think any more changes will actually help anything. At least I can pinpoint the two added patches which might shed light on something. Again, I'll keep you posted and continue to test this issue, and would be happy to respond with any information requested. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/21872 -- Edit this bug report at http://bugs.php.net/?id=21872&edit=1
