Top 18 SAP Common ABAP Dumps in ST22 & Troubleshooting

ST22 SAP Common ABAP Dumps in ST22 TroubleShooting

The standard SAP Transaction code ST22 compiles the ABAP Dumps occurred in the SAP System.

In this article, I will detail the Top 18 most common ABAP dumps in ST22. It may help through troubleshooting as the first step.

Second, you can search for, if exists a SAP Note which can correct the issue or ask SAP for help.

Common ABAP Dumps in ST22


The problems with the dump STORAGE_PARAMETERS_WRONG_SET are mainly related to the general restrictions of the 32bit OS. You can address up to 4 GB of virtual memory. Each process in OS is running in its own context and can address max. 4 GB. The parameters which are related to heap memory ie- abap/heap_area_dia, abap/heap_area_nondia, abap/heap_area_total are should be set to 2 GB. Common approaches which we can take for this dump are:

  • Please use in the ‘boot.ini’ file the switch 3GB and restart your whole computer as described in the below SAP Notes:
    • SAP Note 552209 : Maximum memory utilization for processes on NT/Win 2000
    • SAP Note 313347 : Windows NT, 2000, 2003: Editions and memory usage.
  • Another way to avoid this problem is to try to add more criteria to your report/program/transaction so that there will be fewer entries that need to be retrieved from your database or buffers. This way, the system would not need to use up much resource to complete the transaction. The query may have been quite big already and the load cannot be accommodated. So please do add more criteria or options so that there will less data to fetch.
  • To decrease the value of the parameters: rdisp/ROLL_SHM, rdisp/PG_SHM
  • Migrate to 64-bit OS (as per SAP Note 931024 and SAP Note 996600)


The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested by the system because the program needed to expand an internal table, but not is available.

When Extended Memory is completely used up, the process will go into PRIV mode and it will start using Heap Memory in case of Windows or vice versa in case of UNIX. Once this enters into PRIV mode, no other user will be able to use the corresponding work process. If there is enough memory for it to finish, you will not see the error.

Please refer the following SAP notes:

  • SAP Note 649327 : Analysis of memory consumption.
  • SAP Note 20527 – Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
  • Note 185185 : Application: Analysis of memory bottlenecks


The dump TSV_TNEW_BLOCKS_NO_ROLL_MEMORY usually means that the roll buffer has been exhausted. Please check the usage of your roll buffer with ST02⇾History⇾Page. Near the bottom of the screen you can see ROLL BUFFER history.

If the roll buffer has been exhausted, you can increase the size with parameter rdisp/ROLL_MAXFS, but make sure you have sufficient disk space to handle the additional size of this buffer if it writes to disk.
Please refer the following SAP note:

  • SAP Note 185185 – Application: Analysis of memory bottlenecks


The LOAD_PROGRAM_LOST error can occur when there are two or more versions of a given program loaded into the buffer at any given time.

This happens when the program is changed by one user while it is still in use by another user.
When a user gets to the program that is having this problem and R/3 attempts to load the generated version from the buffer, it sees that the version is not the most current and tries to swap it out for the most current, but the load was lost from the PXA buffer, hence it throws the dump of LOAD_PROGRAM_LOST.

LOAD_PROGRAM_LOST are the result of the combination of not enough PXA space + changes of programs which are in use currently. A running program can’t run with two different versions of one program. Ask the users restart their transactions (/nST22).

By the way, if the PXA would be big enough then the user who does not leave their transaction for weeks will not see the changes to this application until they restart the transaction.

Troubleshooting for ABAP Dumps LOAD_PROGRAM_LOST

Other way to correct the error is you need to run transaction SAMT & regenerate the program(s) that are listed in the dump.

You can then do a $SYNC in the command field in the affected application server, but make sure that the other application servers are not running at that time. After the $SYNC, the other app servers can be brought up and the buffers should then be in sync.

Please refer the following SAP notes:

  • SAP Note 24824 : Inconsistencies in a Program Load
  • SNote 10367 : Termination LOAD_PROGRAM_LOST


The short dump CALL_FUNCTION_SIGNON_INCOMPL is typical of an RFC-Call with incorrect or missing logon-data. So, we have to find out where the call is coming from.

Please refer the following SAP notes:

  • SAP Note 171805 – Determining RFC client when sign-on problems occur.
  • SAP Note 684788 – Possible reason for CALL_FUNCTION_SIGNON_INCOMPL.


This error mostly appears with the user SAPSYS. The user SAPSYS is an internal user, it is not a personally used ID in the R/3 system. However, all system errors and ABAP programs are run via this user id. As per note 93254, since release 4.0 the parameter auth/rfc_authority_check is set on 1 per default.

This means, as long as you did not set it explicitly to value 0, any incoming RFC call is checked as described in the mentioned note.
The common approaches which we can take on this dump are:

  1. Deactivate RFC authority Check: set auth/rfc_authority_check to value 0 (zero) in your profile and restart the server. (This is the least secure option as any authorization checks are disabled for all RFC requests).
  2. Assign full RFC authorities to the users who need to connect to your system via RFC.

