SAP Knowledge Base Article - Preview

2535340 - ABAP processes of instance [ABAP: UNKNOWN] did not start after 10:10 minutes.


  • While installing a Primary or Additional Application Server (PAS, AAS) with Software Provisioning Manager (SWPM) or while Software Update Manage (SUM) creates the shadow system, below error occurs:
    • SWPM

      <html> <head> </head> <body> <p> An error occurred while processing option <i>SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > Software Life-Cycle Options > Additional SAP System Instances >
      Oracle > Dialog Instance( Last error reported by the step: ABAP processes of instance  [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.)</i>. You can now: </p> <ul> <li> Choose <i>Retry</i><br>to
      repeat the current step. </li> <li> Choose <i>Log Files</i><br>to get more information about the error. </li> <li> Stop the option and continue later. </li> </ul> <p> Log files are written to
      /tmp/sapinst_instdir/NW701/LM/AS/ORA/DI. </p> </body> </html
    • In sapinst_dev.log below entries appear:
      INFO 2017-09-14 13:27:31.334 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/modlib/iaxxbjsmod.cpp:83] id=modlib.jslib.childAppReturn
      Execution of the command "/usr/sap/SID/DXX/exe/sapcontrol -prot NI_HTTP -nr xx -function GetProcessList" finished with return code 0. Output:
      <DATE> <TIME>


      name, description, dispstatus, textstatus, starttime, elapsedtime, pid

      disp+work, Dispatcher, GRAY, Stopped, , , 20118
      igswd_mt, IGS Watchdog, GREEN, Running, 2017 09 14 13:17:20, 0:10:11, 20119
      ERROR 2017-09-14 13:27:31.565 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/sapinst/CSiStepExecute.cpp:1117] id=controller.stepExecuted errno=FCO-00011
      The step start with step key |NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|di|0|start was executed with status ERROR ( Last error reported by the step: ABAP processes of instance <SID>/D03 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up.).
    • SUM

      Severe error(s) occurred in phase MAIN_SHDRUN/START_SHDI_FIRST!
      Last error code set:
      Shadow instance
      couldn't be started, check 'START_SHDI_FIRST.LOG' and 'DEVTRACE.LOG': Process /usr/sap/SUM/abap/exe/sapcontrol exited with 2, see '/usr/sap/SUM/abap/log/SAPup.ECO' for details
      To analyze errors during the start of the shadow instance, check the 'START_SHDI_FIRST.LOG' and 'DEVTRACE.LOG' files in directory '/usr/sap/SUM/abap/log'.
  • Above error points that the dispatcher is in GRAY status. In dev_disp or DEVTRACE.LOG, following entries appear:
    • *** ERROR => e=28 semget(3039988,1,2016) (28: No space left on device) [evtux.c 640]
      *** ERROR => DpWpEvtInit: EvtCreate (rc=1) [dpxxwp.c 521]
      *** DP_FATAL_ERROR => DpSapEnvInit: DpWpEvtInit



Linux, Solaris operating systems


kernel.sem  , e=28 semget ,  EvtCreate , DP_FATAL_ERROR , DpSapEnvInit , disp+work, Dispatcher, GRAY, DISPATCHER EMERGENCY SHUTDOWN , installing additional instance , startInstallation , ABAP: UNKNOWN did not start after 10:10 minutes. Giving up , controller.stepExecuted errno=FCO-00011 MAIN_SHDRUN/START_SHDI_FIRST START_SHDI_FIRST.LOG DEVTRACE.LOG , KBA , BC-INS-UNX , Installation Unix , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-CST-DP , Dispatcher, Task Handler , BC-OP-LNX , Linux , BC-INS-SWPM , Installation with Software Provisioning Manager , BC-OP-LNX-OLNX , Oracle Linux , BC-OP-LNX-RH , Red Hat Linux , BC-OP-LNX-SUSE , SUSE Linux , BC-OP-SUN , SUN Solaris , 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.