The socket bind failed for host * and port 80

The socket bind failed for host * and port 80
Problem :
TCPPort       E   TCPC0003E: TCP Channel TCP_2 initialization failed.  The socket bind failed for host * and port 80.  The port may already be in use.

Resolution : You can stop the HTTP service temporarily from the command line:

From command prompt "run" : net stop HTTP
After running this command it will show dependent services and ask -- Do you want to continue this operation? (Y/N) [N]: Y
At last it will say : The HTTP service was stopped successfully.
Now In console you will not get this problem.

Another Approch :

When attempting to access the home page for one of the WebSphere Commerce starter stores (for example, ConsumerDirect), an error message displays. An example of the error message follows:

A WebGroup/Virtual Host to handle /webapp/wcs/stores/servlet/ConsumerDirect/index.jsp has not been defined.

The virtual host definitions in the WebSphere Application Server might not be functioning properly.

A simple test to verify this situation is to attempt to access the starter store's home page using port 8000 instead of port 80. For example if ConsumerDirect was published, try to access the store using https://localhost:8000/webapp/wcs/stores/servlet/ConsumerDirect/index.jsp. If port 8000 was successful then the virtual host definitions will need to be updated.

To change the virtual host definitions:

1. Start the WebSphere Commerce Test Server using either the Rational Application Developer interface or using the startWCServer.bat script.
2. Access the WebSphere Application Server's administrative console
3. Select Environment > Virtual Hosts
4. Select the default_host entry
5. From the "additional properties" section select "Host Aliases"
6. Delete the references to port 80 and 443
7. Save your change to the master configuration.
8. Restart the server.

You should now be able to access the starter stores using port 80.

Refrence : Unable to browse store pages when using port 80