DYNPRO_SEND_IN_BACKGROUND

[Former Member]

Hi All,

I am getting the ABAP dumps in the Production DYNPRO_SEND_IN_BACKGROUND but i dont have any cancelled Background jobs.

I am posting my dump here, Please suggest me the solution for this

Category ABAP Programming Error
Runtime Errors DYNPRO_SEND_IN_BACKGROUND
Except. CX_SY_SEND_DYNPRO_NO_RECEIVER
ABAP Program SAPLSRABAX_EXC
Application Component BC-ABA-LA
Date and Time 10.03.2014 16:52:18

Short text

Screen output without connection to user.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSRABAX_EXC" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_SEND_DYNPRO_NO_RECEIVER', was

not caught and

therefore caused a runtime error.

The reason for the exception is:

During background processing, the system attempted to send a screen to

a user.

Current screen: "SAPMSSY0 " 0120.

Additional system information: "no window system type given"

How to correct the error

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DYNPRO_SEND_IN_BACKGROUND" "CX_SY_SEND_DYNPRO_NO_RECEIVER"

"SAPLSRABAX_EXC" or "LSRABAX_EXCU01"

"DISPLAY_EXC_SCREEN"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP Release..... 702

SAP Basis Level. 0006

Application server... ""

Network address...... ""

Operating system..... "Windows NT"

Release.............. "6.1"

Hardware type........ "48x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... ""

Database type..... "MSSQL"

Database name..... "AZP"

Database user ID.. "azp"

Terminal.......... "215_PRT"

Char.set.... "C"

SAP kernel....... 720

created (date)... "Sep 19 2011 23:29:58"

create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"

Database version. "SQL_Server_9.00 "

Patch level. 105

Patch text.. " "

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

SAP database version. 720

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.... 0

EM...... 8379584

Heap.... 0

Page.... 319488

MM Used. 2337072

MM Free. 1850048

User and Transaction

Client.............. 000

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

Language key........ "F"

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

Transaction ID...... "0966A8E3E0B7F1AD9306782BCB449F94"

EPP Whole Context ID.... " "

EPP Connection ID....... " "

EPP Caller Counter...... 0

Program............. "SAPLSRABAX_EXC"

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

Screen Line......... 6

Debugger Active..... "none"

Information on where terminated

Termination occurred in the ABAP program "SAPLSRABAX_EXC" - in

"DISPLAY_EXC_SCREEN".

The main program was "SAPMS380 ".

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

of the (Include) program "LSRABAX_EXCU01".

Source Code Extract
Line	SourceCde
1	FUNCTION DISPLAY_EXC_SCREEN.
2	*"----------------------------------------------------------------------
3	*"*"Lokale Schnittstelle:
4	*" IMPORTING
5	*" REFERENCE(P_LIVE_DUMP) TYPE FLAG DEFAULT SPACE
6	*" REFERENCE(P_SNAP) TYPE SNAP OPTIONAL
7	*" EXPORTING
8	*" REFERENCE(P_PROCEED) TYPE FLAG
9	*" CHANGING
10	*" REFERENCE(P_FT) TYPE RSDUMP_FT_IT
11	*"----------------------------------------------------------------------
12
13	if p_snap is supplied.
14	snap = p_snap.
15	endif.
16	*** screen 100 carrys the list.
17	*** check language
18	if second_language is initial.
19	call 'C_SAPGPARAM' id 'NAME' field 'zcsa/second_language'
20	id 'VALUE' field SECOND_LANGUAGE.
21
22	endif.
23
24	if p_live_dump is supplied.
25	live_dump = p_live_dump.
26	endif.
27	if not p_ft is initial.
28	ft_it = p_ft.
29	endif.
30	call screen 100.
>>>>>	if p_ft is initial.
32	p_ft = ft_it.
33	endif.
34	p_proceed = proceed_flag.
35
36
37	ENDFUNCTION.

Internal notes

The termination was triggered in function "dytrcexit"

of the SAP kernel, in line 2786 of the module

"//bas/720_REL/src/krn/dynp/dymain.c#24".

The internal operation just processed is "CMPS".

Internal mode was started at 20140310165217.

Active Calls in SAP Kernel

Lines of C Stack in Kernel (Structure Differs on Each Platform)

SAP (R) - R/3(TM) Callstack, Version 1.0

Copyright (C) SAP AG. All rights reserved.

Callstack without Exception:

App : disp+work.EXE (pid=6340)

When : 3/10/2014 16:52:17.424

Threads : 2

Computer Name : AZTSAP_PRD

User Name : SAPServiceAZP

Number of Processors: 48

Processor Type: Intel64 Family 6 Model 47 Stepping 2

Windows Version : 6.1 Current Build: 7601

State Dump for Thread Id 18c0

0000000002028350 000000014188F496 0000000002B3D5E0 disp+work!DumpStacks [ntstcdbg.c (548)]

0000000002028450 0000000140272AA4 00000000744FA000 disp+work!NTDebugProcess [ntstcdbg.c (383)]

0000000002028480 00000001404B390A 00000000744FA000 disp+work!CTrcStack [dptstack.c (183)]

