Regarding Exception condition "CONFIG_NOT_FOUND" raised - while logging

Hi,
Could you please any one help me out.
When ever I login into the CRM Web UI with any of the Sales Manager Roles(SALESPRO or any ZRole that has been copied from SALESPRO) I get below error / exception:
The URL http://testinstsin1.sapcrmondemand.com:/sap/bc/bsp/sap/crm_ui_frame/BSPWDApplication.do was not called due to an error.
The following error text was processed in the system TRG : Exception condition "CONFIG_NOT_FOUND" raised.
The error occurred on the application server SGPSAROU01_TRG_00 and in the work process 1 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_BSP_DLC_CONFIGURATION~GET_CONFIG_DATA of program CL_BSP_DLC_CONFIGURATION2=====CP
Method: LOAD_CRITERIA_ADVANCED_SEARCH of program CL_CRM_CENTRAL_SEARCH=========CP
Method: LOAD of program CL_CRM_CENTRAL_SEARCH=========CP
Method: CONSTRUCTOR of program CL_CRM_CENTRAL_SEARCH=========CP
Method: GET_SEARCH_OBJECTS_AS_TABLE of program CL_CRM_CENTRAL_SEARCH=========CP
Method: DO_INIT of program CL_CRM_CNTR_LAUNCHER_IMPL=====CP
Method: DO_INIT of program CL_BSP_CTRL_ADAPTER===========CP
Method: CREATE_PAGE of program CL_BSP_PAGE_BASE==============CP
I am able to successfully login into the CRM WebUI with other roles. The problem is only with SALESPRO and ZRoles copied from SALESPRO.
Regards,
Rajanand

Oh... Sorry my last message was posted wrongly.
Please have a look at the class where this error happens and set a breakpoint to enter on debug mode and try to find the Role cofig Key, the Component usage, the object type and the object subtype for which the system is looking for a screen configuration.
You must have deleted some screen configuration  for your initial page on this roles, that is leadig to this problem.
Regards.

