lawandorder Posted February 28, 2007 Share Posted February 28, 2007 New issue Windons XP localhost install. Installed XAMPP and switched to php version 4. Created database using local web host control panel. Donwloaded oscommerce "catalog" folder into webroot and changed permissions. Ran the install per quick install instructions. But at step 7 when I press "catalog" or "administration" I get an apache error "Apache HTTP Server has encountered a problem and needs to close".... PS. Global variables set to ON Help greatly appreciated. Link to comment Share on other sites More sharing options...
amayernx Posted February 28, 2007 Share Posted February 28, 2007 New issueWindons XP localhost install. Installed XAMPP and switched to php version 4. Created database using local web host control panel. Donwloaded oscommerce "catalog" folder into webroot and changed permissions. Ran the install per quick install instructions. But at step 7 when I press "catalog" or "administration" I get an apache error "Apache HTTP Server has encountered a problem and needs to close".... PS. Global variables set to ON Help greatly appreciated. Having noticed your other posts on the issue, I dug up the original post, and I'll bite. If it's XP, does the Windows event log have anything of any value when this happens? If so, what does it say? "encountered a problem and needs to close" means that somewhere, someone rearranged the atoms of the universe. Moreover, if you fire up XAMPP, then just go to the regular catalog page (not through the installer), what happens? Link to comment Share on other sites More sharing options...
lawandorder Posted February 28, 2007 Author Share Posted February 28, 2007 Thanks for the help. Don't really know what I am doing but I was able to follow the instructions. A little more info on the problem. After the apache shutting down error page the page goes blank.....but apache appears to still be running per the xampp control panel ? Have tried pointing the browser directly at the catalog page without going through xampp - still getting the same Apache error ??? Sorry to appear stupid but where can I find the windows event log ? Thanks again Link to comment Share on other sites More sharing options...
amayernx Posted February 28, 2007 Share Posted February 28, 2007 The event log can be found in the control panel -> administrative tools -> event log. The errors should be recorded in the "Application" or "System" logs, with a source of "Apache" or "XAMPP". Link to comment Share on other sites More sharing options...
lawandorder Posted February 28, 2007 Author Share Posted February 28, 2007 I just tried it again and viewed the logs immediately after. Got one error in the application log - Faulting application apache.exe, version 2.2.3.0, faulting module php4ts.dll, version 4.4.5.5, fault address 0x00085ee9. Hmmmmm.... Link to comment Share on other sites More sharing options...
amayernx Posted February 28, 2007 Share Posted February 28, 2007 Looks like the PHP 4 configuration/installation may be damaged. I'd double check the configuration first and perhaps reinstall. Link to comment Share on other sites More sharing options...
lawandorder Posted February 28, 2007 Author Share Posted February 28, 2007 Thanks again. Do u know how to check the PHP 4 configuration ? Also, I'm on my third installation of Xampp now. Link to comment Share on other sites More sharing options...
John1 Posted March 28, 2007 Share Posted March 28, 2007 I'm having this same problem, does anybody know how to fix this yet???? :'( Link to comment Share on other sites More sharing options...
lawandorder Posted March 30, 2007 Author Share Posted March 30, 2007 I found the problem. In one of the earlier posts it said to switch the php version in XXAMP from 5 to 4...which I did. This is wrong. You should be using version 5 of php. I simply switched it back to version 5 using the phpswitch.bat file in the localhost screen and reinstalled oscommerce. Worked first time ! Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.