What could cause an 101 Error in WAMP under Windows 7? [closed]
Solution 1:
I had the same problem.
- OS: Windows 7
- Server: Apache 2.2.17-win32
- MySQL: 5.1.53-win32
- PHP: 5.2.14-Win32
Replacing C:/<MySQL Dir>/bin/libMySQL.dll with C:/PHP/libmysql.dll solved my problem.
The error occurs when you try to connect to database with mysql_connect. It is shown on the following line in error log above.
[Wed Oct 14 13:52:32 2009] [notice] Parent: child process exited with status 255 -- Restarting.
So Apache crashes when mysql_connect tries to connect. So use proper libmysql.dll is helpful here.
Solution 2:
I ran across something very much like this --- but my configuration included Drupal in addition to PHP. So for you Drupal people out there, I would suggest checking for a function recursively calling itself.
In my case, I was trying to move a Drupal installation from one machine to another. The old system had Log4Drupal enabled and configured to write to a log file on a drive and folder that did not exist on the new machine. Near as I could tell, the log function tried to report something and when that failed, it tried to log the failure, etc.
To work around the problem, it was useful to look in the database and find out what file Log4Drupal was using. The MySQL query is "select * from variable where name like 'log%'". I created all the folders needed to make that path good. Then my Drupal system was able to start and I could use Log4Drupal's admin page.
Solution 3:
I had the same problem.
You should close the connection at the end of your page code using the connection resource. This worked for me:
mysql_close($conn);
where $conn is your MySQL database connection resource variable which you have used to connect to MySQL database.