Apache Friends Support Forum

I have worked for several years with Xampp 1.5.1 (PHP 5.1) without any problem (Windows XP). Recently I installed Wordpress 2.8.6. The site was OK, but when using Dashboard Apache crashes as soon as I open the Plugins, News or Development Blog section. On Ubuntu with Lamp (PHP 5.2): no problems.

The error message was (Dutch, sorry!):
In Apache HTTP Server is een fout opgetreden en moet worden afgesloten. Onze excuses voor dit ongemak.
Details van de foutmelding:
szAppName : apache.exe szAppVer : 2.2.0.0 szModName : php5ts.dll
szModVer : 5.1.1.1 offset : 000a6582

On a test XP computer I installed Xampp 1.7.2 and the problem disappeared, only Apache runs much slower than with 1.5.1. So I would like to keep the older version of Xampp, but I need to run WordPress on it. Any suggestions? Thanks.

Translated - Cassandra wrote:In Apache HTTP Server has encountered a problem and needs to close. We apologize for this inconvenience.
Details of the error:
szAppName: apache.exe szAppVer: 2.2.0.0 szModName: php5ts.dll szModVer: 5.1.1.1 Offset: 000a6582

This issue has been around for some time in older XAMPP versions and it appears to have been eliminated in the newer versions but there was never a definitive answer that I could find when it was a frequent post on the forums.

Consider that Wordpress 2.8.6 Dashboard, plug-ins etc. may not be backward compatible with your older version of PHP and is maybe why it's working in XAMPP 1.7.2 version that has PHP 5.3.0.



Here are some of the solutions that had positive results for some but not all.

1. Check in your xampp\apache\conf\httpd.conf file, down near the end of the file for these 2 entries that should look like this - if not change them:
EnableMMAP off
EnableSendfile off

Also add this if it is not there right at the end of the file:
Win32DisableAcceptEx

Save the file and restart Apache, then test for the issue again - always make a backup of *.conf and *.ini files before editing.


2. Make sure you only have those extension you require uncommented in your xampp\apache\bin\php.ini file - all extensions uncommented can cause strange issues.


3. Some had success by copying the php5ts.dll file from the \xampp\apache\bin folder into your C:\Windows\system32 folder then, after booting your PC, test for the issue again.


4. Another claimed to have had success by enabling this extension in the \xampp\apache\bin\php.ini file

Code: Select all

;extension=php_threads.dll

remove the comment character ; from the beginning of the line, then save the file and restart Apache and test for the issue again - but as always make a backup copy of any *.ini or *.conf file before editing and use a text editor when editing.


5. This fix seems to have worked for many:
http://bugs.php.net/bug.php?id=44645
Rename the file \xampp\mysql\bin\libmysql.dll to libmysql.dll_ which in effect causes the file in the \xampp\apache\bin folder to be used - restart Apache and MySQL and test again for the issue.

You can try any of the above fixes one at a time then test after each and see which, if any, fixes your issue.
If you find one, then I would appreciate a post back with which one did the trick for you.



To save you some time, there appears to be no help, that I could find, from over at the Wordpress.org forums on this subject, except the reference to backward incompatibility with older PHP versions.

A search here in the XAMPP For Windows forum using php5ts as the keyword will give you results that will verify what I have posted above in condensed form.


And finally, if you can't solve the riddle of the php5ts.dll issue, you may have to upgrade your Wordpress, as recommended by their web site, to the latest version 2.9.1 to keep up to date with any security fixes they have incorporated.

The same would apply with XAMPP as now the version is 1.7.3 with PHP 5.3.1 and the developers always seem to keep abreast of any major component changes and security updates.

Good luck.

Thank you very much, Izzy, I appreciate it that you understand that I would like to find the bug first, before upgrading. With your valuable instructions I will delve into the settings, never had much to change because Xampp always worked fine. Please give me some time, I will certainly report back to this forum.

Upgrading WordPress to 2.9.1. *almost* solved the problem. I have had one Apache crash since but cannot reproduce it. If I get more crashes I'll try the other solutions.