SAP Knowledge Base Article - Preview

2414599 - Dialog instance does not start due to a died gateway


The SAP ABAP Application Server does not start.

Firstly is required to analyse the dispatcher trace file (dev_disp) inside of instance work folder. Dispatcher reports the following error:

*** ERROR => [DpProcDied] Process died (PID:36444 HANDLE:1744 rc:0x0) [dpnttool2.c 147]
*** ERROR => gateway (pid 36444) died [dpxxdisp.c 17664]
*** DP_FATAL_ERROR => Gateway died with status 2 - I better exit now


The error means that the gateway service (gwrd) died during the start up. The gateway trace file (dev_rd) reports the following error:

***LOG Q0Z=> DpSysAdmExtCreate, bad version (lib=<lib version> krn=<kernel version>) [dpxxtool2.c 723]
* LOCATION SAP-Gateway on host USNENCPW125.NMCorp.Nissan.Biz / sapgw00
* ERROR dp lib version mismatch, please check installation
* TIME Wed Jan 11 08:06:34 2017
* VERSION <lib version>
* RC -9999
* MODULE dpxxtool2.c
* LINE 730
* DETAIL version of external and kernel dp lib mismatch (ext lib
* version is <lib version> / kernel lib version is <kernel version> )
*** ERROR => DpIPCInit2: DpSysAdmExtCreate [dpxxtool2.c 411]
***LOG S0V=> GwStopGateway, gateway stopped () [gwxxrd.c 13396]


 In this case, <lib version> and <kernel version> mismatch.





  • All relesed of SAP Netweaver kerne


Start, Restart, startsap, instance, failed, sapstartsrv, Unknown, webmethod, MMC, SAPMMC,  SAPMC, Web service , KBA , BC-CST-STS , Startup Service , BC-CST-GW , Gateway/CPIC , 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.