Stopping apache kills windows! why?

[48inch]

OK a server in the office just died so to give me a test platform I just installed Apache on my desktop machine. So far so good and all seems to work. Then I install PHP, mysql etc and make some config changes. At this point I stop Apache so that it will restart and pick up the new changes to the config, except that rather than stopping apache it killed the entire windows machine and rebooted windows. That definitely achieved what I wanted but it's bit more extreme than I need. Any idea why this should behave this way and how I can stop it doing it?

Setup is Apache 2.2.22 on Windows Xp SP3, I've also installed PHP 5.2.17 and MySQL 5.5.20. Though I don't beleieve they are at fault as it was stopping Apache to pick up those items which showed the problem. It shows this behavior whether I use the Apache monitor to stop Apache 4or use NET STOP apache2.2. It also showed the same behaviour if I stopped the service from services.msc, although that was less consistent.

So does any kind soul out there have any ideas as to why it would do this and how do I stop it?

 

[Noway2]

Welcome to tek-tips.

This sounds like an odd behavior. My initial reaction is that it sounds like some sort of "protection fault" or invalid instruction operation that caused Windows to crash. With regards to Apache and PHP there are about four different versions based upon the compiler library (VC6 or VC9 I believe) and support for threading and which one you need is highly dependant upon which version of Win you are running. Are you sure that you downloaded the right version AND got compatible versions of PHP and SQL?

 

[48inch]

As I understand it there is only one version of Apache that is appropriate (Apache 2.2.22 32bit) but four versions of PHP. The PHP version installed is VC6 thread safe which seemed to be the recommended version although there does seem some ambiguity in that (which you can read as I may have misunderstood which version I needed).

More conclusively it works because when the thing has started up I can run PHP pages so although I suppose it could be some kind of protection issue it's not affecting the core functionality. Also the behaviour showed itself when I had editted httpd.conf to pick up the PHP dlls and was stopping Apache to pick up those changes, i.e. at that point PHP was not linked to Apache so stopping Apache should not have been dependant on the PHP installation. Hence I think it's something to do with Apache itself and not PHP.

 

[Noway2]

Have you tried looking into the event log to see if there is any sort of warning or error message?