Yes, that's what I'd assume too. The problem *looks* like a memory leak
yet only affects one particular site which is why it's so strange. I did
some Googling but came up with little. The only other suspects I found
were related to information being passed to a COM object, and possibly
if you're running it as an ISAPI module. Also if the page is trying to
access an area of the filesystem that it does not have permissions to do
so, but this is not likely the issue since you mentioned you don't lose
any functionality. It's also not likely that the js is causing it
either. Unfortunately, it also appears as though this error is probably
one of the most unhelpful errors that IIS can ever display when using PHP.
Perhaps try looking for a common denominator? You said that the error is
generated in different spots. Maybe review your code in each of the
places it appears and see if there are any common elements that might
give you a better clue as to what's causing it. Cheers.
Armando
Dbird.. wrote:
Armando,
I appreciate the response. Hopefully we can track it down better. The
websites which are functioning properly are actually much more complex than
this one. lol.
The only real difference is that I have some javascript running a countdown
clock which is displayed using images which are replaced through the js...
But it's code that has run cleanly for a long time in other applications and
I cannot see how this would cause the problems I am seeing now.
But if it were a memory leak wouldn't it translate across the other websites
as well?
"Armando" <dijital@xxxxxxx> wrote in message
news:43F15850.6080300@xxxxxxxxxx
If it goes away on a server reboot for a period of time, then it sounds
suspiciously like a memory leak, ie; the application is trying to
reference an area of memory it doesn't have access to. I've seen this
problem with other applications... they'd run fine for a period of time
after a reboot then start throwing out errors in the event log. Reboot,
fine for another period of time. Maybe check your event log for any
errors? Can you perhaps expand on the differences between this site and
your others? Are there other modules it's using that your other sites
are not? Cheers.
Armando
Dbird.. wrote:
To make this even more interesting is that when I reboot the server, the
error goes away for a period of time, usually about 30 minutes.
Any ideas?
""Dbird.."" <groover4life@xxxxxxxxxxx> wrote in message
news:14.F0.30933.B3E01F34@xxxxxxxxxxxxxxx
I'm running php version 4.3.7 on Windows 2003 Server and IIS 6.0
I have several websites which are all using php extensively but I have
one
website where I am consistantly getting the following error:
"PHP has encountered an Access Violation at 01930AFD"
The error occurrs on every page, but where on the page it shows up
varies.
I have NO loss of functionality on the website so this really has me
baffled.
Where is the error coming from? How can I find out more information as
to
the source of the error? How can I simply remove that error message
from
being displayed into my web pages and wreaking havoc on their format?
I've been on this one for a couple of days and I'm really stumped on
this
one.
Thanks in advance.
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
