WampServer

I've just downloaded and installed WAMP today, but have not been able to get it to start.

My system information:

8Gb of RAM, plenty of disk space (300 Gb free space)

Windows version 8.1 64 bit
WampServer (64 bit) Version 2.5
Apache Version is 2.4.9
PHP Version is 5.12 -64b
MySQL Version is 5.6.17
WampServer icon is ORANGE

hosts file - Only 127.0.0.1 localhost is uncommented

On trying to start the server I get a popup window with the error message:

Aestan Tray Menu

Could not execute menu item (internal error)
[Exception] Could not perform service action:
The service has not been started

Apache, PHP and MySQL error logs are all empty.

Event Viewer logs:

The Apache service named reported the following error:
>>> AH00015: Unable to open logs .

The Apache service named reported the following error:
>>> AH00451: no listening sockets available, shutting down .

The Apache service named reported the following error:
>>> (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:80 .

wampmysqld64: ready for connections.
Version: '5.6.17' socket: '' port: 3306 MySQL Community Server (GPL)

Event Scheduler: Loaded 0 events

Server socket created on IP: '::'.

- '::' resolves to '::';

IPv6 is available.

Server hostname (bind-address): '*'; port: 3306

Server hostname (bind-address): '*'; port: 3306

InnoDB: Waiting for purge to start

InnoDB: 128 rollback segment(s) are active.

InnoDB: Highest supported file format is Barracuda.

InnoDB: Completed initialization of buffer pool

InnoDB: Initializing buffer pool, size = 128.0M

InnoDB: Not using CPU crc32 instructions

InnoDB: Compressed tables use zlib 1.2.3

InnoDB: Mutexes and rw_locks use Windows interlocked functions

InnoDB: The InnoDB memory heap is disabled

InnoDB: Using atomics to ref count buffer pool pages

Plugin 'FEDERATED' is disabled.

I initially had WAMP installed on C:\ with 34 Gb of free space, and after failing to resolve the problem I uninstalled and reinstalled on an external drive with 460 Gb of free space.

I have tried disconnecting from the internet so I could safely exit my anti-virus (ESET NOD32), MalwareBytes Anti-Malware and UnHackMe/RegRun/Warrior, but exiting these made no difference.

I have followed all of the advice I can find, but I'm stumped! I'd be very grateful for any help anybody could offer.

Thanks,
Russell

It looks to me like the Apache service has not started!

Which explains

Aestan Tray Menu

Could not execute menu item (internal error)
[Exception] Could not perform service action:
The service has not been started




This makes me think that you have something that hs already allocated port 80

The Apache service named reported the following error:
>>> (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:80 .


Do you have amother Apache running?
Do you have IIS running?

Run the port 80 test from the wampmanager menu :-

wampmanager -> Apache -> Test port 80


What does that tell you?

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Thank you! So simple when you know what to do!!

The result was:

Information not available. (Might be Skype).


I quit Skype and then restarted all service - and Viola! It works perfectly. Thanks so much for your fast and helpful response!

Now I'll restart Skype while the Apache server is running, and hopefully force Skype to find another port. Or I'll search Google (or is it Alphabet now?) for how to run both together.

Best regards,
Russell

Just an update:

It's working perfectly, thank you! I went to Skype, and under Tools > Options > Advanced > Connections there is a checkbox near the top which says, "Use port 80 and 443 for additional incoming connections"

I've unchecked that, so hopefully won't have any more problems. But if I do, I know where to start looking.

There is something else that, as far as "I" have found, is "NOT" anywhere in the Net.
I've been struggling for 2 days to figure out why I couldn't get WAMP to go "green". I went through every possible bit of information - changing ports; running command prompt to see what's using the port; running debug through command prompt; etc.
Debug kept telling me that Apache was using already listening to port 80.
Obviously not the version I was attempting to use.

I had run older versions and the most current version previously, although a lot of problems trying to get multiple versions working.
I uninstalled everything - so I thought.
I had a folder with a backup, but it was all renamed and should not have been live.

I had uninstalled everything and installed 2.5 with Apache 2.4.9, MySQL 5.6.17 and PHP 5.5.12, then rebooted.

That still didn't work.
Finally, I decided to look at Task Manager (Windows 10) to see what I could find.
wampmysql64 and wampapache64 were running, and I didn't see any other Apache...until I scrolled down the unorganized list of programs running (Task Manager > Services).

Apache2.2 was running.
I have no idea why it wasn't uninstalled, but as soon as I highlighted, hit "End Task", Apache2.2 "stopped" and my installed WAMP 2.5 turned green immediately!

Skype has been redeveloped so that it uses port 40255 and the box to also listen to 80 is unchecked by default. Skype isn't the issue anymore.

So, after going through everything, if you keep seeing the debug tell you Apache is already using port 80, head directly to Task Manager and see if there is more than 1 version of Apache running.

Now I can move forward with "trying" to install older versions in order to access an old site with critical information.
I hope this helps others.