Similar Messages

  • Exception condition "CONFIG_NOT_FOUND" raised.

    Hi,
    I am trying to create an Opportunity in CRM 7.0 WEB UI. The moment i click on the create opportunity, i am getting a pop window, showing the transaction types which i have created in spro. But when i am selecting any one of them, i am getting a dump error mention in the subject matter.
    I did ST22 & checked the notes on service marketplace based in the description, but could not find anything relevant to this error.
    Here is, what i am getting the dump
    Error when processing your request
    What has happened?
    The URL http://uapkb2dc.gep.ge.com:8028/sap/bc/bsp/sap/crm_ui_frame/BSPWDApplication.do was not called due to an error.
    Note
    The following error text was processed in the system CS1 : Exception condition "CONFIG_NOT_FOUND" raised.
    The error occurred on the application server uapkb2dc_CS1_28 and in the work process 1 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: IF_BSP_DLC_CONFIGURATION~GET_CONFIG_DATA of program CL_BSP_DLC_CONFIGURATION2=====CP
    Method: GET_XML of program CL_CHTMLB_CONFIG==============CP
    Method: IF_BSP_ELEMENT~DO_AT_BEGINNING of program CL_CHTMLB_CONFIG==============CP
    Method: ONLAYOUT of program CLO247JT6QHPYQHQ33T513E8SHV84CP
    Method: %_ONLAYOUT of program CL_O247JT6QHPYQHQ33T513E8SHV84CP
    Method: DO_REQUEST of program CL_BSP_PAGE===================CP
    Method: CALL_VIEW of program CL_BSP_PAGE_BASE==============CP
    Method: CALL_VIEW of program CL_BSP_CONTROLLER=============CP
    Method: PROCESS_VIEW of program CL_BSP_WD_VIEW_CONTROLLER=====CP
    Method: DO_REQUEST of program CL_BSP_WD_VIEW_CONTROLLER=====CP
    I am not able to find the solution on this & i would appreciate of someone can help me fixing this.
    What i did is, I tried to add certain fields from "Configure Page Button" & added certain fields to right column. Since then, i am getting this error. I do not how to remove those.

    Hi,
    Go to transaction BSP_WB_CMPWB and open the compoenent BT111H_OPPT.
    Select the view you have modified and click on configuration tab. click on edit and select the custom config
    you have created.either you can remove the entries you have added which caused the dump or if you are not sure delete the
    custom configuration.This should fix the issue.
    Thanks,
    Rajiv.

  • Exception condition CONFIG_NOT_FOUND raised in opportunity page

    Hi Experts,
                    I am getting an exception in opportunity page as follows :
    The following error text was processed in the system MCD : Exception condition "CONFIG_NOT_FOUND" raised.
    The error occurred on the application server gsusapdp03_MCD_00 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: IF_BSP_DLC_CONFIGURATION~GET_CONFIG_DATA of program
    CL_BSP_DLC_CONFIGURATION2=====CP
                    I enhanced CRM opportunity component to include another view(Custom view).
    I have created the role config key 'ZMKT_PRO' and created a new configuration with following
    settings :
    Role Key                   ZMKT_PRO
    Component Usage  <DEFAULT>
    Object Type              BT111_OPPT
    Object Subtype      ZOPS
                    Now when I use code like mentioned below, i get the exception when opening the page
    <%
      DATA:
      lv_xml    TYPE string.
      lv_xml = controller->configuration_descr->get_config_data( ).
    %>
    <chtmlb:overviewFormConfig xml  = "<%= lv_xml %>"
                   mode = "RUNTIME" />
                    What wrong am I doing here?

    Hi Ruby,
                  Thanks for your reply. "Do you have the default configuration maintained?".
    Can you tell me which all default configurations need to be maintained?
                 My view is a simple blank view and I think I didnt check that checkbox which will
    automatically create all the buttons. Is there any way to work around this problem as I have already
    written a lot of code in this view. I also tried you code , but I had same exception. This exception is raised
    by the same get_config_data( ) method.  I debugged and found the source of exception at following point :
    CALL METHOD cl_bsp_dlc_xml_storage2=>get_config_data
              EXPORTING
                iv_component          = me->component
                iv_viewname           = me->viewname
                iv_role_key           = me->role_key
                iv_component_usage    = me->component_usage
                iv_object_type        = me->object_type
                iv_object_sub_type    = me->object_sub_type
                iv_pers_only          = iv_pers_only
              IMPORTING
                es_pers_data          = ls_pers_data
                es_config_data        = ls_config_data
                ev_config_data_origin = me->current_config_data_origin.
                Values were :
    ME->COMPONENT =  ZCRM_XXXX
    ME->VIEWNAME =       z(viewname)
    ME->ROLE_KEY =  ZMKT_PRO(ZROLE KEY )
    ME->COMPONENT_USAGE =  CUBTOpptOverview
    ME->OBJECT_TYPE  =  BT111_OPPT
    ME->OBJECT_SUB_TYPE  =  ZOPS
             Any solution?Thanks in advance....

  • Error while processing dimension: "Exception condition "X_MESSAGE" raised"

    Hi,
    I have recently transported an Appset from development to production environment. The transport finished successfully, without any error.
    Then I update the members of the dimensions and I process it (Production Environment). I get "Exception condition "X_MESSAGE" raised."
    I need to solve this problem as soon as possible.
    Regards,
    Miguel.

    check the below link
    Re: Dump when doing selective deletion

  • Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

    Hi All,
    I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
    At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
    ===========================================
    Runtime Errors RAISE_EXCEPTION
    Date and Time 25.07.2008 08:31:11
    Short text 
    Exception condition "METADATA_MISSING" raised. 
    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 "SAPLDSVAS_SERV" raised the exception 
    condition "METADATA_MISSING". 
    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" " " 
    "SAPLDSVAS_SERV" or "LDSVAS_SERVC7I" 
    "MAP_DSVAS_TT_DATA_TO_TT_25" 
    or 
    "SAPLDSVAS_SERV" "METADATA_MISSING" 
    or 
    "RDSMOP_MAIN " "METADATA_MISSING" 
    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... "terra" 
    Network address...... "172.16.1.198" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x Intel 801586" 
    Character length.... 16 Bits 
    Pointer length....... 32 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "TERRA" 
    Database type..... "ORACLE" 
    Database name..... "DSM" 
    Database user ID.. "SAPSR3" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Oct 23 2007 01:07:18" 
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" 
    Database version. "OCI_10201_SHARE (10.2.0.1.0) " 
    Patch level. 133 
    Patch text.. " " 
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." 
    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.... 8176 
    EM...... 37628064 
    Heap.... 0 
    Page.... 65536 
    MM Used. 31785376 
    | MM Free. 1656912
    =============================================
    Configuration:
    OS :Windows 2003 server.
    Solution Manager 7.0 SP15
    Oracle 10.2
    RAM - 2 GB
    Its bit urgent, Please help out us.
    Thanks in advance.
    Best Regards,
    Pratyusha

    Hi
    Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
    This error is related to ABAP program.
    Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

  • Exception condition "T681Z_MISSING" raised

    Hello,
    The SD collegaues are getting following dump while creating an invoice in transaction VF02.I am not able to find any help on SDN or any notes for the same.Please help.
    Short text
    Exception condition "T681Z_MISSING" raised.
    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 "SAPLV61Z" raised the exception
    condition "T681Z_MISSING".
    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" " "
    "SAPLV61Z" or "LV61ZF0T"
    "T681Z_SELECT"
    or
    "SAPLV61Z" "T681Z_MISSING"
    or
    "SAPMV60A " "T681Z_MISSING"
    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.
    Regards,

    Hello,
    Thanks for the help.
    I am not an ABAP person but still trying to write what i figured.
    The debugger hints at a sitution wherein a variable "ts_kappl" receives a value 'V' but after an assignment to other variable "available" the value of "available" changes to "0" somewhere.
    This results in a dump on trying to deliver the order for the functional people.
    Can anyone give some idea on this.
    Regards,

  • Short Dump, Exception condition "NOT_EXIST" raised

    Dear Colleagues!
    I am having a problem with short dump, I am getting the message Exception condition "NOT_EXIST" raised.
    I am trying to load data to ODS with full load and filtering via a DTP.
    In the monitoring the load doesn't even get started.
    I have already loaded data succesfully in this ODS... But now it doesn't work anymore..
    I also tried to replicate and active all the rules and objects again.
    And in the source system if I test the extractor it works fine.
    I saw an earlier thread on this issue, and it recommended programs ZDMDELTAREPAIR or RSBDELTAREPAIR, but this thread was especially for BW 3.5. We are using 7.0 and have SP10. Are these programs still valid or is there another note for 7.0?
    Hope you can help!
    Regards Silje
    Does anyone have any ideas?
    regards, Uros

    Hi again,
    I tried RSBDELTAREPAIR and it worked!
    Thanks to the forum again!
    Silje

  • Exception condition "CONVERSION_ERROR" raised.

    Hi,
    We have been getting short dumps in our production system daily. I was unable to locate the problem by looking at the dump. The dump says that CONVERSION_ERROR raised.
    Which application raised this exception? Again no clue on the same. Please find the text of the dump.
    Short text
        Exception condition "CONVERSION_ERROR" raised.
    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 "CL_SWF_CNT_CONTAINER==========CP" raised the
         exception
        condition "CONVERSION_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" " "
        "CL_SWF_CNT_CONTAINER==========CP" or "CL_SWF_CNT_CONTAINER==========CM02J"
        "IF_SWF_CNT_CONVERSION~TO_XML"
        or
        "CL_SWF_CNT_CONTAINER==========CP" "CONVERSION_ERROR"
        or
        "SAPMSSY1 " "CONVERSION_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... "zacwtbsrv0
        Network address...... "10.27.191.
        Operating system..... "Windows NT
        Release.............. "5.2"
        Hardware type........ "4x AMD64 L
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 9
        Shortdump setting.... "full"
        Database server... "ZACWTBSRV063"
        Database type..... "MSSQL"
        Database name..... "EP1"
        Database user ID.. "ep1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 21 2008 00:12:39"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 157
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    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...... 8379680
    Heap.... 0
    Page.... 16384
    MM Used. 8164576
    MM Free. 212256
    User and Transaction
        Client.............. 100
        User................ "WF-BATCH"
        Language Key........ "E"
        Transaction......... " "
      Transactions ID..... "FB565CDDF6D0F1BFA292001E0B5D7336"
      Program............. "CL_SWF_CNT_CONTAINER==========CP"
      Screen.............. "SAPMSSY1 3004"
      Screen Line......... 2
      Information on caller of Remote Function Call (RFC):
      System.............. "EP1"
      Database Release.... 700
      Kernel Release...... 700
      Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
      Call Type........... "synchron and transactional (emode 0, imode 0)"
      Inbound TID.........." "
      Inbound Queue Name..." "
      Outbound TID........."0A1BBF4011A4488D408222BD"
      Outbound Queue Name.." "
      Client.............. 100
      User................ "HPRETORIUS"
      Transaction......... " "
      Call Program........."SAPLERFC"
      Function Module..... "ARFC_DEST_SHIP"
      Call Destination.... "WORKFLOW_LOCAL_100"
      Source Server....... "zacwtbsrv064_EP1_00"
      Source IP Address... "10.27.191.64"
      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 "CL_SWF_CNT_CONTAINER==========CP" -
         in "IF_SWF_CNT_CONVERSION~TO_XML".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 67
        of the (Include) program "CL_SWF_CNT_CONTAINER==========CM02J".
    Source Code Extract
    Line  SourceCde
       37     lv_xml_table_req = 'X'.
       38   ENDIF.
       39   IF xml_stream IS REQUESTED.
       40     lv_xml_stream_req = 'X'.
       41   ENDIF.
       42
       43   IF use_xslt NE space.
       44
       45     cl_swf_cnt_conversion_service=>to_xml_xslt(
       46       EXPORTING
       47         container                  = me
       48         include_null_values        = include_null_values
      49         include_initial_values     = include_initial_values
      50         include_change_data        = include_change_data
      51         include_texts              = include_texts
      52         include_extension_elements = include_extension_elements
      53         save_delta_handling_info   = save_delta_handling_info
      54         xml_dom_req                = lv_xml_dom_req
      55         xml_table_req              = lv_xml_table_req
      56         xml_stream_req             = lv_xml_stream_req
      57       IMPORTING
      58         xml_dom                    = xml_dom
      59         xml_table                  = xml_table
      60         xml_stream                 = xml_stream
      61         xml_rendered_size          = xml_rendered_size
      62       EXCEPTIONS
      63         conversion_error           = 1
      64         OTHERS                     = 2
      65            ).
      66     IF sy-subrc <> 0.
    >>>>       RAISE conversion_error.
      68     ENDIF.
      69
      70   ELSE.
      71
      72     cl_swf_cnt_conversion_service=>to_xml_ixml(
      73       EXPORTING
      74         container                  = me
      75         include_null_values        = include_null_values
      76         include_initial_values     = include_initial_values
      77         include_typenames          = include_typenames
      78         include_change_data        = include_change_data
      79         include_texts              = include_texts
    Could you please help me out in resolving this issue?
    Is there any need to apply any OSS notes?
    Thanks in advance. And reward points will be given for the solution..
    Thanks,
    Ravikumar.

    Hi,
    U will receive this error when ever it is not possible to achieve runtime conversion.
    i.e When u r passing the data from one type variable to another type if the conversion is not defined or not possible u will get this dump. Just analyze the dump in ST22.
    Look at this simple example. Here i am trying to assign 101.23 to l_p for which length is not sufficient. So i will get dump. But if u do the same with character variable it will truncate the data.
    DATA: l_p(2) TYPE P DECIMALS 2.
    l_p = '103.23'.
    WRITE l_p.
    So check the place where u r getting the dump. It must be some assignment statement.
    Hope it gave some idea on ur case.
    Thanks,
    Vinod.

  • Exception condition "FAILED" raised.

    My TRM functional consultant has been trying to run end of day processes in the Transaction RKLNACHT but the following dump appears:
    Runtime Errors         RAISE_EXCEPTION                                                             
    Date and Time          16.05.2008 10:33:21                                                         
    Short text                                                                               
    Exception condition "FAILED" raised.                                                         
    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 "CL_POSITIONSERVICE_TRQ========CP" raised the               
         exception                                                                               
    condition "FAILED".                                                                               
    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" " "                                                                        
        "CL_POSITIONSERVICE_TRQ========CP" or "CL_POSITIONSERVICE_TRQ========CM00I"                  
        "GET_POSITIONS_BY_DIFF"                                                                               
    or                                                                               
    "CL_POSITIONSERVICE_TRQ========CP" "FAILED"                                                                               
    or                                                                               
    "RKLNACHT " "FAILED"                                                                         
        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... "tetradev"                                                             
        Network address...... "192.168.1.81"                                                         
        Operating system..... "SunOS"                                                                
        Release.............. "5.9"                                                                  
        Hardware type........ "sun4u"                                                                
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 0                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "tetradev"                                                                
        Database type..... "ORACLE"                                                                  
        Database name..... "DEV"                                                                     
        Database user ID.. "SAPSR3"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                        
        created (date)... "Aug 31 2006 20:59:23"                                                     
        create on........ "SunOS 5.9 Generic_117171-13 sun4u"                                        
        Database version. "OCI_102 (10.2.0.2.0) "                                                                               
    Patch level. 75                                                                               
    Patch text.. " "                                                                               
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."               
        SAP database version. 700                                                                    
        Operating system..... "SunOS 5.9, SunOS 5.10"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 16759392                                                                               
    Heap.... 0                                                                               
    Page.... 180224                                                                               
    MM Used. 10608952                                                                               
    MM Free. 1957592                                                                               
    User and Transaction                                                                               
    Client.............. 300                                                                     
        User................ "DARLINGTON"                                                            
        Language key........ "E"                                                                     
        Transaction......... "KLNACHT "                                                              
        Program............. "CL_POSITIONSERVICE_TRQ========CP"                                      
        Screen.............. "SAPMSSY0 1000"                                                         
        Screen line......... 6                                                                       
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "CL_POSITIONSERVICE_TRQ========CP" -                
         in "GET_POSITIONS_BY_DIFF".                                                                 
        The main program was "RKLNACHT ".                                                                               
    In the source code you have the termination point in line 37                                 
        of the (Include) program "CL_POSITIONSERVICE_TRQ========CM00I".                              
    Source Code Extract                                                                               
    Line       SourceCde                                                                               
    7              l_selector         TYPE REF TO cl_flow_selector_dif,                               
        8      * workarea for table with positions                                                        
        9              l_tab_position     TYPE trqy_position_obj,                                         
       10              l_position         TYPE REF TO if_position_trq,                                    
       11              l_count            type i.                                                         
       12                                                                               
    13      * initialization                                                                               
    14        CLEAR re_tab_position.                                                                   
       15                                                                               
    16      * Get positions for ranges                                                                 
       17        CALL METHOD ca_pos_identifier_dif=>agent->get_persistent_by_range                        
       18          EXPORTING                                                                               
    19            im_context     = trqco_con_trq                                                       
       20            im_ranges      = im_ranges                                                           
       21          RECEIVING                                                                               
    22            re_identifiers = l_tab_identifier.                                                   
       23        CHECK NOT l_tab_identifier IS INITIAL.                                                   
       24                                                                               
    25        LOOP AT l_tab_identifier INTO l_identifier.                                              
       26                                                                               
    27          l_selector = l_identifier->derive_selector( ).                                         
       28                                                                               
    29      *   get TRQ positions for selectors                                                        
       30          CALL METHOD read_positions_by_selector                                                 
       31            EXPORTING                                                                               
    32              im_selector      = l_selector                                                      
       33            RECEIVING                                                                               
    34              re_tab_positions = l_tab_position.                                                 
       35          DESCRIBE TABLE l_tab_position LINES l_count.                                           
       36          IF l_count <> 1.                                                                       
    >>>>>            raise failed.                                                                        
       38          ENDIF.                                                                               
    39          APPEND LINES OF l_tab_position TO re_tab_position.                                     
       40        ENDLOOP.                                                                               
    41                                                                               
    42      ENDMETHOD.                                                                               
    Contents of system fields                                                                        
    Name          Val.                                                                               
    SY-SUBRC      0                                                                               
    SY-INDEX      0                                                                               
    SY-TABIX      2                                                                               
    SY-DBCNT      1                                                                               
    SY-FDPOS      0                                                                               
    SY-LSIND      0                                                                               
    SY-PAGNO      0                                                                               
    SY-LINNO      1                                                                               
    SY-COLNO      1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE      End-of-Day Processing                                                                   
    SY-MSGTY      E                                                                               
    SY-MSGID      64                                                                               
    SY-MSGNO      030                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    SY-MODNO      0                                                                               
    SY-DATUM      20080516                                                                               
    SY-UZEIT      103319                                                                               
    SY-XPROG      SAPLSBAL_DB                                                                             
    SY-XFORM      %_CONTROL_EXIT_DYNPRO                                                                   
    Does anyone have suggestions as to how I can solve this problem?
    Assistance will be appreciated.

    bumping...any suggestions...welcome

  • Exception Condition "Fatal_Error" Raised in SMQ2

    Hi,
    I am doing File to Proxy(ECC) Asynchronous scenario. in this getting the error in Target side(ECC) in SMQ2 message is showing error , when I double click on this error getting the error message like  Exception Condition "Fatal_Error" Raised.
    Because of this interface error Remaining interfaces also getting failure.
    these interfaces was working fine.
    I searched in SDN, but i didn't get proper solution for related to this issue.Pl suggest us to resolve this issue.
    Regards,
    Pasi

    Hi Pasi,
    This looks like a data issue which has resulted in an exception in Proxy code. If this is not a production system I will suggest you to delete the error entry from queue and test with an older successful data and see whether it gets successfully executed or not.
    Or you can try to debug the proxy code, with XML structure (taken from SXMB_MONI of PI) and see where the exception is raised
    Regards
    Suraj

  • Exception condition "NO_TRIGGER_INSTANCE" raised error in SMQ2

    Dear all,
    i'm getting this error  in SMQ2 transaction of xi server.
    Exception condition "NO_TRIGGER_INSTANCE' raised
    Did anyone encounter this issue before. Pls share your inputs in resolving it,
    Regards,
    Jack

    Hi ,
    Can you provide the details of this  dump from ST22  for understanding .
    Regards ,
    Hanumant .

  • RFC_ERROR_SYSTEM_FAILURE: Exception condition "CNTL_ERROR" raised.

    I wrote a function.This read codes from a  .txt file, create an abap program dinamically and after run it.
    I wrote a java program with jco  and i wrote an abap program for calling function .&#304;f i runned abap program not happened any problem.But i runned java program.i saw this error :
    RFC_ERROR_SYSTEM_FAILURE: Exception condition "CNTL_ERROR" raised.
    My function :
    FUNCTION Z_MS_FUNC2.
    *"*"Local Interface:
    *"  IMPORTING
    *"  EXPORTING
    *"     VALUE(RESULT) TYPE  ZMS_SONUC-SONUC
    DATA: code TYPE TABLE OF rssource-line.
    data : p_file TYPE string.
    p_file = 'C:\deneme.txt'.
        CALL FUNCTION 'GUI_UPLOAD'
          EXPORTING
            filename                      = p_file
            FILETYPE                      = 'ASC'
          tables
            data_tab                      = code.
    INSERT REPORT 'zms_dinamik002' FROM code.
    SUBMIT zms_dinamik002 AND RETURN.
    result = 'Successfull.'.
    ENDFUNCTION.
    this code  show error row :
    38     CALL METHOD CL_GUI_FRONTEND_SERVICES=>DIRECTORY_LIST_FILES                  
        39       EXPORTING                                                                 
        40         DIRECTORY                   = FILE                                      
        41         FILTER                      = ''                                        
        42         FILES_ONLY                  = 'X'                                       
        43 *    DIRECTORIES_ONLY            = 'X'                                          
        44       CHANGING                                                                  
        45         FILE_TABLE                  = filetab                                   
        46         COUNT                       = count                                     
        47       EXCEPTIONS                                                                
        48         CNTL_ERROR                  = 1                                         
        49         DIRECTORY_LIST_FILES_FAILED = 2                                         
        50         WRONG_PARAMETER             = 3                                         
        51         ERROR_NO_GUI                = 4                                         
        52         others                      = 5.                                        
        53                                                                               
    54     IF SY-SUBRC <> 0.                                                           
    >>>>>       RAISE CNTL_ERROR.                                                         
        56     ENDIF.
    deneme.txt
    report mehmet.
    data wa like zms0005.
    wa-jop_id = 14.
    wa-jop_name = 'UZAK4'.
    modify zms0005 from wa.

    Hi,
    wa-jop is not defined (data: wa-jop type...)!
    Try to insert the coding-lines in a new report. Than make a syntax check.
    Regards Mario
    Edited by: Mario Müller on Mar 11, 2008 6:47 AM

  • Error message "Exception condition "INTERNAL_ERROR" raised" in Backend.

    Hi
    I am trying to replicate the materials from Backend to SRM and every time I get the message "Exception condition "INTERNAL_ERROR" raised" in the backend system and the Outbound queue in R/3 system gets stuck.
    I have maintained the middleware tables correctly and was able to download other objects.
    Can someone kindly help me out in determining the error.
    Regards
    Manoj

    Hello Manoj,
    I suppose your´re working with a release < SRM4.0? Then please check the following settings:
    SPRO
    Customer Relationship Management > Master data  > Condition Technique
    Create general configuration parameters                            
    Maintain here the TIMEZONE_MASTER_DATA_DB -> pls read the documentation for this point in customizing.
    BR
    Michael

  • Exception condition "MESSAGE_ID_NOT_FOUND" raised in SMQ2

    Hi,
    I am getting below error in production PI(PI7.3) SMQ2 ,
    Exception condition "MESSAGE_ID_NOT_FOUND" raised.
    i tried to refresh and execute LUW but entry still going to same status and i have deleted first entry then next entry is going to same status.
    can you please provide your inputs on this to fix this issue.
    Cheers,
    Giri

    Hi Giri,
    Check if everything is fine with respect to your DB.
    also check this note.
    1293244 - MESSAGE_ID_NOT_FOUND: Event-driven message processing
    Thanks and Regards,
    Naveen

  • Exception condition "COMMUNICATION_ERROR" raised.

    Hi Experts,
    Now Im working with Business graphis. After comple the designing I Tested  the Webdynpro Application.
    It shows Dump like "Exception condition "COMMUNICATION_ERROR" raised".
    The Error Description is :
    The URL http://sapecc6ides.ssdomain.com:8001/sap/bc/webdynpro/sap/zgra_demo/ was not called due to an error.
    Note
    The following error text was processed in the system E60 : Exception condition "COMMUNICATION_ERROR" raised.
    The error occurred on the application server sapecc6ides_E60_01 and in the work process 1 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: EXECUTE of program CL_IGS_CHART_ENGINE===========CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LBUSINESS_GRAPHICS======CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
    Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP
    Method: CONV_VIEW_INTO_VE_ADAPTER_TREE of program CL_WDR_INTERNAL_WINDOW_ADAPTERCP
    Method: SET_CONTENT_BY_WINDOW of program CL_WDR_INTERNAL_WINDOW_ADAPTERCP
    Method: RENDER_WINDOWS of program CL_WDR_CLIENT_SSR=============CP
    Method: IF_WDR_RESPONSE_RENDERER~RENDER_VIEWS of program CL_WDR_CLIENT_SSR=============CP
    Method: IF_WDR_RESPONSE_RENDERER~RENDER_USER_INTERFACE_UPDATES of program CL_WDR_CLIENT_SSR=============CP
    Any one help me on this issue.
    Points will be rewarded.
    Edited by: Viji on Dec 21, 2007 1:04 PM

    Hi,
    I think it's due to lack of configured IGS - Check your Internet Graphics Server settings/config.
    Regards
    Raja Sekhar

Maybe you are looking for