Symptom
System is unable to start with the below error in dispatcher and work process trace under WORK directory “/usr/sap/<SID>/Instance<Nr>/work"
dev_disp
***LOG Q41=> DpDumpInternalTables, () [dpxxdisp.c 3455]
*** ERROR => DpHdlDeadWp: W4 (pid <xxxx>) died (severity=0, status=65280) [dpxxwp.c 1440]
DpTraceWpStatus: child (pid=<xxxx>) exited with exit code 255
(...)
** DP_FATAL_ERROR => DpWpCheck: no more work processes
*** DISPATCHER EMERGENCY SHUTDOWN ***
dev_w4
M *** ERROR => ThSetGwParam : NiHostToAddr <$(SAPLOCALHOST).$(SAPFQDN)> failed M in_ThErrHandle: 1 M *** ERROR => ThInit: ThProfileRead (step TH_INIT, thRc ERROR-CORE-INIT_FAILED, action STOP_WP, level 1) |
Same error can be seen in all other work process traces.
Or
Gateway fails to start and you can see following lines in gateway trace:
dev_rd
ERROR => GwInitHostAdrs: GwHostToAddr(<$(SAPLOCALHOST).$(SAPFQDN)>) failed, rc=-2 [gwxxaddr.c 431] |
Read more...
Environment
SAP NetWeaver
Product
Keywords
ThSetGwParam, NiHostToAddr, ERROR-CORE-INIT_FAILED, SAPFQDN, SAPLOCALHOSTFULL, SAPLOCALHOST, Hostname resolution, niping , KBA , BC-CST-STS , Startup Service , BC-CST-DP , Dispatcher, Task Handler , BC-CST-NI , Network Interface , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.