Please also check the user id provided in RFC connection (check from SM59) which cause the dump RFC_NO_AUTHORITY. Make sure that this user has sufficient authorizations.
Please refer the following SAP notes:

  • SAP Note 171805 : Determining RFC client when sign-on problems
  • SAP Note 93254 – RFC short dump RFC_NO_AUTHORITY
  • SNote 91980 : Missing output of RFC short dump after login errors


For this error, please go to service market to download the latest patch for your SAP Application release and apply the patch. The latest patch would be useful for the problem. The SYSTEM_NO_TASK_STORAGE is a known problem and related to limitation of 32bit OS.

Please see notes 110172, 552209, 546361 for details. As long term solution you have to use 64bit Windows (Note 996600). The cause for the dump SYSTEM_NO_TASK_STORAGE could also be an old sap collector. SAP recommends using the updated collector version always.

The common approaches which we can take on this dump are:

  1. Check your settings match the recommendations mentioned in SAP Note 146289.
  2. Are limits set according to SAP Note 323816 (Referenced in SAP Note 146289)
  3. If there is no additional instances on the same host then it should be possible to increase EM/TOTAL_SIZE_MB from 4096 MB towards the RAM and even higher so that ztta/roll_extension can be reached. Also, the swap space should be set according to SAP Note 153641 for this.


Please refer the following SAP notes:

  • SAP note 789477 : Large extended memory on AIX (64-bit) as of Kernel
  • SAP note 191801 – AIX 64-bit with a lot of Extended Memory
  • SNote 445533 – Lots of extended memory on AIX (64-bit)
  • SAP note 581319 – Signal 33 on AIX (64-bit only)
  • SAP note 153641 : Swap space requirement for R/3 64-bit kernel


The error CALL_FUNCTION_NOT_FOUND is due to the fact that the program called the function which doesn’t exist in the library.

Means the requested function module is not found in table TFDIR. Also, you may get this error if the buffered version of the TFDIR contains errors.

The error needs to attention based on the function module. You may take a general approach mentioned in the SAP Note 98458.

Please refer the following SAP note:



This error usually comes when you don’t have sufficient authorization to login to the trusted system. This dump accompanies by 4 different error codes:

Error Code Signification of Error
0 Incorrect logon data for valid security ID.
1 calling system is not a Trusted System or security ID is invalid.
2 Either user does not have RFC authorization (authorization object S_RFCACL)
2 or a logon was performed using one of the protected users DDIC or SAP*
3 timestamp of the logon data is invalid.

Please refer the following SAP notes:

  • SAP Note 986707 : No authorization to log on as a trusted system (RC=1)
  • SAP Note 128447 : Trusted/Trusting Systems
  • SAP Note 204039 : Authorization check in trusted system


Generally, SYSTEM_CORE_DUMPED is related to R/3 system kernel. Upgrade the kernel patch to the latest may solve the issue. But without a detail analysis of the core dump at the Kernel, we cannot conclude the reason behind the dump. I would recommend contacting SAP for this dump.

  • SAP Note 19466 : Downloading SAP kernel patches


In most situations where the ST22 DUMP PXA_NO_SHARED_MEMORY occurs there is not enough contiguous address space to create the buffer of size xMB Approx (where x is size in megabytes).

The SAP note 129813 may be relevant as some DLLs may be positioned that are stopping the creation of this large buffer on Windows platforms.

Also SAP Note 307976 gives information about this dump type PXA_NO_SHARED_MEMORY.


Is a GUI related error. Go for latest GUI version to avoid this error.

You will get a File Version similar to:
7100.2.9.10397100 means SAPGUI 7.10.2 means Compilation 2.9 means Patch level.1039 is a build number

Message_Type_X Dump also occurs when proper date format is not maintained in SU01 transaction of the user who have faced this dump.

In case you have received a complaint from the customer that he is receiving this dump while running some transactions, please go to SU01 and check the date format in the defaults tab. If there is any date format other than DD.MM.YYYY, please change that to this format to avoid this error


Memory bottleneck encountered by the program while sorting.


Not enough memory for user context.


Not enough SAP Paging Memory. Set ‘rdisp/pg_maxfs’ to sufficiently large value (say 32,000).

If the problem exists even after assigning this value then there could be a fault in the program itself.


Not enough memory for SET/GET Parameter (Otherwise known as SPA/GPA Memory).

Try extending the memory area with SAP profile ‘ztta/parameter_area’.


Number range problem, likely document number exists.


EXSORT_FWRITE_FAILED is related to disk space. There is not enough disk space for the external sorting process in the sort directory.

To avoid this move either the extract files (DIR_EXTRACT) or the sort files (DIR_SORTTMP) to a separate directory with enough space.

Original Post: Common ABAP Dumps (ST22) and troubleshooting in SAP