If Apache fails to start after a reboot

May 15th, 2007   11 Comments

If you’re using XAMPP and Apache fails to start (e.g. after a reboot), check what the problem is by looking in the Windows Event Viewer.

Go to Start > Settings > Control Panel.

In the Control Panel double-click Administrative Tools.

In the Administrative Tools window double-click Component Services.

In the left pane of the Component Services window, expand Event Viewer (local).

Select Application.

The right pane lists system messages. Look for any with the source Apache Service.

Double-click the most recent Apache Service message.

In the Event Properties dialog box, review the error and click the down arrow to browse through all messages that happened at the same time.

When I did this I had the following three messages happening every time I tried to start Apache from the XAMPP Control Panel:

Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID: 3299
Date: 02/04/2007
Time: 11:27:30
User: N/A
Computer: JOKER
Description:
The Apache service named reported the following error:
>>> Unable to open logs .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID: 3299
Date: 02/04/2007
Time: 11:27:30
User: N/A
Computer: JOKER
Description:
The Apache service named reported the following error:
>>> no listening sockets available, shutting down .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID: 3299
Date: 02/04/2007
Time: 11:27:30
User: N/A
Computer: JOKER
Description:
The Apache service named reported the following error:
>>> (OS 10048)Only one usage of each socket address
(protocol/network address/port) is normally permitted. :
make_sock: could not bind to address 0.0.0.0:443 .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

If this happens it indicates that something else is hogging port 443, the standard SSL port. You need to find out what’s using port 443 (and, most likely, also port 80) and stop these programs.

In my case the problem was IIS. The IIS Admin service was set to auto-start and was grabbing port 443. I wanted to use Apache, so I could happily turn off IIS. If you want to run both, you’ll have to run one of them on non-standard ports – e.g. 8080 instead of 80 and 4443 instead of 443 (you then have to specify the port to browse to a page via that web server – e.g. http://mydomain.xyz:8080/whatever.html.

To turn off the IIS Admin service:

Go to Start > Settings > Control Panel.

In the Control Panel double-click Administrative Tools.

In the Administrative Tools window double-click Services.

In the right pane of the Services window, look for IIS Admin. If its status is reported as “Started”, select this service and choose Action > Stop.

Now try starting Apache from the XAMPP Control Panel.

If this works, disable IIS Admin by going back to the Services window, right-clicking the service, choosing Properties and in the Properties dialog box changing Startup type from “Automatic” to “Disabled”, then Apply the change.

Potentially similar posts

Comments are closed

  1. User Gravatar Alistair said:

    June 26th, 2007 at 1:22 pm (#)

    The problem is usually that something else is using port 80. In the above example it was IIS, but it might also have been Skype, or something else.

    The best way to find out is to do:

    Start > Programs > Apache Friends > XAMPP > Port check

    This opens a command shell window and lists the ports used by XAMPP components. If port 80 is currently being used by something other than apache.exe then that’s your problem.

    If the program using port 80 is inetinfo.exe then stop the World Wide Web Publishing Service in Windows’ Services dialog box.

  2. User Gravatar Bjarne K said:

    October 20th, 2007 at 2:24 pm (#)

    Thanks!

    I had the same problem, and discovered that the service IIS admin was startet (for unknown reasons).

    This site saved me a lot of time, thanks!

  3. User Gravatar Maruf said:

    October 19th, 2008 at 5:13 am (#)

    Thanks!

    Skype was my culprit…
    The tutorial helped a lot.. Thank you very much

  4. User Gravatar Girish said:

    August 8th, 2009 at 1:17 pm (#)

    I havn’t started IIS Admin still in event viewer it throws 3299 event id, what to do plz suggest

  5. User Gravatar Alistair said:

    August 14th, 2009 at 7:12 pm (#)

    It’s a long time since I looked at this, but I think you need to try and track down what’s using port 443. Try turning any likely services off until you find the culprit.

  6. User Gravatar Guido Diemer said:

    September 7th, 2009 at 4:18 am (#)

    In my case it was an IP Check monitor driven by FIREBIRD.ORG

  7. User Gravatar Mark van Alphen said:

    September 24th, 2009 at 11:23 pm (#)

    Thanks, this helped me.
    It was exact the same problem.

  8. User Gravatar Matovolwa said:

    January 28th, 2010 at 10:03 am (#)

    On my side, the event description was 'The Apache service named reported the following error: >>>Unable to open logs'.
    I stpped the ISS Admin service so i was able to successfully start the McAfee ePolicy Orcherstrator Server.

  9. User Gravatar itauthor said:

    January 28th, 2010 at 10:13 am (#)

    Thanks for posting that info Matovolwa

  10. User Gravatar P4ul said:

    November 14th, 2010 at 6:32 am (#)

    thanks, i never would have guessed skype was causing it

  11. User Gravatar itauthor said:

    November 18th, 2010 at 12:52 pm (#)

    Glad that helped. Thanks for commenting.