ID: 21681
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: IIS related
Operating System: Windows 2000
PHP Version: 4.3.0
New Comment:
I already had random "CGI Error" (HTTP 502 error) with IIS5+W2K+CGI
under heavy load.
I solved the pb by turning on the "Allow interaction with desktop"
option for IIS Admin service.
I guess there was sthg that needed to access desktop in my CGI
initialization phase (in some external libs?). Maybe it is the same
case with php.exe
I don't know if it can tamper with web server security.
Previous Comments:
------------------------------------------------------------------------
[2003-01-20 17:56:44] [EMAIL PROTECTED]
I have tried Microsoft sevral times but without luck. The DBLIB API we
are using for the MSSQL extensions has not been updated since SQL
Server 6.0, though Microsoft has released at least 3 versions since
then.
My best hope right now is to use FreeTDS on Win32 (as it is done on
*nix) but the Win32 port is, to my best knowledge, not stable at this
point. As soon as I have a FreeTDS version of DBLIB I'll make the MSSQL
extension work with it.
------------------------------------------------------------------------
[2003-01-20 03:59:59] [EMAIL PROTECTED]
A question for [EMAIL PROTECTED]:
can you give me please a tip to the CGI processes? Where must i set
this? Is this on IIS oder direct on Windows 2000 to set?
Or have you a more information about it?
Thanks and best regards,
Andi
------------------------------------------------------------------------
[2003-01-19 19:02:11] [EMAIL PROTECTED]
A question for [EMAIL PROTECTED]:
Is there anything you can do for this problem? If it isn't a piece of
code, perhaps a nice email to Microsoft or something like
that...Please. Microsoft won't come to PHP guys asking if there's
something they could do. It's you who must go to them. Furthermore,
your email would be a lot more powerful than an email from some
ordinary PHP developer. I mean, practically, this "bug" prevents me
from using ISAPI at all and as you may have noted I'm not the only one.
You've got to face the facts, because this "bug" might prevent ISAPI
from ever becoming for production use. So please, do something about
it. Hit the home run, because ISAPI is nearly there!
------------------------------------------------------------------------
[2003-01-18 18:48:32] [EMAIL PROTECTED]
Hi,
thanks for your tip, I will test it and return a feedback.
------------------------------------------------------------------------
[2003-01-18 18:38:02] [EMAIL PROTECTED]
This is a problem with missing thread safety in the Microsoft libraries
used to build the MSSQL extension. It can be used with ISAPI but you
can only get a stable system when using cgi or fastcgi.
The CGI error is not caused by either PHP or the MSSQL extension, but
rather a problem with IIS. CGI processes are launched in forground, but
the default setting for Windows NT/2000 is to optimize performence for
background processes. If you switch this the CGI errors will go away.
------------------------------------------------------------------------
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/21681
--
Edit this bug report at http://bugs.php.net/?id=21681&edit=1
