SAP Knowledge Base Article - Preview

3026212 - ICM HTTPS service does not start due to wrong hostname configuration

Symptom

ICM cannot start its HTTPS service.
Also, ICM state can be found as not fully started.  
In the output of operating system command "niping -v" there is a mismatch between short hostname and FQHN of local computer as following:

niping -v

Hostname/Nodeaddr verification:
===============================

Hostname of local computer: hostnameA (NiMyHostName)
FQHN of local computer: hostanameB.example.com (NiGetOwnFQDN)

Lookup of hostname: hostnameA (NiHostToAddr)
--> IP-Addr.: 10.10.10.10
Lookup of IP-Addr.: 10.10.10.10 (NiAddrToHost)
--> Hostname: hostanameB.example.com

Lookup of hostname: localhost (NiHostToAddr)
--> IP-Addr.: 127.0.0.1
Lookup of IP-Addr.: 127.0.0.1 (NiAddrToHost)
--> Hostname: localhost

Also, in "niping -v" output, the IP resolved for hostnameA does not resolve back to hostnameA (IP resolves to hostanameB instead).

In addition, it can happen that in dev_icm trace file (in trace level 1) no information about the SSL library to be loaded after "Added service PORT=443,PROT=HTTPS" trace entry be written.
As a consequence, "Activated service PORT=443,PROT=HTTPS" entry cannot be found in dev_icm trace. 



Read more...

Environment

SAP NetWeaver release independent

Product

SAP NetWeaver all versions

Keywords

KBA , BC-CST-IC , Internet Communication Manager , BC-CST , Client/Server Technology , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.