Dump Analysis in J2IU Tcode

On execution of the report its showing the following dump.
Runtime Errors         PERFORM_CONFLICT_UC_STRUCT
Except.                CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time          21.05.2009 13:26:24
Short text
     Structure-type conflict when calling a FORM
What happened?
     Error in the ABAP Application Program
     The current ABAP program "J_1IRUTZ" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
      not caught and
     therefore caused a runtime error.
     The reason for the exception is:
     The call of the FORM "DETERMINE_DEFAULT_VALUES" is incorrect:
     The actual parameter no. 2 is at PERFORM not compatible with the
     structure type requested by FORM "DETERMINE_DEFAULT_VALUES".
     The FORM "DETERMINE_DEFAULT_VALUES" is defined in program "SAPMJ1II".
     This error occurs in Unicode if the fragment view of the types is
     incompatible.
Missing Handling of System Exception
     Program                                 J_1IRUTZ
Trigger Location of Exception
    Program                                 J_1IRUTZ
    Include                                 J_1IUPBO
    Row                                     97
    Module type                             (MODULE PBO)
    Module Name                             FILL_PAYABLE_AMOUNT
Source Code Extract
Line  SourceCde
   67   ENDIF.
   68 ENDMODULE.                             " FILL_ACCOUNT_BALANCES  OUTPUT
   69 &----
   70 *&      Module  FILL_PAYABLE_AMOUNT  OUTPUT
   71 &----
   72 *       text                                                           *
   73 ----
   74 MODULE fill_payable_amount OUTPUT.
   75   IF flg_first_time = 'X' .
   76 *get the total value of amount payable
   77     LOOP AT it_exchdr.
   78       totals-bed = totals-bed + it_exchdr-exbed.
   79       totals-aed = totals-aed + it_exchdr-exaed.
   80       totals-sed = totals-sed + it_exchdr-exsed.
   81       totals-cess = totals-cess + it_exchdr-cess.
   82        totals-ecs = totals-ecs + it_exchdr-ecs.
   83
   84 *NCCD changes starts
   85       totals-nccd = totals-nccd + it_exchdr-nccd.
   86 *NCCD changes ends
   86 *NCCD changes ends
   87     ENDLOOP.
   88 *determine default values based on customization
   89
   90     PERFORM determine_default_values(sapmj1ii)
   91                                     USING p_exgrp
   92                                           totals   "#EC NO_INCOMP
   93                                           max_bal
   94                                    CHANGING  rg23a
   95                                              rg23c
   96                                              st_pla.
>>>>>     ent_tot-bed = rg23a-bed + rg23c-bed + st_pla-bed.
   98     ent_tot-sed = rg23a-sed + rg23c-sed + st_pla-sed.
   99     ent_tot-aed = rg23a-aed + rg23c-aed + st_pla-aed.
  100     ent_tot-ecs = rg23a-ecs + rg23c-ecs + st_pla-ecs.
  101
  102 *NCCD changes starts
  103     ent_tot-nccd = rg23a-nccd + rg23c-nccd + st_pla-nccd.
  104 *NCCD changes ends
  105     ent_tot-cess = st_pla-cess.
  106
  107     flg_first_time = space.
  108   ENDIF.
  109 *
  110   PERFORM check_min_balances.
  111 ENDMODULE.                             " FILL_PAYABLE_AMOUNT  OUTPUT
  112 &----
  113 *&      Module  STATUS_9010  OUTPUT
  114 &----
  115 *       text                                                           *
  116 ----
Please help me out.....
Regards.
Santosh Alle

hi,
I think J2IU is utilization of excise. Use the t-code J2IUN for Excise Utilization.
Regards
Aromal R

