I have an intranet-only site running in Windows XPPro, IIS 5.1, PHP
5.2.5. I have not used or changed this site for several months - the
last time I worked with it, all was well.

When I tried it just now, I am getting the subject error message
(specifically: PHP has encountered an access violation at 00F76E21).

The error is NOT occurring on every page request (but it is on most of
them) and, when I get the error, simply pressing <F5to refresh the
page results in the page being served successfully.

Some googling around indicates that "permissions" are not set
correctly. But, if that was actually the case, a <refreshwouldn't
work either would it? This seems to be a sporadic issue.

Any ideas as to what's going on here?

On Thu, 04 Sep 2008 07:52:22 -0700, Martin <ironwoodcanyon@gmail.com>
wrote:

>I have an intranet-only site running in Windows XPPro, IIS 5.1, PHP
>5.2.5. I have not used or changed this site for several months - the
>last time I worked with it, all was well.
>
>When I tried it just now, I am getting the subject error message
>(specifically: PHP has encountered an access violation at 00F76E21).
>
>The error is NOT occurring on every page request (but it is on most of
>them) and, when I get the error, simply pressing <F5to refresh the
>page results in the page being served successfully.
>
>Some googling around indicates that "permissions" are not set
>correctly. But, if that was actually the case, a <refreshwouldn't
>work either would it? This seems to be a sporadic issue.
>
>Any ideas as to what's going on here?

