Click to See Complete Forum and Search --> : Please help!!Embarressing situation.


Anon
07-13-2001, 05:48 PM
Hi,

I convinced our manager to use php.Now when the project is all done and we are demonstrating to one of our clients system is saying---PHP ENCOUNTERED ACCESS VIOLATION AT 0A5588U.
I rebooted my system and then everything is working fine.I am getting this error once in a while but absolutly have no idea why it is saying like that.

I am using PHP 4.0.4 installed as CGI module on win2000.I have MSSQL server at the back end.

Any one please help me with solutions or suggestions.
This is soo important to me.I have to answer to my manager.

Sagil.

Anon
07-14-2001, 04:42 PM
Sounds like a ram problem. Check your ram.

Anon
07-17-2001, 01:27 PM
I have what seems like a pretty similar setup (minus the SQL backend) and I get the same errors. I just have a computer setup in my house running Win2000/IIS 5/PHP 4.0.4 just to do development/testing on, and it seems that after the server's been running for a couple days or so all PHP scripts start producing this error. It's not a RAM problem; I've had no other problems with the machine at all, and I've had been using the server for many months doing ASP and other web development with no problems. Also, just like him, the problem is fixed with rebooting (or just restarting IIS). ASP scripts and regular HTML files are run and served just fine, but PHP scripts give this error after IIS has been running for a day or two.

If anyone can help with this I would also greatly appreciate it.

Thanks,
Andy

Anon
07-17-2001, 06:38 PM
I just looked through some of the installation and readme files that came with the win32 php .zip file and read that the ISAPI version of PHP for win32 may suffer from "serious reliability issues". Anyway, if you used something like the EasyWindows installer, or just set it up to run that way on your own, I'm thinking that may be the problem. I just edited my server to run PHP in the CGI mode (have "php.exe %s %s" execute .php files instead of php4isapi.dll) and things are working fine right now, but of course they worked fine for awhile the other way too. Anyway, I just thought I'd pass this along in case you missed that bit in the install.txt as I did. :)