ID: 16411
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Feedback
+Status: No Feedback
Bug Type: MSSQL related
Operating System: Windows 2000
PHP Version: 4.3.0
New Comment:
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.
Previous Comments:
------------------------------------------------------------------------
[2003-01-15 21:19:06] [EMAIL PROTECTED]
I doubt that Perl solution will fix this, but I hope that this issue
stays at the forefront until it can either be fixed with a PHP-side
workaround or we find someone at microsoft who's friendly to our cause
(not easy to do when you keep making fun of their name).
>From what I've seen in a lot of messages, mostly looking at #9852, and
have seen some common threads:
Most people with this issue have SQL 2000.
Mpwti have fast servers.
Mpwti have redirects (location: or javascript's).
Some people have fixed this by changing server priority.
Sphftb implementing delays in their redirects.
Sphftb installing MDAC and security patches.
Sphftb setting IIS bandwidth limitations.
Sphftb switching away from PHP :[
It appears to a layman (who has many friends in QA roles) that we have
a problem with nearly simultaneous invocations of PHP -and- MSSQL.
Early in this thread, vielina indicated that they never encountered
this problem until SQL2K, so it would seem that a slave to the mssql
extension dll is the suspect.
This supports most of the workaround suggestions I've seen - changing
foreground/background status would impact the execution times of these
scripts, slow links would prevent the redirect from turning into a GET
so quickly, etc. Some people have had luck using javascript redirects
- I have seen improvement, but not elimination of the issue.
For myself, I'm considering just doing away with my attempts to rewrite
dirty, complicated URLs. I feel for those with frameset apps, as there
really is no avoiding this in such an environment.
One thought I just had, but it's a phenomenal longshot -- anyone diddle
with the SQL Server Compatibility level in the SQL2K server parms? You
can set compat. to earlier versions, but I have no clue what that
means. I have never reproduced this on localhost (WinXP with PWS and
MSDE SQL server)...
------------------------------------------------------------------------
[2003-01-14 14:05:07] [EMAIL PROTECTED]
I just found the solution, at least for my problem.
I have a very simple Perl script, that was giving this error.
When I added to the top of the file:
print "Content-type: text/html\n\n";
the error from IIS is gone.
I hope this helps you PHP folks.
------------------------------------------------------------------------
[2003-01-14 13:35:53] [EMAIL PROTECTED]
I too get this error message. I am using Win 2000, IIS; and Perl
5.6.1. My Perl script is simply:
print "hello";
so I do not think the problem has anything to do with SQL.
------------------------------------------------------------------------
[2003-01-10 14:30:56] [EMAIL PROTECTED]
I can also verify the problem. MSSQL_ call followed by a header
redirect produces this problem more often than it doesn't. IIS5 with
php 4.2.x.
Since I've been fighting this problem off and on over the last few
months, I've had to switch to ODBC to meet an upcoming launch date.
However, I'll continue to follow and contribute any info I can when
time allows.
------------------------------------------------------------------------
[2003-01-06 12:03:30] [EMAIL PROTECTED]
Updating version
------------------------------------------------------------------------
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/16411
--
Edit this bug report at http://bugs.php.net/?id=16411&edit=1
