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:

Another update....

>From research it only happens on Windows OS - and not all Set ups of
Windows.....  (it does not happen on my set up - just on my clients set
up)

Apparently - it is not just php it happens with it is ASP too....

However there seems to be a solution..... - or at least steps to reduce
the problem

http://bugs.php.net/bug.php?id=9852

>From : [4 Aug 2002 10:48pm CDT] scott at datalink dot net dot au 

onwards...

in particular...
[25 Oct 2002 10:15am CDT] dmendez at artech dot com dot uy 

& 

[28 Oct 2002 4:35am CST] ewald dot murgg at fh-joanneum dot at 

& 
[3 Mar 5:23pm CST] gkasten at filnet dot fr 
&

[20 Mar 5:10pm CST] ottawasixtyseven at hotmail dot com

Come down to setting the windows system performance to Background
Application - "Go to start button, control panel, system, advanced tab
then performance
option." to quote one of the posts....

also if it is still happening use SAPI modules (for exapmle
php4isapi.dll).  version instead of php.exe - see php.net


Previous Comments:
------------------------------------------------------------------------

[2003-08-08 00:00:53] seang at moosecat dot com dot au

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

------------------------------------------------------------------------

[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.

------------------------------------------------------------------------

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

Reply via email to