Symptom
The SAP ABAP Application Server does not start. Firstly it is required to analyze the dispatcher trace file (dev_disp) inside of the problematic instance's work folder (LocalDrive\usr\sap\<SID>\SCS<XX>\work).
The dispatcher trace file 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] ***************************************************************************** * COUNTER 1 *** ERROR => DpIPCInit2: DpSysAdmExtCreate [dpxxtool2.c 411] |
In this case, <lib version> and <kernel version> are not the same.
Read more...
Environment
- Operating System independent
- Database independent
- SAP NetWeaver
- SAP Web Application Server for SAP S/4HANA
- ABAP Platform
Product
Keywords
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 for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.