ID: 16411
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: MSSQL related
Operating System: Windows 2000
PHP Version: 4.3.0
New Comment:
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.
Previous Comments:
------------------------------------------------------------------------
[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
------------------------------------------------------------------------
[2003-01-06 12:02:13] [EMAIL PROTECTED]
What version of the MDAC are all of you using? I've heard that the
latest MDAC causes a lot of problems and that many users are
downgrading to the last version. Just wondering if this might be true
or not for any of you.
------------------------------------------------------------------------
[2003-01-02 09:27:17] [EMAIL PROTECTED]
I have experienced the same bug when running Win2000 Server and MS Sql
2000. MS SQL 7 would not produce this error.
The error has been reproduced in all PHP versions I've tried up to
4.3.0.
I've tried to use delays and change preformance parameters in MSSQL,
but no luck there.
A temporary solution would be to rewrite the code to use ODBC for
database calls. This cannot be considered a acceptable solution, but it
does work for us until this bug is corrected.
------------------------------------------------------------------------
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
