Opening Reporting Server communication port 80 failed

[VictorCalvo]

Hi,

I am experiencing problems with the Reporting Manager. The context is a v15 Redundant project. The reporting Manager has been working properly since the first day in both servers, but some days ago it has been detected that it wasn't possible to launch reports (BIRT is the report sw used). I realized the Reporting Manager was stopped in the active server (status 0, blinking blue and yellow), but in the passive server there was no problem. If the project switches the active server, reports can be launched succesfully. So, the problem is with one particular server. The log file returns the following when an attempt of start this manager is executed:

WCCOAreporting(1), 2022.05.31 03:39:11.654, SYS, FATAL, 54, Unexpected state, Opening Reporting Server communication port 80 failed
WCCOAreporting1:SOAP 1.1 fault SOAP-ENV:Server [no subcode]
WCCOAreporting1:"Intento de acceso a un socket no permitido por sus permisos de acceso.
WCCOAreporting1:"
WCCOAreporting1:Detail: bind failed in soap_bind()
WCCOAreporting(1), 2022.05.31 03:39:13.668, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAreporting(1), 2022.05.31 03:39:13.679, SYS, INFO, 181, Closing connection to (SYS: 1 Event -num 0 CONN: 1)

I checked the port, but its status is "listening", so, as far as I know, it shouldn't be the problem. No installation or Windows update has been performed at the server. No configuration changes, neither. Recently, the server has been shutted down by cutting off the power. Several times a backup recovering from the online backup has been performed due to data base corruption issues. I don't know if these events would have affect the reporting manager in a way it is experiencing this.
I would like to know which additional comprobations I could perform and how I can solve this.

Thank you,

[dbindernagel]

If the reporting manager is currently not running but the port status is 'listening', wouldn't that mean the port is currently used by another program? Than the reporting manager cannot use this port.

You should be able to check with netstat -no which other program is using the port.