ID: 8548
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Closed
Bug Type: IIS related
Operating system: 
PHP Version: 4.0.4
Assigned To: 
Comments:

No feedback. And most likely user error.


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

[2001-06-09 23:58:07] [EMAIL PROTECTED]
sounds like stale dll's lying about possibly please clean any php related dll's (in 
the WINNT and system32 folders too) and try installing fresh.

- James

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

[2001-01-13 10:24:10] [EMAIL PROTECTED]
user feedback:

we are not using MS Visual Studio. But I found something new:

when I install 4.04 and replace the isapi.dll with the one from 4.03pl1 everything is 
fine. So the bug must be somehere in there.


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

[2001-01-08 16:15:07] [EMAIL PROTECTED]
do you by any chance have MS Visual Studio installed on that computer? If so, could 
you compile debug version of 4.0.4, and send a backtrace? (you can get it in the MS 
debugger under View -> Debug Windows -> Call Stack or by hitting ALT + 7)

win32 build instructions can be found at http://www.php.net/version4/win32build.php, 
ignore the notes on BCmath, it's not necessary to copy the files anymore.

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

[2001-01-04 08:01:50] [EMAIL PROTECTED]
I installed PHP 4.04 on W2K Server (GERMAN) with SP1. As soon as you try to execute a 
PHP Script (even the simplest possible echo "HELLO") you receive "INTERNAL SERVER 
ERROR".

We had to switch back to 4.03PL1.



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



ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=8548&edit=2


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to