Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Former Member

Some customers have reported "IRepSetBuffer" errors in the traces in SM50.

A way to check if these errors are false or really connected to Webgui activities is to:

Check if ITS trace levels set to 2 in SITSPMON. If one or more ITS

parameters (trace level related) in SITSPMON are set to 2, then then set them to 1.

This way you can check in SM50 if the errors disappear. If yes then there is no need for further action.

If the errors still appear a kernel upgrade is recommended.

In most cases the error is originated from the service names being longer than 14 characters.

This can be verified in SE80.

This is a known bug and has been corrected in later kernel patches.

So the general recommendation is to use the newest possible kernel.

The problem with this situation is that there is no dump in ST22 so there is no obvious way to determine where the error is coming from.

The trace entries in SM50 look like this :

*** ERROR => xgdk: IRepSetBuffer: customer/$$$$-> $***