EHealth web won’t start.

Products

• CA eHealth

Issue/Introduction

When we try to start the eHealth web service (httpd) we get errors:

D:\eHealth\web\httpd\bin>nhihttpd.exe

(OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address [::]:80

(OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address 0.0.0.0:80

AH00451: no listening sockets available, shutting down

AH00015: Unable to open logs    

…

 

When we check netstat we see port 80 is listening so it should be available.

Environment

eHealth 6.3.x

Cause

The error tells you that port 80 is not available:

AH00072: make_sock: could not bind to address 0.0.0.0:80

Added note, when you check netstat to see if a port is free, it should not show in the list at all.

If it shows as listening, it is in use.
here is an example form a machine where port 80 is free:

C:\>netstat -a |grep :80

  TCP    0.0.0.0:8063           HOSTM4800:0         LISTENING

 

We see that port 80 is not listed, so is not in use.

…

Here is an example where port 80 IS in use:

C:\>netstat -a |grep :80

  TCP    0.0.0.0:80             F178171:0      LISTENING

 

…

Another tool you can use on windows is sysinternals tcpview, from Microsoft.com.

 

This is an excellent graphical port viewer.

Resolution

Find out what is using the port and shut it off.

Verify that the port is now free by running netstat

netstat -a | grep :80

 

 

Start the eHealth web service in windows services GUI or from the command line