Solution : https://service.sap.com/sap/support/notes/1845121 (SAP Service marketplace login required)
Summary :
SAP components such as message server, dispatcher, and gateway fail to start due to port conflicts, as indicated by error messages related to binding and listening (e.g., 'NiIBindSocket: bind (10013: WSAEACCES: Permission denied)' for Windows or 'NiIBindSocket: bind (98: Address already in use)' for Linux). The issue arises when the port, particularly port 3600, is already in use by another process. The recommended resolution involves identifying and terminating the process occupying the port using system-specific commands like 'netstat' or 'lsof'.
Key words :
components bc-op-aix ibm aixbc-op-hpx hp-uxbc-op-lnx linuxbc-op-nt windowsbc-op-sun sun solaris priority normal category problem product, customer component bc-net network infrastructure, __%pdfstyle%__ / } symptom sap message server, __%pdfstyle%__ / } #monospace td { font-family, __%pdfstyle%__ / } #monospace, product version references, grep <port number>linux/unix, / __%pdfstyle%__font-size, nidgbind header data released, css sap notes 164937 nipbind
Related Notes :
| 164937 | NiPBind: service 'sap????' in use |