START_ABAP_NOT_INITIALIZED is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: F - Installation Errors
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
Status index after roll area initialization: <runtime parameter>.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
The ABAP/4 processor has not been initialized.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
During initialization of the program <runtime parameter>, an
internal error occurred.
START_ABAP_NOT_INITIALIZED - start abap not initialized STACK_STATE_NO_ROLL_MEMORY - stack state no roll memory STACK_STATE_ILLEGAL_MODE - stack state illegal mode STACK_RPERF_POPSTATE_ERROR - stack rperf popstate error STACK_NO_ROLL_MEMORY - stack no roll memory STACK_JSTCK_ILLEGAL_CODE - stack jstck illegal code