Similar Messages

  • ABAP dump while running the tcode MIGO

    Hi All,
    I am getting the abap dump while running the tcode MIGO when I searched I got two relevant sap notes but our functional team said that its not applicable in our case.
    Please find the details of ST22 analysis-:
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          17.04.2009 13:18:45
    Short text
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
        Short text of error message:
        No RFC destination is defined for SAP Global Trade Services
        Long text of error message:
        Technical information about the message:
        Message class....... "/SAPSLL/PLUGINR3"
        Number.............. 002
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        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:
        "MESSAGE_TYPE_X" " "
        "SAPLMBWL" or "LMBWLU21"
        "MB_POST_GOODS_MOVEMENT"
    SAP Notes i have reffered 1098491, 1041122
    Currently we are running on SAP_APPL     600     0007     SAPKH60007     
    Regards,
    Prashant

    Hi Rohit,
    This particular note is valid for
    Support
    Packages Release Package
    Name
    PI 2004_1_46B SAPKIPZI38
    PI 2004_1_46C SAPKIPZI48
    PI 2004_1_470 SAPKIPZI58
    PI 2004_1_500 SAPKIPZI68
    Our system is running on PI_BASIS     2006_1_700     0005     SAPKIPYM05
    Pls suggest.
    Regards,
    Prashant

  • What is Short Dump Analysis and  secendry index  ?

    Dear Experts .
    1.) What is purpose of T-codes SE30 and ST22 ?
    What is Short Dump Analysis ?
    2.) What is secendry index , How to use it ? How it effects the Performance of a report ?
    Please it is urgent ...
    Regards : Rajneesh

    Hi
    A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
    Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
    The snapshot contains the following information:
    Why the program has terminated
    What caused the program termination
    Where in the program code the termination occurred
    What you can do to correct the error
    The values of the relevant system fields when the program terminated
    The calls or events that were active when the program terminated
    Any other programs that are affected.
    http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
    Index: Technical key of a database table.
    Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
    Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
    Structure of an Index
    An index can be used to speed up the selection of data records from a table.
    An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
    When creating indexes, please note that:
    An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
    Only those fields whose values significantly restrict the amount of data are meaningful in an index.
    When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
    Make sure that the indexes on a table are as disjunctive as possible.
    (That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
    Accessing tables using Indexes
    The database optimizer decides which index on the table should be used by the database to access data records.
    You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
    The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
    If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
    When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

  • Error in HRPAD31 ( Short dump Analysis )

    Hi friends,
    When i am changing the existing qualification or adding new qualification it is showing this error in short dump
    Pls advise me if there is some relationship i am missing in 031 ?
    here is the description of short dump
    Runtime Error  DBIF_RSQL_SQL_ERROR 
    Exception        CX_SY_OPEN_SQL_DB                                   
    Occurred on     10.09.2008 at   10:48:39                                                                               
    An SQL error occurred when accessing a table.                                                                               
    What happened?                                                                               
    What can you do?                                                                               
    Make a note of the actions and input which caused the error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                                                               
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer   
    termination messages, especially those beyond their normal deletion        
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below   
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB',  wasneither                                                                   
    caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"                                                                  
    Since the caller of the procedure could not have expected this exception to occcur, the running program was terminated.                                 
    The reason for the exception is:                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure "ADATA_DB" 
    "(FORM)", or declared in the procedure's RAISING clause.                       
    To prevent the exception, note the following:                                  
    Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31 by 80 in tablespace PSAPSTABD"        
    Internal call code.........: "RSQL/INSR/HRPAD31"                
    Please check the entries in the system log (Transaction SM21).                                                                               
    You may able to find an interim solution to the problem           
    in the SAP note system. If you have access to the note system yourself, use the following search criteria:                                                                               
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                                       
    "SAPLRHAP" or "LRHAPF1K"                                                       
    "ADATA_DB"                                                                     
    System environment                                                                               
    SAP Release.............. "620"                                                                               
    Application server....... "Development"                                    
    Network address.......... "200.200.200.10"                             
    Operating system......... "Windows NT"                                 
    Release.................. "5.2"                                        
    Hardware type............ "2x IA64 Level 3"                            
    Character length......... 8 Bits                                       
    Pointer length........... 64 Bits                                      
    Work process number...... 1                                            
    Short dump setting....... "full"                                                                               
    Database server.......... "Development"                                    
    Database type............ "ORACLE"                                     
    Database name............ "VC3"                                        
    Database owner........... "SAPR3"                                                                               
    Character set............ "English_United State"                                                                               
    SAP kernel............... "640"                                        
    Created on............... "Aug 16 2007 23:23:39"                       
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "                                                                               
    Patch level.............. "196"                                        
    Patch text............... " "                                                                               
    Supported environment....                                              
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 
    User, transaction...                                                                               
    Client.............. 600                                                      
    User................ "HUSER"                                                
    Language key........ "E"                                                      
    Transaction......... "PP01 "                                                  
    Program............. "SAPLRHAP"                                               
    Screen.............. "MP100100 6000"                                          
    Screen line......... 16                                                                               
    Information on where terminated                                                                               
    The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".        
    The main program was "MP100100 ".                                                                               
    The termination occurred in line 57 of the source code of the (Include)  program LRHAPF1K"                                                           
    of the source code of program "LRHAPF1K" (when calling the editor 570).       
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the  procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.                                              
    The procedure is in the program "SAPLRHAP ". Its source code starts in line 8  of the (Include) program "LRHAPF1K ".                                                                               
    PLS LET ME KNOW IF I NEED TO CHECK ALL MY CONFIGURATION ?

    Hi Ted,
    It is working, i just logged off and logged in. Now there is no error.
    Thanks for all your support. I am struggling on this isse from 3 days and could not sort it out.
    I appreciate on more time for your knowledge.
    I have rewarded the points also....  
    Regards
    HR user

  • How to do DUMP Analysis ?

    How to do DUMP Analysis ?Can anybody explain me the steps to solve the dump step by step ?
    thanks
    Naresh

    Hi
    A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
    Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
    The snapshot contains the following information:
    Why the program has terminated
    What caused the program termination
    Where in the program code the termination occurred
    What you can do to correct the error
    The values of the relevant system fields when the program terminated
    The calls or events that were active when the program terminated
    Any other programs that are affected.
    http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
    Index: Technical key of a database table.
    Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
    Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
    Structure of an Index
    An index can be used to speed up the selection of data records from a table.
    An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
    When creating indexes, please note that:
    An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
    Only those fields whose values significantly restrict the amount of data are meaningful in an index.
    When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
    Make sure that the indexes on a table are as disjunctive as possible.
    (That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
    Accessing tables using Indexes
    The database optimizer decides which index on the table should be used by the database to access data records.
    You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
    The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
    If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
    When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

  • ABAP dump analysis

    HI all
    Pl let me know ABAP Dump analysis .which type of abap dump problems arrived every time. pl explain explain more than two or three  examples recently u face abap dumps and solutions hoe u resolved that problems
    [removed by moderator]
    I really appreciate your feed back on this request
    Thanks
    Hari

    hi
    <b>Dump Analysis</b>
    A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
    Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
    <b>
    The snapshot contains the following information</b>:
    Why the program has terminated
    What caused the program termination
    Where in the program code the termination occurred
    What you can do to correct the error
    The values of the relevant system fields when the program terminated
    The calls or events that were active when the program terminated
    Any other programs that are affected.
    In Basis 6.20, you can also reorganize short dumps from within ST22 via menu option Goto->Reorganize but I'm not sure if that exists in 4.6C. This option allows you to specify a different retention period for the short dumps. You would need to use this manual reorganization process in place of the batch version.
    <b>If there is requirement for you to keep some of your ABAP short dumps there is also an option in ST22 to allow you to keep them indefinately. When you see the list of dumps, you simply cursor select the required
    dump(s0 and select menu option Short dump->Keep. Kept short dumps are not subject to reorganization until they are released again.</b>
    regards
    ravish
    <b>plz dont forget to reward points if helpful</b>

  • Sql error dump while using pfcg tcode.

    hi,
    I am getting one dump while executing PFCG tcode. Hereunder i am pasting the log,
    Runtime Errors DBIF_RSQL_SQL_ERROR
    Exception CX_SY_OPEN_SQL_DB
    Database error text........: "ORA-01115: IO error reading block from fil
    (block # 52025)#ORA-01110: data file 9:
    '/oracle/OPL/sapdata2/sr3_6/sr3.data6'#ORA-27091: unable to queue
    I/O#ORA-27072: File I/O error#HPUX-ia64 Error: 5: I/O error#Additional
    information: 3#Additional inform"
    Internal call code.........: "[RSQL/FTCH/AGR_FLAGS ]"
    Please check the entries in the system log (Transaction SM21).
    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:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "SAPLPRGN_START3" or "LPRGN_START3U33"
    "PRGN_START3_LOAD_FLAGS"
    Soon help will be appreciated.
    regards

    Hello,
    Take a look at note 546006 - point 6
    Thanks

  • Crash Dump Analysis, application cannot execute

    Welcome,
    my question regarding to dump crash. I have problem with application. When I run application, I see first intro, second intro and later application crash and return to the desktop with error stop working. I created dump file of error and paste analyze below. 
    I must add, that this application works properly on the other computer with Windows Server 2012 Datacenter x64. Could someone tell me, where is the problem, why application crashed with error access violation?
    Primary Analysis
    Crash Dump Analysis
    Windows 8 Version 9600 MP (8 procs) Free x86 compatible
    Product: WinNt, suite: SingleUserTS
    kernel32.dll version: 6.3.9600.17415 (winblue_r4.141028-1500)
    Machine Name:
    Debug session time: Sun Jan 25 04:09:51.000 2015 (UTC - 5:00)
    System Uptime: 1 days 1:33:05.076
    Process Uptime: 0 days 0:00:14.000
    Kernel time: 0 days 0:00:00.000
    User time: 0 days 0:00:00.000
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2
    Exception Analysis                
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2
    *** ERROR: Symbol file could not be found. 
    Defaulted to export symbols for aticfx32.dll -
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    *** The OS name list needs to be updated! Unknown Windows version: 6.3 ***
    FAULTING_IP:
    +8afa2
    5458455f ??             
    EXCEPTION_RECORD: 
    ffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 5458455f
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: 5458455f
    Attempt to read from address 5458455f
    DEFAULT_BUCKET_ID: 
    BAD_INSTRUCTION_PTR
    PROCESS_NAME: 
    game.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx".
    The memory could not be "%s".
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx".
    The memory could not be "%s".
    EXCEPTION_PARAMETER1: 
    00000000
    EXCEPTION_PARAMETER2: 
    5458455f
    READ_ADDRESS: 
    5458455f
    FOLLOWUP_IP:
    game+8afa2
    0048afa2 eb12           
    jmp     game+0x8afb6 (0048afb6)
    FAILED_INSTRUCTION_ADDRESS:
    +8afa2
    5458455f ??             
    NTGLOBALFLAG: 
    0
    APPLICATION_VERIFIER_FLAGS: 
    0
    FAULTING_THREAD: 
    00001004
    PRIMARY_PROBLEM_CLASS: 
    BAD_INSTRUCTION_PTR
    BUGCHECK_STR: 
    APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ
    LAST_CONTROL_TRANSFER: 
    from 0048afa2 to 5458455f
    STACK_TEXT: 
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0018f678 0048afa2 00000de1 00000000 000083f3 0x5458455f
    00000000 00000000 00000000 00000000 00000000 game+0x8afa2
    SYMBOL_STACK_INDEX: 
    1
    SYMBOL_NAME: 
    game+8afa2
    FOLLOWUP_NAME: 
    MachineOwner
    MODULE_NAME: game
    IMAGE_NAME: 
    game.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 
    3f329165
    STACK_COMMAND: 
    dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb
    FAILURE_BUCKET_ID: 
    BAD_INSTRUCTION_PTR_c0000005_game.exe!Unknown
    BUCKET_ID: 
    APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ_BAD_IP_game+8afa2
    WATSON_STAGEONE_URL: 
    http://watson.microsoft.com/StageOne/game_exe/0_0_0_0/3f329165/unknown/0_0_0_0/bbbbbbb4/c0000005/5458455f.htm?Retriage=1
    Followup: MachineOwner
    Loaded Module List
    start   
    end        module name
    00400000 00a50000  
    game     game.exe   
    60000000 60028000  
    ijl10    ijl10.dll  
    6f580000 70b0f000  
    atioglxx atioglxx.dll
    72960000 729c0000  
    AudioSes AudioSes.dll
    729c0000 72a13000  
    MMDevAPI MMDevAPI.dll
    72a20000 72b30000  
    aticfx32 aticfx32.dll
    72b30000 72b4c000  
    atigktxx atigktxx.dll
    72b50000 72c29000  
    atiadlxy atiadlxy.dll
    72c30000 72c45000  
    atiglpxx atiglpxx.dll
    72c50000 72c90000  
    powrprof powrprof.dll
    72c90000 72d7c000  
    ddraw    ddraw.dll  
    72d80000 72da5000  
    dinput   dinput.dll 
    72db0000 72e31000  
    dsound   dsound.dll 
    72e40000 72e65000  
    glu32    glu32.dll  
    72ec0000 72f9e000  
    opengl32 opengl32.dll
    73500000 7350a000  
    avrt     avrt.dll   
    73530000 7353f000  
    wtsapi32 wtsapi32.dll
    73540000 73547000  
    dciman32 dciman32.dll
    73680000 736a3000  
    WINMMBASE WINMMBASE.dll
    737c0000 737e3000  
    winmm    winmm.dll  
    73800000 7381b000  
    userenv  userenv.dll
    73d90000 73db1000  
    devobj   devobj.dll 
    73df0000 73f2a000  
    propsys  propsys.dll
    73f30000 74136000  
    comctl32_73f30000 comctl32.dll
    74140000 7415a000  
    dwmapi   dwmapi.dll 
    74160000 7424d000  
    uxtheme  uxtheme.dll
    74250000 742d9000  
    comctl32 comctl32.dll
    74850000 74858000  
    winnsi   winnsi.dll 
    74890000 748b0000  
    IPHLPAPI IPHLPAPI.DLL
    74b10000 74b18000  
    version  version.dll
    74c70000 74c7f000  
    profapi  profapi.dll
    74c80000 74d0b000  
    SHCore   SHCore.dll 
    74d80000 74d89000  
    kernel_appcore kernel.appcore.dll
    74e40000 74e94000  
    bcryptPrimitives bcryptPrimitives.dll
    74ea0000 74eaa000  
    CRYPTBASE CRYPTBASE.dll
    74eb0000 74ece000  
    sspicli  sspicli.dll
    74f30000 74f3e000  
    msasn1   msasn1.dll 
    74f40000 74f7c000  
    cfgmgr32 cfgmgr32.dll
    74f90000 7509e000  
    gdi32    gdi32.dll  
    750a0000 751f3000  
    user32   user32.dll 
    75200000 7527c000  
    advapi32 advapi32.dll
    75280000 75315000  
    oleaut32 oleaut32.dll
    75320000 753e3000  
    msvcrt   msvcrt.dll 
    753f0000 75431000  
    sechost  sechost.dll
    75440000 755bd000  
    combase  combase.dll
    75620000 75733000  
    msctf    msctf.dll  
    75740000 758c8000  
    crypt32  crypt32.dll
    758d0000 7590d000  
    wintrust wintrust.dll
    75910000 7599d000  
    clbcatq  clbcatq.dll
    759a0000 75ae0000  
    kernel32 kernel32.dll
    75b00000 76dac000  
    shell32  shell32.dll
    76e40000 76e47000  
    nsi      nsi.dll    
    76e50000 76e95000  
    shlwapi  shlwapi.dll
    76ea0000 76f5a000  
    rpcrt4   rpcrt4.dll 
    76f60000 77088000  
    ole32    ole32.dll  
    77090000 77096000  
    psapi    psapi.dll  
    770a0000 77177000  
    KERNELBASE KERNELBASE.dll
    77180000 771d0000  
    ws2_32   ws2_32.dll 
    771d0000 7726b000  
    comdlg32 comdlg32.dll
    773f0000 775a1000  
    setupapi setupapi.dll
    775b0000 775d7000  
    imm32    imm32.dll  
    776b0000 7781e000  
    ntdll    ntdll.dll  
    Unloaded modules:
    72b30000 72b4c000  
    atigktxx.dll
    Any help would be appreciated,
    Pawel

    PT
    Metropolis software was shut down in 2009 and there is no further support or development for the products.  Since their shutdown is prior to win 8 it cannot be compatible.  Read about it here http://www.giantbomb.com/metropolis-software-house/3010-107/
    The only thing I can suggest for you is to try re-installing the game in compatibility mode.
    To install in compatibility mode do the following:
    Right click the installer>properties>compatibility>choose OS
    http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1
    (works in vista, win 7, win 8, and win 10)
    Wanikiya and Dyami--Team Zigzag

  • Upgrade Dump analysis

    Hi Gurus
    Here is a list of our system dumps in September and October. I would like if any of you would analyze these for any trends or differences.
    The reason is that we upgraded from BW 3.1 to 3.5 by the end of September. We need to know if this has lead to a signifiacant change in the types of dumps we are receiving.
    <b>Pre Upgrade</b>     
      <b>Runtime error     Count</b>
    MESSAGE_TYPE_X     214
    DYNPRO_SEND_IN_BACKGROUND     43
    STORAGE_PARAMETERS_WRONG_SET     41
    CALL_FUNCTION_SEND_ERROR     29
    UNCAUGHT_EXCEPTION     17
    START_CALL_SICK     14
    TIME_OUT     12
    RAISE_EXCEPTION     9
    TYPELOAD_LOST     8
    CALL_FUNCTION_OPEN_ERROR     7
    DBIF_RSQL_INVALID_RSQL     5
    DBIF_RSQL_SQL_ERROR     5
    RFC_ATTACH_GUI_FAILED     4
    IMPORT_FORMAT_ERROR     4
    DBIF_DSQL2_SQL_ERROR     4
    DBIF_SETG_SQL_ERROR     4
    LOAD_PROGRAM_LOST     4
    TSV_TNEW_PAGE_ALLOC_FAILED     4
    RABAX_CALLING_RABAX     3
    DBIF_REPO_SQL_ERROR     2
    SYSTEM_CORE_DUMPED     2
    OBJECTS_OBJREF_NOT_ASSIGNED     2
    CONNE_IMPORT_ILL_OBJECT_TYPE     1
    ITAB_DUPLICATE_KEY     1
    SAPSQL_INVALID_TABLENAME     1
    DBIF_RTAB_SQL_ERROR     1
    DBIF_DSQL2_OBJ_UNKNOWN     1
    SAPSQL_ARRAY_INSERT_DUPREC     1
    GETWA_NOT_ASSIGNED     1
    <b>Post Upgrade     </b>
    <b>Name of runtime error     Count</b>
    MESSAGE_TYPE_X     211
    DBIF_RSQL_SQL_ERROR     16
    STORAGE_PARAMETERS_WRONG_SET     11
    OBJECTS_OBJREF_NOT_ASSIGNED     10
    CALL_FUNCTION_SEND_ERROR     9
    SYNTAX_ERROR     9
    TIME_OUT     8
    TSV_TNEW_PAGE_ALLOC_FAILED     6
    TYPELOAD_LOST     5
    CALL_FUNCTION_OPEN_ERROR     5
    IMPORT_FORMAT_ERROR     5
    SYSTEM_CORE_DUMPED     4
    DBIF_RSQL_INVALID_RSQL     3
    LOAD_PROGRAM_LOST     3
    UNCAUGHT_EXCEPTION     3
    SAPSQL_CURSOR_ALREADY_OPEN     3
    RAISE_EXCEPTION     2
    CALL_FUNCTION_NOT_FOUND     2
    CALL_FUNCTION_NO_DEST     2
    DBIF_SETG_SQL_ERROR     2
    RFC_ATTACH_GUI_FAILED     2
    ITAB_DUPLICATE_KEY     1
    SAPSQL_INVALID_TABLENAME     1
    CALL_FUNCTION_ACCEPT_FAILED     1
    CONNE_IMPORT_ILL_OBJECT_TYPE     1
    SAPSQL_INVALID_FIELDNAME     1
    TYPELOAD_NEW_VERSION     1
    SYSTEM_CANCELED     1

    Hi Jeevi,
    You can check Dump using ST22 transaction. Dump analysis is nothing but the analysis as what was the cause of dump, what went on the worng in the program which resulted in dump and such questions and getting there answers.
    Reward points if useful.
    Regards,
    Atish

  • ST22 Dump Analysis

    How to use ST22 to analyse dump analysis in a ABAP program ?

    Hi
    You can use the function module SUBST_LIST_ABAP_DUMP to get the complete text of the dump and you can use the function module TCC_SHORTDUMP_INFO to get all the short dumps within a date range.
    SUBST_LIST_ABAP_DUMP - Get the complete text of the dump
    TCC_SHORTDUMP_INFO - Get all the short dumps within a date range
    RS_ST22_GET_DUMPS
    RS_ST22_GET_DUMPS
    to get the dump results.
    other related fun modules are:
    RS_ST22_GET_DUMPS_CATEGORIES
    RS_ST22_GET_DUMP_CATEGORY
    RS_ST22_GET_DUMP_CATEGORY_TEXT
    Regards
    Vasu

  • About dump analysis

    hi guru
    please tell me procedure of dump analysis.
    how as a programmer i will achieve this.
    regards.
    subhasis

    Hi,
    Goto ST22, select dump u want there u will find lot of informatiuon like error descripton, analysis, what to do, memory map and so on with code line where error is there .
    u can go to directily on line where dump is given.
    u can check analysis why error occured so u will be clear to recify it.
    if u want u can check memory status at run time .
    Hope this iwll help u.
    Jogdand M B

  • ST 22 dump analysis

    Hi, In ST22 dump analysis, we are getting the following columns...
    Date, Time, Host, User,Client, Error ID....Is there any way to get also the program name (which is usually available on double clicking any row) in it...
    Because dump analysis report if needed to do program wise it is very difficult to do so....

    Hi Soumen,
    the reportname is already available in the dump overview.
    You can see the information, if you scroll the alv to the right end. If you don't see the column 'Reportname', then you have to adjust the layout of the alv with the layout button. There you have also the possibility to rearrange the sequence of the columns and/or to (un-)hide several columns, which are unnecessary for you.
    Save your changes as user-specified layout.
    Greetings
    Joerg

  • Data_offset_too_large , why this error occurs in dump analysis

    HI,
    when i tried to execute the report it gives the dump analysis as DATA_OFFSET_TOO_LARGE, on which occasion it gives the erros

    Hi,
    Kindly check the error dump using <b>ST22 - Runtime error analysis</b>.
    In error report look for the followings:
    <b>Error analysis:</b> This gives the reason for the error.
    <b>How to correct the error:</b> Here you can find the recommended solution for the error.
    <b>Source Code Extract:</b> Here you can find the source code in which the error has occured.
    In the source code, kindly look for the <b>">>>>>"</b> mark against the line number.
    The error has occured only at that line of the source code.
    In your case, the error might have occured while assigning a variable of larger size
    to a variable of size relatively smaller than that.
    Best regards,
    Thangesh

  • Dump by 0Orgunit_ATTR in TCode RSA3 in ECC/ F4 selection for ORGEH missing

    Hi Gurus,
    i am facing a problem by executing 0Orgunit_attr in the quality system. In D System vevry thing is ok.
    By executing the 0Orgunit_ATTR extractor in RSA3 in ECC, i had a dump.
    The Error is as follow:
    Runtime Errors ITAB_DUPLICATE_KEY
    Date and Time 14/01/2011 11:10:12
    Short dump has not been completely stored
    Short text
    A row with the same key already exists.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLRSAODS" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis
    An entry was to be entered into the table
    "\FUNCTION=RSAR_ODS_GET\DATA=L_TH_ISOSMAP" (which should have
    had a unique table key (UNIQUE KEY)).
    However, there already existed a line with an identical key.
    The insert-operation could have occurred as a result of an INSERT- or
    MOVE command, or in conjunction with a SELECT ... INTO.
    The statement "INSERT INITIAL LINE ..." cannot be used to insert several
    initial lines into a table with a unique key.
    After some researches by SDN i proceed as follow:
    1.I used program: RSAR_RSISOSMAP_REPAIR in SE38 to identify the objects. But no object were found.
    2.I checked table RSISOSMAP in SE16. It was empty.
    I noticed that in the extractor checker the selection button for ORGEH is missing. That means i can not use F4 to select and organizational Unit.
    Could you please help?
    Man Thanks in advance
    Gilo

    resolved with help of basis team

  • Billing output dump analysis

    Hi,
    While taking print out of the invoice correction billing type, system is giving dump.
    The dump error analysis displayed following message-
    " In the current programme "ABCDE123", an arethmetic operation ('divide','/','div',or 'mod') with a type P operand attemptde to divide by 0."
    What does this mean and how this error can be removed?
    Pls. guide.
    Points will be rewarded.
    Regards

    hi
    if you feel this answer solve your query please reward with points
    You can solve this through the transaction code st22 and analyse the error with your abaper fix the solution
    thanks & Regards
    Rack29

Maybe you are looking for

  • Deleting pages

    How do I delete select pages from a multipage PDF in Reader DC?

  • ICal colors on my Intel iMac

    I bought a new iMac a few months ago. I am running Tiger. Since i bought the iMac, i have been having periodic trouble with the colors in iCal. Every so often, i will open iCal (or another application will open it for me) and it will be completely bl

  • JSON from WCF

    Trying to create my first WCF application using Win7 / Visual Studio Express 2013, and IIS Express. Want to dump data as JSON, but run into problems 'out of the gate'. Added a new service function; [OperationContract]         [WebInvoke(Method = "GET

  • Upgrade from CS4 to CS5 extended

    bought a CS5 extended to upgrade my CS4 ext. I have all the serial numbers but canot recall the procedure. I did reinstall the CS4 on my new 64 bit Windows 7 but now what.?I do not have the CS5 ext discs I think I did a digital download. Thanks, earl

  • [SOLVED] About the registration page...

    okay to make this shorter ive registered here using the answer of this guy http://answers.yahoo.com/question/index - 504AAO187t im so interested in arch linux that's why searched for the answer and i found one. lol. a to that captcha. im running back