Skip to Content
avatar image
Former Member

Runtime Error : CALL_DIALOG_CONTAINER_MISSING

Please Help, I am getting the following Dump:

Regards,

Runtime Errors CALL_DIALOG_CONTAINER_MISSING

Date and Time 04.12.2008 10:29:33

Short tex

Format error during parameter transfer: No further container available.

What happened?

Error in the SAP kernel.

The current ABAP "SAPMS380" 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

For a precise analysis of the error, you should supply

documents with as many details as possible.

How to correct the error

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.

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:

"CALL_DIALOG_CONTAINER_MISSING" " "

"SAPMS380" or " "

"SYSTEM-EXIT"

System environment

SAP-Release 700

Application server... "DMATE"

Network address...... "140.1.1.141"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... "dmate"

Database type..... "ADABAS D"

Database name..... "AD0"

Database user ID.. "SAPAD0"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Jun 23 2008 00:09:46"

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

Database version. "SQLDBC 7.6.0.018 CL 119055 "

Patch level. 166

Patch text.. " "

Database............. "MaxDB 7.6, MaxDB 7.7"

SAP database version. 700

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

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 456692560

Heap.... 0

Page.... 267976704

MM Used. 833296

MM Free. 3353920

User and Transaction

Client.............. 040

User................ "CONSULTANT"

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

Transaction......... "FB1S "

Transactions ID..... "A5CCC1DDC388F1439FA4001143E563CA"

Program............. "SAPMS380"

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

Screen line......... 0

Information on where terminated

Termination occurred in the ABAP program "SAPMS380" - in "SYSTEM-EXIT".

The main program was "SAPMS380 ".

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

of the (Include) program " ".

Contents of system fields

Name Val.

SY-SUBRC 0

SY-INDEX 0

SY-TABIX 0

SY-DBCNT 0

SY-FDPOS 0

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY

SY-UCOMM

SY-TITLE ABAP Runtime Error

SY-MSGTY

SY-MSGID

SY-MSGNO 000

SY-MSGV1

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO 0

SY-DATUM 20081204

SY-UZEIT 102932

SY-XPROG

SY-XFORM

Active Calls/Events

No. Ty. Program Include Line

Name

1 EVENT SAPMS380 ??? 0

SYSTEM-EXIT

Chosen variables

Name

Val.

No. 1 Ty. EVENT

Name SYSTEM-EXIT

Internal notes

The termination was triggered in function "imp_ldial_segment"

of the SAP kernel, in line 1915 of the module

"//bas/700_REL/src/krn/runt/abxdat.c#4".

The internal operation just processed is " ".

Internal mode was started at 20081204102932.

Requested paging area: 32706.

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=5540)

When : 12/4/2008 10:29:32.703

Threads : 2

Computer Name : DMATE

User Name : SAPServiceAD0

Number of Processors: 4

Processor Type: EM64T Family 15 Model 4 Stepping 1

Windows Version : 5.2 Current Build: 3790

State Dump for Thread Id 704

FramePtr ReturnAd Param#1 Function Name

0000000007ead400 0000000077d7047f 0000000000343e90 ntdll!NtWaitForSingleObject

0000000007ead4a0 000000000173b1d1 0000000000000014 kernel32!WaitForSingleObjectEx

0000000007ead6f0 00000000006179c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]

0000000007ead720 0000000000b05d9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]

0000000007ead770 0000000000b0afc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7093)]

0000000007eae150 00000000009736d2 0000000001c859b0 disp+work!ab_rabax [abrabax.c (1231)]

0000000007eae190 00000000009aee62 0000000007eaf4d0 disp+work!imp_ldial_segment [abxdat.c (1915)]

0000000007eae1f0 0000000000a2b2a6 0000000007eae330 disp+work!ab_ReadData [abconcnv.c (1397)]

0000000007eae230 0000000000a2b13a 0000000007eae330 disp+work!ReadSkipValue [abconne.c (7339)]

0000000007eae270 0000000000a3500f 00000000000000ae disp+work!ReadSkipValue [abconne.c (7369)]

0000000007eaf710 0000000000977317 0000000003698300 disp+work!ab_connread [abconne.c (4924)]

0000000007eaf750 0000000000b68126 0000000007eb6050 disp+work!ab_ldiaimport [abxdat.c (2052)]

0000000007eaf780 000000000064bc9c 0000000000000000 disp+work!ab_nmode [abtcod.c (939)]

