Quantcast
Channel: SCN : All Content - ABAP Development
Viewing all articles
Browse latest Browse all 8332

Exception condition "INTERNAL_ERROR" raised

$
0
0

Runtime Errors         RAISE_EXCEPTION

Date and Time          21.08.2014 21:53:43

 

What happened?

     The current ABAP/4 program encountered an unexpected

     situation.

 

 

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

     A RAISE statement in the program "SAPLCEI0" raised the exception

     condition "INTERNAL_ERROR".

     Since the exception was not intercepted by a superior

     program, processing was terminated.

 

     Short description of exception condition:

 

     For detailed documentation of the exception condition, use

     Transaction SE37 (Function Library). You can take the called

     function module from the display of active calls.

     -

How to correct 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:

 

 

    "RAISE_EXCEPTION" " "

    "SAPLCEI0" or "LCEI0U30"

    "VC_I_GET_CONFIGURATION"

 

 

    or

 

 

    "SAPLCEI0" "INTERNAL_ERROR"

 

 

    or

 

 

    "SAPMSSY1 " "INTERNAL_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.

 

System environment

    SAP-Release 700

 

 

    Application server... "sap01717"

    Network address...... "10.61.89.105"

    Operating system..... "Linux"

    Release.............. "2.6.40-0.8-default"

    Hardware type........ "x86_64"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.. 15

    Shortdump setting.... "full"

 

 

    Database server... "sap01716"

    Database type..... "ORACLE"

    Database name..... "QWT"

    Database user ID.. "SAPDAT"

 

 

    Terminal................. "10.61.31.114"

 

 

    Char.set.... "C"

 

    SAP kernel....... 720

    created (date)... "Mar 17 2013 18:46:25"

    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr121116"

    Database version. "OCI_102, 11.2.0.3.0, V1, default"

 

 

    Patch level. 420

    Patch text.. " "

 

 

    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"

    SAP database version. 720

    Operating system..... "Linux 2.6, Linux 3"

 

 

    Memory consumption

    Roll.... 0

    EM...... 16759232

    Heap.... 0

    Page.... 16384

    MM Used. 14978448

    MM Free. 1777544

 

 

User and Transaction

    Client.............. 500

    User................ "RFC_TAULIA"

    Language Key........ "E"

    Transaction......... " "

    Transactions ID..... "53F6515E320E5BBBE10000000A3D5969"

 

 

    Program............. "SAPLCEI0"

    Screen.............. "SAPMSSY1 3004"

    Screen Line......... 2

 

 

    Information on caller of Remote Function Call (RFC):

    System.............. "########"

    Database Release.... 720

    Kernel Release...... 720

    Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"

    Inbound TID.........." "

    Inbound Queue Name..." "

    Outbound TID........." "

    Outbound Queue Name.." "

 

 

    Client.............. "###"

    User................ "############"

    Transaction......... " "

    Call Program........."SAPJCo30"

    Function Module..... "/TAULIA/CT_RFC_BUS_DOC_GET"

    Call Destination.... "SAPR3"

    Source Server....... "SWDETDOLPHPODD"

    Source IP Address... "10.61.31.114"

 

 

    Additional information on RFC logon:

    Trusted Relationship " "

    Logon Return Code... 0

    Trusted Return Code. 0

 

 

    Note: For releases < 4.0, information on the RFC caller are often

    only partially available.

 

 

Information on where terminated

    Termination occurred in the ABAP program "SAPLCEI0" - in

     "VC_I_GET_CONFIGURATION".

    The main program was "SAPMSSY1 ".

 

 

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

    of the (Include) program "LCEI0U30".


Viewing all articles
Browse latest Browse all 8332

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>