Jump to content

PHP on 64 bit windows, with iis 6, php access violation problem


Recommended Posts

 

We have an application that works fine on a normal win32 based PHP-Apache-Mysql system.

 

Recently we moved to a new server which is win64 bit,

and web server we use here is iis 6.

 

Though there were almost no changes in code as expected, we had a PHP Access voilation xxxxxx(typical windows memory id)  problem occuring on almost every page request.

 

Checking forums, we found the problem was a known bug in php and was corrected in php 4.x

 

We are using php 5.2.x and mysql 5.1.x, both installed as appropriate on a win64 bit win2003 machine.

 

We couldnt understand why the error was still appearing.

 

In one of our many tests, We tested by inserting a 1 sec delay for every 100 mysql query requests the php script made (the script is a large database updater and processes several 100,000 records before it ends). Inserting this delay kind of stabilized the system, and we stopped havng the php access violation problems.

 

Questions, we are trying to find answers for:

 

1. Is php tested and stable on win 64 bit.. are there critical, known bugs.

2. Is the php access violation, an unfixed known bug on php for 64 bit machines.

 

Any help/information is appreciated.

 

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.