0000000007eb6020 0000000000b6633f 0000000007eb6078 disp+work!dy_cdiag [dynpabsv.c (1830)]

0000000007eb9640 0000000000b0a0f0 0000000001d0b870 disp+work!ab_sdialog [abtcod.c (300)]

0000000007eb9f30 0000000000b0c3c0 0000000000000001 disp+work!rabax_do [abrabax.c (5338)]

0000000007eba910 0000000000a35c78 0000000001d0b8a0 disp+work!ab_rabax [abrabax.c (1497)]

0000000007eba960 0000000000a36730 0000000800007fff disp+work!ab_mnew [abmarea.c (228)]

0000000007eba9d0 00000000009726b8 000000000000096a disp+work!ab_mnnext [abmarea.c (297)]

0000000007ebaa20 00000000009b07bb 000000000000000c disp+work!exp_ldial_segment [abxdat.c (1391)]

0000000007ebaa70 0000000000a26d88 000007fe7257a190 disp+work!ab_WriteData [abconcnv.c (1590)]

0000000007ebaaf0 0000000000a33d8b 000007fe8c76c7d8 disp+work!export_itab [abconne.c (3877)]

0000000007ebbc60 000000000097620d 0000000000000000 disp+work!ab_connwrite [abconne.c (1992)]

0000000007ebbca0 0000000000b69431 000007ffe7be1f88 disp+work!ab_locex [abxdat.c (1008)]

0000000007ebbd30 0000000000b69e17 000007ffe7be1f88 disp+work!dial_local [abtcod.c (213)]

0000000007ebbea0 0000000000ad3390 0000000000000000 disp+work!ab_cdialog [abtcod.c (203)]

0000000007ebc740 0000000000ad50b3 0000000000000129 disp+work!ab_retdynp [abdynpro.c (671)]

0000000007ebc7d0 0000000000679328 0000000000000129 disp+work!ab_dstep [abdynpro.c (492)]

0000000007ebc950 000000000067d76d 000007fe725e08ae disp+work!dynpmcal [dymainstp.c (2396)]

0000000007ebc9f0 000000000067ca2a 0000000000000000 disp+work!dynppai0 [dymainstp.c (1106)]

0000000007ebcaa0 00000000006395c5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]

0000000007ebfc30 00000000004dbc4c 0000000000000002 disp+work!dynpen00 [dymain.c (1646)]

0000000007ebfeb0 000000000042f096 0000000007f62ff0 disp+work!TskhLoop [thxxhead.c (4538)]

0000000007ebfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1136)]

0000000007ebff10 00000000019e84b1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]

0000000007ebff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]

0000000007ebffa0 0000000000000000 00000000019e8340 kernel32!BaseProcessStart

State Dump for Thread Id 11a0

FramePtr ReturnAd Param#1 Function Name

000000000c9dfe40 0000000077d5f651 0000000007f1cc60 ntdll!NtFsControlFile

000000000c9dfeb0 00000000018ce23f 0000000000000000 kernel32!ConnectNamedPipe

000000000c9dff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]

000000000c9dff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex

000000000c9dffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart

List of ABAP programs affected

Index Typ Program Group Date Time Size Lang.

0 Prg SAPMS380 0 09.03.2008 19:40:55 182272 E

1 Typ SYST 0 09.09.2004 14:18:12 34816

Directory of Application Tables

Name Date Time Lngth

Val.

Program SAPMS380

SYST . . : : 00004612

\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Dec 04, 2008 at 09:16 AM

    You need to add more info. When are you getting the error?, whats triggering it?, what troobleshooting steps have you done so far?

    I can only find one note related to that dump...and without info is very difficult to tell if its related or not to your case... anyhow, Read Note 370415

    Regards

    Juan

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Juan,

      I also received the same error while deleting the Product categories Under Responsibility of a Purchase group in Transaction PPOMA_BBP in SRM.

      Once it allows me to delete them but I do the same twice I do get like below

      "Runtime error MEMORY_NO_MORE_PAGING has occurred"

      If you have any idea on the above issues then please help me to fix this issues.

      Thanks & regards

      Pratap J

  • avatar image
    Former Member
    Apr 06, 2009 at 05:13 AM

    thanks

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Chaitanya,

      I'm getting the same error on the same program. Did you solve your problem?

      Many thanks in advance.

      Regards,

      Flaviano Passarelli