kewnood Posted October 9, 2002 Posted October 9, 2002 Every time I load the osCommerce site winxp says: "Apache.exe has encountered a problem and needs to close. We are sorry for the inconvenience." and wants me to send an error report. The thing is Apache didn't actually close and the page loads just fine after that error msg. The problem is specific to osCommerce, as phpmyadmin and others don't have this problem. I suspect it has something to do with these two lines in the conf file: define('DIR_FS_DOCUMENT_ROOT', 'c:/program files/apache group/apache/htdocs'); define('DIR_FS_CATALOG', 'c:/program files/apache group/apache/htdocs/catalog/'); When i had apache 2 the error would totally crash my machine, with apache 1.3 it doesn't really affect anything, but it's just very annoying. Does anyone know a solution to this problem?
Jan0815 Posted October 9, 2002 Posted October 9, 2002 Does anyone know a solution to this problem? Update your PHP. This is a known problem that occurs in some combinations of PHP and Apache. If you use a newer PHP version the problem will be solved. HTH You can't have everything. That's why trains have difficulty crossing oceans, and hippos did not adapt to fly. -- from the OpenBSD mailinglist.
kewnood Posted October 9, 2002 Author Posted October 9, 2002 If you use a newer PHP version the problem will be solved.HTH Version 4.2.3 not new enough? Do I have to use the nightly builds?
Jan0815 Posted October 9, 2002 Posted October 9, 2002 Version 4.2.3 not new enough? Do I have to use the nightly builds? Hehe. In that case I would like to rephrase. Use an older version ;-) Anyway - I am running osC on my laptop with WinXP, Apache 1.3.24, PHP 4.2.1 and I have no problems. I remember these crashes you mention and it was solved by updating both Apache and PHP. What Apache version are you using? You only mentioned you tried with apache 2.0 and 1.3 HTH You can't have everything. That's why trains have difficulty crossing oceans, and hippos did not adapt to fly. -- from the OpenBSD mailinglist.
kewnood Posted October 9, 2002 Author Posted October 9, 2002 Currently running apache 1.3.27 I've tryed it with every version of php from 4.2.3 to 4.2.1 - no luck so far. I'll try altenating apache versions tomorrow, i've had enough for tonight:)
kewnood Posted October 10, 2002 Author Posted October 10, 2002 Sadly the apache 1.3.24 & php 4.2.1 combination doesn't work for me:( Any alternative solutions to pursue?
kewnood Posted October 10, 2002 Author Posted October 10, 2002 BTW the apache error log says: [Thu Oct 10 19:14:45 2002] [error] Cannot remove module mod_rewrite.c: not found in module list
idbeu Posted November 11, 2002 Posted November 11, 2002 I have the same problem. Was this ever resolved? Thanks!
jdfitch Posted November 11, 2002 Posted November 11, 2002 My question is WHY would anyone want to run a server in Windows XP. Why not just rent billboards out on the highway and publish your information thier and save the cost of maintaining a server. I use Windows 2000 for my servers and Apache and php never give me a minutes trouble and never have. Just my thoughts, your may differ. But! Until Microsoft bothers to close the secruity holes in XP (right now they are big enough to drive a truck through) I will not use XP on any platform for any reason. If you choose not to decide you still have made a choice, I will choose a purpose clear, I will choose Free Will. --Neal Peart - Rush
jdfitch Posted November 11, 2002 Posted November 11, 2002 Go into your apache Conf. file and comment out the offending mod_ If you can live with out it. That should solve the problem temoprarily. If you choose not to decide you still have made a choice, I will choose a purpose clear, I will choose Free Will. --Neal Peart - Rush
idbeu Posted November 15, 2002 Posted November 15, 2002 I was using Windows 2000. I say was, because I formatted and installed Linux. But Linux is having PHP issues with Apache2 also. If the problem is a mod, it is probably a PHP mod, which is required.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.