Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

No buffer for GUI communication... CALL_FUNCTION_NO_GUI_BUFFER

Former Member

‎2015 Apr 01 1:35 PM

0 Likes
692

Good afternoon

Yesterday we started getting ST22 dumps CALL_FUNCTION_NO_GUI_BUFFER - about 5 dumps per second..

I've searched on SCN and found similar posts but none of the answered. If you have an idea what caused this and how to fix or avoid, please assist.

Thank you and best regards,

Adrian Bruwer

2 REPLIES 2
Read only

Private_Member_7726
Active Contributor

‎2015 Apr 01 2:54 PM

0 Likes
520

Hi,

I don't believe this is ABAP Development thema at all..., and did you search OSS as well..?  Are there perhaps also some ZDATE_ILLEGAL_LOCTIME dumps before CALL_FUNCTION_NO_GUI_BUFFER dumps started, as described in 1885573 - Several dumps CALL_FUNCTION_NO_GUI_BUFFER? If yes, Basis should look at 447839 - ZDATE_ILLEGAL_LOCTIME.

cheers

Janis

Read only

DavidLY
Product and Topic Expert
Product and Topic Expert

‎2015 Apr 02 9:14 AM

0 Likes
520

Hello,

The CALL_FUNCTION_NO_GUI_BUFFER dump can also be a consequence of dump POSTING_ILLEGAL_STATEMENT.

A cause for the last one is described in SAP note 1628406.

You can analyze the ABAP stack from dump POSTING_ILLEGAL_STATEMENT
and saw the affected program which is being executed.
It is possible that an error code is causing this dump. It occurs most
likely because statement "COMMIT" is used incorrectly.


Please double-check the code with your development team.

Regards,

David