Re: Access Violation in ISAPI version

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, there...

I had seen that error message in my PC (with windows 2000 Server + php4.2.3
+ Oracle9i)

if you are using PHP on IIS(, I recommend that you should check
"session.save_path = c:/temp" in your php.ini.
(this file normally located in c:\winnt directory)

some developers discussed this problem being related with
"session.save_path" property...

Please, check these article in...

http://www.php.net/manual/sk/printwn/function.session-save-path.php

If it can't fix your problem... sorry for bothering you...
Good luck.

"Ryan Jameson" <RJameson@usa.ibs.org> wrote in message
CC8578B824E74940BA5126774F49628D136680@nathan.ibs.org">news:CC8578B824E74940BA5126774F49628D136680@nathan.ibs.org...
Has anyone else had problems with the error "PHP has encountered an Access
Violation at 098029AE" ...

It's talked about at:
http://bugs.php.net/bug.php?id=15333


The most frustrating thing is our ISP went above the call of duty to install
PHP for me, and now his response is... well read for yourselves:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I read through all the stuff at php.net.  The long and short of it is this:
Nobody really knows what is causing the problem.
It appears to be a problem with a dual-processor machine (which is what
you're using)
It is believed that 4.2.3 solves the problem (that is the latest version and
the version we are using)
Setting the security model to "low" on the site helps in many cases (doesn't
eliminate the problem, just reduces how often it occurs)

Ergo, this has been my problem with "public domain" scripting languages such
as PHP.  There is not a single source that can be held accountable for
ensuring a problem is solved.  It is the reason that we have standardized on
CF, because when it's bad, Macromedia HAS to fix it.

All that being said, and consistent with our terms of installation, I will
take some time to see if I can "trim up" the configuration and improve the
situation.  However, because this problem crashes the server completely, if
we can't find a resolution soon, I will opt to remove it from the system.

One of our key responsibilities is system stability and reliability.  Again,
I'll see if I can modify the config to alleviate this, however, the php
resource was very little help.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I'm pretty disappointed that this hasn't been fixed yet. Has anyone had any
luck fixing it?

Thanks!
<>< Ryan



-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux