How to troubleshoot MESSAGE_TYPE_X dump in ST22 of SAP system?

This article answers the following queries :

ü  How to troubleshoot  MESSAGE_TYPE_X dump in ST22 of SAP system?

ü  What could be the reason for MESSAGE_TYPE_X dump in SAP and how to avoid it?

-------------------------------------------------------------------

Sometimes, Basis administrators will receive complaints from some customers that whenever they are running any transaction in SAP, they are receiving MESSAGE_TYPE_X dump.

If you could login to ST22 transaction of SAP system and go through the dump, you might have seen similar to below screen

Please check if this issue exists for all the users. If you and most of the others are not facing this issue and only some set of customers are facing this issue, then most likely this issue could be due to lower SAP GUI version and patch level of those customers.

So, please cross check the SAP GUI version/patch details of the customers. If you feel, GUI version/patch levels are lower than the version of the systems in which it is running fine, and then most probably issue could be due to SAP GUI version and patch level.

Please install latest version or minimum recommended version of SAP GUI in the customer’s desktop which resolves this issue automatically.


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

Incase you have received a complaint from customer that he is receiving this dump while running some transactions, please goto 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.

Please note that there could be other reasons also for these types of dumps. But if the customer is not able to run any transaction, then most likely that is due to lower SAP GUI version and patch levels or the different date format maintained.

How to avoid TIME_OUT dumps in SAP system ?

This article answers the following queries :

• How to avoid TIME_OUT dumps in SAP system ?
• There are lot of TIME_OUT dumps in ST22 transaction. How to avoid these dumps ?

-----------------------------------------------------------------------------------------

These TIME_OUT dumps usually occur if the program has exceeded the maximum permitted runtime without interruption. After this program will get terminated and in ST22 a dump will get generated.

Usually SAP system will terminate the program after permitted runtime to make the work area available to other users who may waiting and to prevent a work area being blocked unnecessarily long time like

Eg: Database accesses without a suitable index (Full table scan)

      Database access with a large result set

     Endless loops (DO, WHILE) etc

In SAP, there is a parameter rdisp/max_wprun_time which limits the maximum permitted runtime without interruption. By default this value is set to 600 seconds. However, if you are frequently encountering more dumps in SAP system due  to this, you can consider increasing this value to 3600 seconds to avoid this issue.

How to change sap parameter ?