This problem is not very well handled, confused a lot of stationmaster very time up
Occurs primarily on the server of a Windows host.
In PHP official,http://bugs.php.net/
can also find two thousand or three thousand pages of the report, their official is also helpless, after 11 iterations, still not completely resolved
Http://bugs.php.net/search.php?cmd=display&search_for=PHP+has+encountered+an+Access&x=8&y=9
At present I offer some of my maintenance experience over the years, some of my folk solutions
The first is the possibility of:
Get rid of eaccelerator extensions in PHP
This will solve your problem, but it may increase the system burden
Because Eaccelerator is mainly to save the system resources of Things
The way to find php.ini
If I'm configuring it for you, it's usually in C:/php/php.ini or C:/winnt/php.ini or C:/windows/php.ini.
Remove
Zend_extension_ts= "C:\php\extensions\eaccelerator_win_xxx.dll"
Eaccelerator.shm_size= "16"
Eaccelerator.cache_dir= "C:\Temp"
eaccelerator.enable= "1"
Eaccelerator.optimizer= "1"
Eaccelerator.check_mtime= "1"
eaccelerator.debug= "0"
Eaccelerator.filter= ""
eaccelerator.shm_max= "0"
Eaccelerator.shm_ttl= "0"
eaccelerator.shm_prune_period= "0"
eaccelerator.shm_only= "0"
eaccelerator.compress= "1"
Eaccelerator.compress_level= "9"
EA was developed primarily in a UNIX environment, but the author ignores that Windows is not actually a memory-sharing mechanism without a U-host, like the U-host.
This bug has been submitted to them, hoping 0.9.5 can solve
Of course, if your machine this problem is not serious, recommended or retained, EA is a very good PHP cache + acceleration Software
With ZO use, will reduce the system burden of 50%-80%, improve load capacity, speed and efficiency of about 200%
The second possibility
Session_save_path need to set an actual physical path, and the directory requires everyone's permissions, similar to the U-Host 0777
The third possibility
C:/winnt/temp or C:/windows/temp.
All permissions are also required for everyone, similar to the U-Host 0777
The fourth kind of possibility
Your memory is seriously insufficient, check, if there is a problem, please add memory, preferably one plus two
For example, add 1G of memory, preferably add 2 identical 512M. Otherwise the dual channel is not enabled, the effect is very general
The fifth kind of possibility
Zendoptimizer and PHP are not very well matched.
Try a different version.
At present, the more stable collocation is
Php4.3.11+zo 2.5.10a
or Php4.4.1+zo 3.0 Beta2.
The sixth kind of possibility
This is a lot of users who use Win2003
They set limits in the application pool.
such as how long time to recycle, the maximum use of memory and so on
These settings are bound to cause this classic PHP error
After hundreds of tests on the wood, the guarantee problem will appear here.