00000000020284D0 00000001404B950D 0000000000000000 disp+work!rabax_CStackSave [abrabax.c (8649)]

0000000002028DE0 0000000140298FE3 0000000000000000 disp+work!ab_rabax [abrabax.c (1419)]

0000000002028FF0 00000001402E88CB 0000000000000001 disp+work!dytrcexit [dymain.c (2849)]

00000000020290C0 000000014029D627 0000000000000002 disp+work!dynprctl [dymainstp.c (470)]

000000000202F320 00000001401123CB 0000000000000000 disp+work!dynpen00 [dymain.c (2015)]

000000000202FDF0 0000000140112BDC FFFFFFFFFFFFFF00 disp+work!TskhLoop [thxxhead.c (4879)]

000000000202FE50 000000014002E3B6 0000000002B3D548 disp+work!ThStart [thxxhead.c (1195)]

000000000202FEF0 00000001400010B1 FFFFFFFF00000001 disp+work!DpMain [dpxxdisp.c (1168)]

000000000202FF20 0000000141BA98A0 0000000002030000 disp+work!nlsui_main [thxxanf.c (80)]

000000000202FF50 0000000076EC652D 0000000000000000 disp+work!__tmainCRTStartup [crtexe.c (594)]

000000000202FF80 00000000775BC541 0000000000000000 kernel32!BaseThreadInitThunk

000000000202FFD0 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart

State Dump for Thread Id 1480

000000000E71FDE0 000007FEFDAD3C2F 0000000078833D03 ntdll!NtFsControlFile

000000000E71FE50 0000000141A7E96F FFFFFFFFFFFFFFFE KERNELBASE!ConnectNamedPipe

000000000E71FEF0 00000000744437D7 0000000003C5F250 disp+work!SigIMsgFunc [signt.c (717)]

000000000E71FF20 0000000074443894 00000000744F95C0 MSVCR80!endthreadex

000000000E71FF50 0000000076EC652D 0000000000000000 MSVCR80!endthreadex

000000000E71FF80 00000000775BC541 0000000000000000 kernel32!BaseThreadInitThunk

000000000E71FFD0 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart

List of ABAP programs affected
Index	Typ	Program	Group	Date	Time	Size	Lang.
0	Prg	SAPMS380	0	13.01.2010	10:16:48	222208	F
1	Typ	SYST	0	09.09.2004	14:18:12	30720
2	Typ	SNAP	0	17.06.2009	13:37:20	7168
3	Prg	SAPMSSYD	0	12.09.2006	11:33:31	23552	F

Directory of Application Tables

Name Date Time Lngth

Val.

Program SAPMS380

SYST 09.09.2004 14:18:12 00004612

\0\0\0\0\x0002\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x001E\0

SY . . : : 00004612

\0\0\0\0\x0002\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x001E\0

SNAP . . : : 00003336

20140310165217AZTSAP_PRD_AZP_00

SNAP_BEG . . : : 00000536

20140310165217AZTSAP_PRD_AZP_00

SNAPT . . : : 00000216

FDYNPRO_SEND_IN_BACKGROUND U0006Additional system info

TFDIR . . : : 00000268

Program SAPSHDTV

SHDSTU . . : : 00000106

|

SHDSTCIU . . : : 00000100

|

ABAP Control Blocks (CONT)
Index	Name	Fl	PAR0	PAR1	PAR2	PAR3	PAR4	PAR5	PAR6	Source Code	Line
20090	9003
81	CALY	02	0000	0034	0035	0000	0000	0000	0000	LSRABAX_EXCU01	19
85	CALY	02	0000	0036	002F	0000	0000	0000	0000	LSRABAX_EXCU01	19
89	CMPS	41	02DB	8000	8000					LSRABAX_EXCU01	24
91	BRAF	02	0004							LSRABAX_EXCU01	24
92	BREL	80	0000							LSRABAX_EXCU01	24
93	mvqk	02	8100	025C	0000					LSRABAX_EXCU01	25
95	CMPS	20	02DD	8003	8003					LSRABAX_EXCU01	27
97	BRAF	05	0004							LSRABAX_EXCU01	27
98	BREL	80	0000							LSRABAX_EXCU01	27
99	MOVE	FF	02DD	0026	8003					LSRABAX_EXCU01	28
101	SETS	02	0000	0037	0000					LSRABAX_EXCU01	30
>>>>>	CMPS	20	02DD	8003	8003					LSRABAX_EXCU01	31
105	BRAF	02	0004							LSRABAX_EXCU01	31
106	BREL	80	0000							LSRABAX_EXCU01	31
107	MOVE	FF	02DD	8003	0026					LSRABAX_EXCU01	32
109	mvqk	02	0083	0000	0002					LSRABAX_EXCU01	34
111	FUNE	00	0000							LSRABAX_EXCU01	37
112	----	00	0000							LSRABAX_EXCU01	37
113	FUNP	31	0000	001B	8000	0000	8000	0000	0000	LSRABAX_EXCU02	1

Thanks in advance.

Regards,

Praveen.

[Former Member]

Hi Praveen,

This Oss Note : 49730 may help you to understand the scenario