SNAP_NO_NEW_ENTRY 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: A - ABAP Programming Error
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.
Depending on cause of error, according to system log.
You probably have to create more space for table SNAP by database means.
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.
Runtime error, short dump could not be written.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The error cause cannot be determined, since the table SNAP does not
contain a suitable short dump.
Table SNAP probably already contains so many short dumps that it cannot take on any more. Examine the situation using the system log.
SNAP contains all short dumps from the last 7 days.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Unfortunately, the system cannot carry out a detailed analysis of the error, as the table SNAP (which gathers information at the time of termination) does not contain a suitable short dump.
SNAP_NO_NEW_ENTRY - snap no new entry SLIN_FUNCTION_BLOCK_WRONG - slin function block wrong SHM_LOCK_OPERATION_FAILED - shm lock operation failed SET_RUN_TIME_CLOCK_ERROR - set run time clock error SET_PARAMETER_VALUE_TOO_LONG - set parameter value too long SET_PARAMETER_UNKNOWN_CODE - set parameter unknown code