Hi:
I've discovered something very interesting:
perhaps you already know that using PHP + IIS in ISAPI mode is not recommended,
because of the: "PHP has encountered an Access Violation at 73342C83" and so errors.
So CGI use is recommended. But I have found that this happens whenever
I'm a keen as you are for the PHP ISAPI module to work reliably, but before
we start sorting out the extension modules, we need to sort out the core
itself. For me (on my NT4/IIS4/SP6 setup), php 'straight out of the box'
falls over with server 500 errors on the simplest of scripts - even with
Hi:
3/7/01 11:33:18 AM, "Phil Driscoll" [EMAIL PROTECTED] wrote:
I'm a keen as you are for the PHP ISAPI module to work reliably, but before
we start sorting out the extension modules, we need to sort out the core
itself. For me (on my NT4/IIS4/SP6 setup), php 'straight out of the box'
falls
Paco wrote:
are you trying with 4.0.4pl1? Try, please. I had the same problems with
previous
Yes, I've been using 4.0.4pl1 since day '0', and it 'reliably' goes wrong
for me. Are you using NT4 or W2K?
Cheers
--
Phil Driscoll
Dial Solutions
+44 (0)113 294 5112
http://www.dialsolutions.com
Hi:
Yes, I've been using 4.0.4pl1 since day '0', and it 'reliably' goes wrong
for me. Are you using NT4 or W2K?
I'm using NT4, SP6 and IIS 4. I have the MSSQL 2000 client libraries installed
(MDAC 2.6) but I can't think they have any influence (the db API used by
php_mssql is backwards
