Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Runtime Errors : CALL_FUNCTION_NO_GUI_BUFFER

Hi All,

i have attached the Short dump details.

Please have a look and provide the necessary information to resolve this issue.

Runtime Errors CALL_FUNCTION_NO_GUI_BUFFER

Date and Time 23.05.2011 16:30:09

Short text

No buffer for GUI communication.

What happened?

Error in the SAP kernel.

The current ABAP "SAPLSGUI" program had to be terminated because the

ABAP processor detected an internal system error.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Error analysis

GUI output buffer............. 0000000000000000

Length of buffer.............. 29992

Internal mode................. 2

How to correct the error

" "

System environment

SAP-Release 701

Application server... " "

Network address...... "10.64.1.195"

Operating system..... "Windows NT"

Release.............. "6.0"

Hardware type........ "2x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 11

Shortdump setting.... "full"

Database server... " "

Database type..... "MSSQL"

Database name..... "R3P"

Database user ID.. "r3p"

Terminal.......... "PISTOL"

Char.set.... "C"

SAP kernel....... 701

created (date)... "Oct 31 2010 23:41:04"

create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 117

Patch text.. " "

Database............. "MSSQL 9.00.2047 or higher"

SAP database version. 701

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0, Windows NT 6.1"

Memory consumption

Roll.... 16192

EM...... 16759360

Heap.... 0

Page.... 40960

MM Used. 1262224

MM Free. 2924992

User and Transaction

Client.............. 400

User................ " "

Language key........ "E"

Transaction......... "LAST_SHORTDUMP "

Transactions ID..... "F41F85E0643DF18A86750050568C617C"

Program............. "SAPLSGUI"

Screen.............. "SAPMS380 0100"

Screen line......... 3

Information on where terminated

Termination occurred in the ABAP program "SAPLSGUI" - in

"SAPGUI_PROGRESS_INDICATOR".

The main program was "SAPMS380 ".

In the source code you have the termination point in line 83

of the (Include) program "LSGUIU01".

Source Code Extract

Line SourceCde

53 call function 'TH_USER_INFO'

54 IMPORTING

55 task_state = task_state.

56 task_state_raw = task_state.

57

58 if not ( task_state_raw o task_term_output_sent ).

59 exit.

60 endif.

61 endif.

62 elseif async_type <> '0'.

63 call function 'TH_USER_INFO'

64 IMPORTING

65 task_state = task_state.

66 task_state_raw = task_state.

67 if not ( task_state_raw o task_term_output_sent ).

68 exit.

69 endif.

70 endif.

71

72 out_text = text.

73 perc = percentage.

74 modno = syst-modno.

75 if perc < 0. perc = 0. endif.

76 if perc > 100. perc = 100. endif.

77

78 call 'RFCControl' id 'CODE' field 'n'. "set NonBlockingGUIRFC

79

80 * if there is no gui attached to this session RFCControl will return

81 * with an error (sy-subrc = 8 or sy-subrc = 16)

82 if sy-subrc = 0.

>>>> call function 'SAPGUI_PROGRESS_INDICATOR'

84 destination 'SAPGUI'

85 keeping logical unit of work

86 EXPORTING

87 text = out_text

88 percentage = perc

89 modn = modno

90 EXCEPTIONS

91 system_failure

92 communication_failure.

93 endif.

94

95 syst-subrc = 0.

96 endfunction.

Former Member
Not what you were looking for? View more on this topic or Ask a question