Symptom
Following error appears in Dispatcher trace file (dev_disp) while starting the SAP system:
*** ERROR => Es2IResCreatePosix: shm_open /SAP_ES2_<instance nr>_<nr> failed. File already exists. If no SAP processes are running any more, you can clean up stale resources with cleanipc. (17: File exists) [es2ux.c 261]
*** ERROR => Es2ResCreateFiles: Es2IResCreate failed [es2xx.c 1324]
*** ERROR => Es2ResCreate: Es2ResCreateFiles failed [es2xx.c 1507]
*** ERROR => DpEmInit: Es2ResCreate (1) [dpInit.c 1624]
*** ERROR => DpMemInit: DpEmInit (-1) [dpInit.c 1399]
*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
Due to this error, the system cannot start. You can also find on Dispatcher trace:
ERROR => Es2IResCreate: shmget failed (size= <size>). (17: File exists)
Read more...
Environment
- AIX, Solaris, Linux operating system
- SAP NetWeaver 2004
- SAP NetWeaver 7.0
- SAP NetWeaver 7.3
- SAP NetWeaver 7.4
- SAP enhancement package 1 for SAP NetWeaver 7.0
- SAP enhancement package 1 for SAP NetWeaver 7.3
- SAP enhancement package 2 for SAP NetWeaver 7.0
- SAP enhancement package 3 for SAP NetWeaver 7.0
- and associated products (e.g. SAP ERP, SAP ECC)
Product
Keywords
Es2IResCreatePosix, shm_open, File already exists, 17: File exists,
Es2ResCreateFiles, Es2IResCreate, Es2ResCreate, Es2ResCreateFiles , KBA , BC-CST-MM , Memory Management , BC-VMC , Virtual Machine Container , 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.