ID: 25579
Updated by: [email][/email]
Reported By: mfenton at learnkey dot com
-Status: Feedback
+Status: No Feedback
Bug Type: IIS related
Operating System: W2K3
PHP Version: 4.3.3
New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.

Previous Comments:

[2003-09-17 18:49:59] [email][/email]

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.

Please read the link above, and give us more information.
So far, your report is the equivalent of saying

"I have this really complex set of software, that links to some other
complex software. I also wrote some code that does some stuff, and we
get an error every so often".

Until you can provide some clues, keep this report set to feedback, as
it means we are waiting for your input.

May I remind you that there is no warranty for PHP and that we
explicitly warn you that running PHP ISAPI in production under windows
is not recommended in our doentation.


[2003-09-17 15:28:47] mfenton at learnkey dot com

On our website we get "PHP has encountered an Access Violation" at a
memory address, Yes this error is very limited in
saying what the problem is. Our servers are running W2K3, IIS6.0, PHP
4.3.3 with MSSQL 2000 on W2K3.

Now I've read many people having this problem, some say to just reset
the service, well thats fine, but not when you run a business and you
have many users online at all times.

Others said that there might be a problem using the php4isapi.dll and
using php as cgi fixes there issue, also read that there might be a
problem with the ODBC dll to connect up to the MSSQL database. There
isn't a fix for this (at least that I have read). In most posts the
quick solution is to either upgrade to the newest version or there
enough information.

We have recieved this error while in our Userend and our Backend.

This is a persistent problem for our website, this needs to be
ASAP. Any more information that will be helpful in determining the
solution to fix this problem I can provide upon request. Thanks for


Edit this bug report at [url][/url]