Well, FWIW, re-booting the computer ALMOST fixed it. Now the error
seems to be encountered only on a couple of different pages - again,
it's at random - sometimes it happens and sometimes it doesn't. :(

"Martin" <ironwoodcanyon@gmail.comwrote in message
news:83vvb45p05r64lepnie529eudvck8s5ekj@4ax.com...

On Thu, 04 Sep 2008 07:52:22 -0700, Martin <ironwoodcanyon@gmail.com>
wrote:
>

>
Well, FWIW, re-booting the computer ALMOST fixed it. Now the error
seems to be encountered only on a couple of different pages - again,
it's at random - sometimes it happens and sometimes it doesn't. :(

nothing is random...and 'almost' is not 'fixed'. without seeing your code,
it's hard to tell what you may be doing.

On Thu, 04 Sep 2008 07:52:22 -0700, Martin wrote:

I have an intranet-only site running in Windows XPPro, IIS 5.1, PHP
5.2.5. I have not used or changed this site for several months - the
last time I worked with it, all was well.
>
When I tried it just now, I am getting the subject error message
(specifically: PHP has encountered an access violation at 00F76E21).
>
The error is NOT occurring on every page request (but it is on most of
them) and, when I get the error, simply pressing <F5to refresh the
page results in the page being served successfully.
>
Some googling around indicates that "permissions" are not set correctly.
But, if that was actually the case, a <refreshwouldn't work either
would it? This seems to be a sporadic issue.
>
Any ideas as to what's going on here?

What kind of load is it under? I don't know if it has anything to do with
your issue but IIS running under XP only allows 10 connections.

--
I told you this was going to happen.

On Thu, 4 Sep 2008 10:52:23 -0500, "Dale" <the.one@example.comwrote:

>
>"Martin" <ironwoodcanyon@gmail.comwrote in message
>news:83vvb45p05r64lepnie529eudvck8s5ekj@4ax.com.. .

>
>nothing is random...and 'almost' is not 'fixed'. without seeing your code,
>it's hard to tell what you may be doing.
>

By "random" I mean that I get the error one time when I view page "X"
but a subsequent viewing of the same page encounters no error. I might
view the page repeatedly without error and then, on the next view, the
error will appear.

On Thu, 04 Sep 2008 10:55:57 -0500, Ivan Marsh <ivanmarsh@yahoo.com>
wrote:

>On Thu, 04 Sep 2008 07:52:22 -0700, Martin wrote:
>

>
>What kind of load is it under? I don't know if it has anything to do with
>your issue but IIS running under XP only allows 10 connections.

No load whatsoever. Like I said, this is on my LAN (in my office where
I develop stuff) and I'm the only one using it.

On Thu, 04 Sep 2008 09:07:27 -0700, Martin wrote:

On Thu, 04 Sep 2008 10:55:57 -0500, Ivan Marsh <ivanmarsh@yahoo.com>
wrote:
>

>
No load whatsoever. Like I said, this is on my LAN (in my office where I
develop stuff) and I'm the only one using it.

Depending on how the page is designed and what it's doing a single page
load could create more than 10 connections.

Monitoring Connections (IIS 6.0)
http://www.microsoft.com/technet/pro....mspx?mfr=true

I'm sure the instructions for IIS 5 are similar.

--
I told you this was going to happen.

Martin schreef:

I have an intranet-only site running in Windows XPPro, IIS 5.1, PHP
5.2.5. I have not used or changed this site for several months - the
last time I worked with it, all was well.
>
When I tried it just now, I am getting the subject error message
(specifically: PHP has encountered an access violation at 00F76E21).
>
The error is NOT occurring on every page request (but it is on most of
them) and, when I get the error, simply pressing <F5to refresh the
page results in the page being served successfully.
>
Some googling around indicates that "permissions" are not set
correctly. But, if that was actually the case, a <refreshwouldn't
work either would it? This seems to be a sporadic issue.
>
Any ideas as to what's going on here?

Hi,

First, to find the reason for an access violation, you must use
debuggertools for IIS.
You can find better help in this newsgroup:
microsoft.public.inetserver.iis (also with finding the right tools to
create a bugreport.)
I heard PHP5.1.something had some issues when trying to free the same
amount of memory twice. (Not sure if that is related)

And I have a, possibly lame, suggestion: Switch to Apache (1.3 or 2).
Most techies consider IIS an inferior webserver.

Regards,
Erwin Moller

--
============================
Erwin Moller
Now dropping all postings from googlegroups.
Why? http://improve-usenet.org/
============================

Ivan Marsh schreef:

On Thu, 04 Sep 2008 09:07:27 -0700, Martin wrote:
>

>
Depending on how the page is designed and what it's doing a single page
load could create more than 10 connections.

Well, would that explain why it doesn't happen on the same page when it
is reloaded?
If the page does the same thing, why would 1 invocation create an error,
and the second not if he is the only one using that server?

I bet something else is wrong.
Best thing to do is switch webserver or diagnose the problem with some
tools. (see my other response).

Regards,
Erwin Moller

>
Monitoring Connections (IIS 6.0)
http://www.microsoft.com/technet/pro....mspx?mfr=true
>
I'm sure the instructions for IIS 5 are similar.
>

--
============================
Erwin Moller
Now dropping all postings from googlegroups.
Why? http://improve-usenet.org/
============================

Martin wrote:

(specifically: PHP has encountered an access violation at 00F76E21).

Off course there are many kinds of access violations, but this seems to
me like PHP is trying to read from a memory address it does not has
access to. This is most likely a bug in PHP (or some other software) or
broken hardware. Try testing your memory (maybe with memtest86) and up-/
downgrading your PHP.

Martin wrote:

I have an intranet-only site running in Windows XPPro, IIS 5.1, PHP
5.2.5. I have not used or changed this site for several months - the
last time I worked with it, all was well.
>
When I tried it just now, I am getting the subject error message
(specifically: PHP has encountered an access violation at 00F76E21).
>
The error is NOT occurring on every page request (but it is on most of
them) and, when I get the error, simply pressing <F5to refresh the
page results in the page being served successfully.
>
Some googling around indicates that "permissions" are not set
correctly. But, if that was actually the case, a <refreshwouldn't
work either would it? This seems to be a sporadic issue.
>
Any ideas as to what's going on here?
>

Martin,

There are several bug reports at bugs.php.net similar to what you are
reporting. But not knowing what your code is doing, I have no idea what
might be related.

You could look through them and see what you can find. Upgrading to
5.2.6 may also fix this bug.

And if you don't find anything, I would recommend you put together a
small test case showing the problem and report it as a bug.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

On Thu, 04 Sep 2008 14:50:08 -0400, Jerry Stuckle wrote:

Martin wrote:

Martin,
>
There are several bug reports at bugs.php.net similar to what you are
reporting. But not knowing what your code is doing, I have no idea what
might be related.
>
You could look through them and see what you can find. Upgrading to
5.2.6 may also fix this bug.
>
And if you don't find anything, I would recommend you put together a
small test case showing the problem and report it as a bug.

Most of the bug reports I've seen on this suggest it's an issue with
running PHP and an ISAPI filter.

Perhaps you could try setting it up as CGI. I vaguely remember running
into a similar issue the one time I attempted to run PHP under Windows.
Though I believe I solved (side stepped) the issue by running Apache
instead of IIS, which my not be a solution for you.


--
I told you this was going to happen.

"Erwin Moller"
<Since_humans_read_this_I_am_spammed_too_much@spam yourself.comwrote
in message news:48c011f2$0$184$e4fe514c@news.xs4all.nl...

>
Martin schreef:

>
Hi,
>
First, to find the reason for an access violation, you must use
debuggertools for IIS.
You can find better help in this newsgroup:
microsoft.public.inetserver.iis (also with finding the right tools
to create a bugreport.)
I heard PHP5.1.something had some issues when trying to free the
same amount of memory twice. (Not sure if that is related)
>
And I have a, possibly lame, suggestion: Switch to Apache (1.3 or
2).
Most techies consider IIS an inferior webserver.
>
Regards,
Erwin Moller
>

FWIW:
I have been struggling to solve a similar problem under Apache. :(

Still dont know the exact cause, but somehow a mySQL dll was the wrong
version.
Replcing it with another 'fixed' it.
How the wrong dll was referenced I still dont know.

Richard

Martin wrote:

I have an intranet-only site running in Windows XPPro, IIS 5.1, PHP
5.2.5. I have not used or changed this site for several months - the
last time I worked with it, all was well.
>
When I tried it just now, I am getting the subject error message
(specifically: PHP has encountered an access violation at 00F76E21).
>
The error is NOT occurring on every page request (but it is on most of
them) and, when I get the error, simply pressing <F5to refresh the
page results in the page being served successfully.
>
Some googling around indicates that "permissions" are not set
correctly. But, if that was actually the case, a <refreshwouldn't
work either would it? This seems to be a sporadic issue.
>
Any ideas as to what's going on here?

Some kind of internal bug in PHP. The access violation error tells
NOTHING and you don't need to waste time on it.

Try different PHP versions or use apache to host PHP scripts. Apache
is less problemic with PHP in my experience.

"AqD" <aquila.deus@gmail.comwrote in message
news:749059af-db00-426b-a549-bc1c5700d1b9@p10g2000prf.googlegroups.com...

Martin wrote:

>
Some kind of internal bug in PHP.

and exactly HOW would you know that?!

The access violation error tells
NOTHING and you don't need to waste time on it.

hmmm...it tells you the application is trying to do something that it is not
allowed to do. your comments seem to be the only thing wasting anyone's
time.

Try different PHP versions or use apache to host PHP scripts. Apache
is less problemic with PHP in my experience.

well, well, well. seems like you don't really think it is 'some kind of
internal bug in PHP' after all! now you're saying it's IIS, or any other
webserver but apache.

if you don't have enough information to go on, don't assume so wonderfully
and precisely what the specific problem is or what is going to solve it!

On Thu, 04 Sep 2008 20:19:50 +0200, Sjoerd <sjoerder@gmail.comwrote:

>Martin wrote:

>
>Off course there are many kinds of access violations, but this seems to
>me like PHP is trying to read from a memory address it does not has
>access to. This is most likely a bug in PHP (or some other software) or
>broken hardware.

Try testing your memory (maybe with memtest86) and up-/
>downgrading your PHP.

At your suggestion, I downloaded memtest86 and ran it but it reported
no memory problems - everything was ok.

Am continuing to try to diagnose the problem.

On Thu, 04 Sep 2008 14:50:08 -0400, Jerry Stuckle
<jstucklex@attglobal.netwrote:

>Martin wrote:

>
>Martin,
>
>There are several bug reports at bugs.php.net similar to what you are
>reporting. But not knowing what your code is doing, I have no idea what
>might be related.
>
>You could look through them and see what you can find. Upgrading to
>5.2.6 may also fix this bug.
>
>And if you don't find anything, I would recommend you put together a
>small test case showing the problem and report it as a bug.

Jerry - Thanks for the suggestions.

I'll upgrade to 5.2.6 but, maybe you could answer a question for me?
How does one "upgrade"? Do I have to do a complete install of 5.2.6?
Or is it possible to simply update certain components some way?

I looked around the PHP site but couldn't find anything that explained
this. Is there a site somewhere that explains a little more fully how
to do this?

Thanks.

AqD wrote:

Martin wrote:

>
Some kind of internal bug in PHP. The access violation error tells
NOTHING and you don't need to waste time on it.

The problem is probably not specifically with PHP, more likely with
the ISAPI DLL or IIS. The access violation does, indeed, tell you
something.

Try different PHP versions or use apache to host PHP scripts. Apache
is less problemic with PHP in my experience.

The OP shouldn't have to switch server environments, as PHP can run
just fine on IIS, when configured properly.

--
Curtis

Martin wrote:

On Thu, 04 Sep 2008 14:50:08 -0400, Jerry Stuckle
<jstucklex@attglobal.netwrote:
>

>
Jerry - Thanks for the suggestions.
>
I'll upgrade to 5.2.6 but, maybe you could answer a question for me?
How does one "upgrade"? Do I have to do a complete install of 5.2.6?
Or is it possible to simply update certain components some way?
>
I looked around the PHP site but couldn't find anything that explained
this. Is there a site somewhere that explains a little more fully how
to do this?
>
Thanks.
>
>
>

You need to do a complete install. There isn't an upgrade path.

But it's pretty painless. If you previously used the zip/gzip files,
just move your old files to another directory (for backup) and unzip the
new files in the same place. Ensure you keep your current php.ini file.

If you used an installer, you should again backup the files (just in
case), remove the old and install the new in the same place.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

On Sep 5, 8:50*pm, "Dale" <the....@example.comwrote:

"AqD" <aquila.d...@gmail.comwrote in message
>
news:749059af-db00-426b-a549-bc1c5700d1b9@p10g2000prf.googlegroups.com...
>
>
>
>
>

>

>

>

>

>

>
and exactly HOW would you know that?!

Because the access violation is not caught and correctly reported in
PHP module, i.e. the php module crashed.

Therefore it's an internal bug.

>

>
hmmm...it tells you the application is trying to do something that it is not
allowed to do. your comments seem to be the only thing wasting anyone's
time.

Yes it is. Unless you want to spend time debugging IIS & PHP module.

>

>
well, well, well. seems like you don't really think it is 'some kind of
internal bug in PHP' after all! now you're saying it's IIS, or any other
webserver but apache.
>
if you don't have enough information to go on, don't assume so wonderfully
and precisely what the specific problem is or what is going to solve it!

The OP was trying to find out what the problem is. It doesn't help
him.

Even if he finds out why the problem access violation was casued, he
cannot solve it by fixing php or iis. So why waste time on things you
cannot fix?

AqD wrote:

On Sep 5, 8:50 pm, "Dale" <the....@example.comwrote:

>
Because the access violation is not caught and correctly reported in
PHP module, i.e. the php module crashed.
>
Therefore it's an internal bug.
>

>
Yes it is. Unless you want to spend time debugging IIS & PHP module.
>

>
The OP was trying to find out what the problem is. It doesn't help
him.
>
Even if he finds out why the problem access violation was casued, he
cannot solve it by fixing php or iis. So why waste time on things you
cannot fix?
>

Maybe because if no one ever took the time to find problems and report
them to Zend, problems would never get fixed.

So you would rather try to work around all of those problems caused by
an unstable product because, by your philosophy, no one should spend the
time reporting bugs.

And BTW - PHP is open source, if you hadn't known. He very well could
find and fix the problem should be be so inclined and have the time to
do so. So that's another way in which your argument is fallacious.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

On Sep 5, 11:47*pm, Curtis <dye...@gmail.comwrote:

AqDwrote:

>

>

>

>

>

>
The problem is probably not specifically with PHP, more likely with
the ISAPI DLL or IIS. The access violation does, indeed, tell you
something.

You can get access violations when the code uses a null pointer or
reference (most likely to happen), or read unallocated or freed
memory, or write into read-only memory blocks etc etc. It could be
anything.

>

>
The OP shouldn't have to switch server environments, as PHP can run
just fine on IIS, when configured properly.

Is it possible to mis-configure PHP to cause an access violation error?

AqD wrote:

On Sep 5, 11:47 pm, Curtis <dye...@gmail.comwrote:

>
You can get access violations when the code uses a null pointer or
reference (most likely to happen), or read unallocated or freed
memory, or write into read-only memory blocks etc etc. It could be
anything.
>

>
Is it possible to mis-configure PHP to cause an access violation error?
>

If it were possible, that would be a bug.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

"AqD" <aquila.deus@gmail.comwrote in message
news:0968a60f-4254-4591-b0a8-31bd1965a792@q5g2000prf.googlegroups.com...
On Sep 5, 8:50 pm, "Dale" <the....@example.comwrote:

"AqD" <aquila.d...@gmail.comwrote in message
>
news:749059af-db00-426b-a549-bc1c5700d1b9@p10g2000prf.googlegroups.com...
>
>
>
>
>

>

>

>

>

>

>
and exactly HOW would you know that?!

Because the access violation is not caught and correctly reported in
PHP module, i.e. the php module crashed.

Therefore it's an internal bug.

=== uhmmm, no, that would only mean that php didn't catch an exception. the
access violation IS the problem...not the fact that php didn't handle the
exception!

>

>
hmmm...it tells you the application is trying to do something that it is
not
allowed to do. your comments seem to be the only thing wasting anyone's
time.

Yes it is. Unless you want to spend time debugging IIS & PHP module.

=== 'yes it is', what? 'it', being your comments? as far as debugging goes,
if you heed the access violation error message, you can start and probably
end by looking at file permissions on both the dll's and any
directories/files that are in play as seen in the op's code.

>
well, well, well. seems like you don't really think it is 'some kind of
internal bug in PHP' after all! now you're saying it's IIS, or any other
webserver but apache.
>
if you don't have enough information to go on, don't assume so wonderfully
and precisely what the specific problem is or what is going to solve it!

The OP was trying to find out what the problem is. It doesn't help
him.

=== actually, it does. you on the other hand, are very much less than
useful.

Even if he finds out why the problem access violation was casued, he
cannot solve it by fixing php or iis. So why waste time on things you
cannot fix?

=== you assume incorrectly that EITHER are to blame!!! resources external to
BOTH applications who's permissions are not sufficient for EITHER to consume
would simply render your bogus assumptions just that, bogus assumptions

On Sep 8, 10:22*am, "Dale" <the....@example.comwrote:

"AqD" <aquila.d...@gmail.comwrote in message
>
news:0968a60f-4254-4591-b0a8-31bd1965a792@q5g2000prf.googlegroups.com...
On Sep 5, 8:50 pm, "Dale" <the....@example.comwrote:
>
>
>
>
>

>

>

>

>

>

>

>

>

>
Because the access violation is not caught and correctly reported in
PHP module, i.e. the php module crashed.
>
Therefore it's an internal bug.
>
=== uhmmm, no, that would only mean that php didn't catch an exception. the
access violation IS the problem...not the fact that php didn't handle the
exception!
>
>
>

>

>
Yes it is. Unless you want to spend time debugging IIS & PHP module.
>
=== 'yes it is', what? 'it', being your comments? as far as debugging goes,
if you heed the access violation error message, you can start and probably
end by looking at file permissions on both the dll's and any
directories/files that are in play as seen in the op's code.

Sorry but you misunderstood what the error means. It's not directly
related to files. The access violation is on memory not file. If non-
permitted files are accessed by PHP, it would probably be reported.

Memory access violation is usually caused by calling null pointer or
freed resource. And given the fact that the error is usually not re-
producable, you cannot track it unless you have a memory dump, or your
php is running with dubug symbols and is attached by a runtime
debugger (not php debugger).

On Sep 8, 10:17*am, Jerry Stuckle <jstuck...@attglobal.netwrote:

AqD wrote:

>

>

>

>

>