Runtime Error "TYPELOAD_NEW_VERSION" occuring in ST22

Hi,
We have been reporting a Runtime Error "TYPELOAD_NEW_VERSION" for a few days now. It appears when we check in ST22.
The Error is as below :
Error analysis
    The data type "ZBSTC0000WMXKNJ" was loaded from the database during the program
     run.
    However, a type of a newer version than the one requried was found here.
Please give me some idea about the cause of this error. Any solutions?

Check this thread which discuss the same error :
Re: TYPELOAD_NEW_VERSION - Error
Mathews

Similar Messages

  • ABAP runtime errors TYPELOAD_NEW_VERSI ON   (SAPM/SAINT UPDATE)

    Hi ,All
    I am using SAP4.6c with Orcle8i database on aWindows 2k Adv server. I have imported SPAM (KD00050.CAR) but after imporiting I am unable to use SPAM/SAINT Transaction code and its showing ABAP runtime error like
    "ABAP runtime errors TYPELOAD_NEW_VERSION
    Data type "PAT03" was found i n a newer version than required.
    Runtime Error
    of the statement s could not be executed at runtime.
    The current ABAP program"SAPLSPAM" had t o be terminated because one
    of the statements could not be executed at runtime.

    Hello Jhony,
    http://help.sap.com/saphelp_nw04/helpdata/en/d7/56e89a884b11d2b422006094b9ea64/content.htm
    Regards
    ismail KARAYAKA

  • Abap runtime error UNICODE_TYPES_NOT_CONVERTIBLE occured

    Hi,ecpert:
    I have encountered one abap runtime error UNICODE_TYPES_NOT_CONVERTIBLE
    and the main logic list below:
    First, I define one parameter which user can input from selection screen.
    PARAMETERS:P_TABNAM LIKE DD03L-TABNAME .
    Then, I get the dynamic internal table based on P_TABNAM .
    CALL METHOD cl_alv_table_create=>create_dynamic_table
                   EXPORTING
                      it_fieldcatalog = ifc
                   IMPORTING
                      ep_table        = dy_table.
      ASSIGN dy_table->* TO <dyn_table> .
    Then, after filling data to <dyn_table>, I want to modify the (P_TABNAM).
    MODIFY (P_TABNAM) from TABLE <dyn_table>.
    And when I run this program , one runtime error UNICODE_TYPES_NOT_CONVERTIBLE occurred.
    Pls give suggestions, thanks.

    Quite appreciate your help, I tried this T-code
    however, I got no information after run it with my program name
    In addition, this program can be activated properly in ABAP editor,and error occured
    when execute the 'Modify' clause.

  • Get a popup an exception runtime error has occurred in script unable to jit debug

    i get a pop up window, just-in-time debugging
    An exception 'runtime error' has occurred in script.
    However, no debuggers are registered that can debug this exception. Unable to JIT debug.

    '''I think I solved it myself yesterday, indirectly''' by deleting a Googleupdater.exe file dated 042511. It has been over 24 hours now and no sign of the 'Just-In-Time Debugger' pop-up. Whew...it was incessant.
    Not sure how I got the Googleupdater.exe file on my computer. I did download Microsoft Security Essentials to help find the JIT problem, but it failed to install properly and run. The next day I remembered it probably only runs on Internet Explorer (which we deleted in 2009) after testing out Firefox. I then also deleted Security Essentials.
    I also downloaded on April 25th the free version of MS Visual Basics because I read on eHow that you can adjust settings in the 'TOOL' menu to stop JIT Debugging pop-ups. However, the free version was 'MS Visual Studio Basic 2008 Express Edition - SP1' which did NOT provide access to JIT Debugging settings (so it was not a solution).
    I must say I switched Internet Security programs to AVAST! on TU | Apr26th and love it so far. Highly recommend looking into AVAST! ver 6.0 at CNET downloads - free. The anti-virus program is free, but everything else costs about $30US for a year. WORTH IT Love the options | settings | flexibility|user friendly windows.
    Trend Micro was then deleted. It had always blocked usage of our internal CD|DVD drive. To use the CD|DVD drive we had to shut off Trend Micro and then turn it back on again after we finished using the CD|DVD drive. NOT a preference - for sure. Jaykay

  • A Runtime Error Has Occured Do you wish to Debug? Line 90 Error: Object Expected

    A Runtime Error Has Occured Do you wish to Debug? Line 90
    Error: Object Expected
    This error is recieved when trying to open "The Fan" video
    news Page from Comcast, This error appears and when you select yes
    or no, the page comes up to install Adobe Flash Player, however
    even after installing it, the error still appears when attempting
    again, even after restart, this does not occur on Firefox, only
    IE

    Also I am on Windows Vista

  • Error: "A runtime error has occurred."

    I am receiving the following error after installing SP3 on crystal XI release2
    A runtime error has occurred.
    Do you wish to Debug?
    Line: 515
    Error: Object Expected
    Any Ideas?

    The following SAP note would help you
    [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do]
    Regards,
    Raghavendra

  • Runtime errors "Raise_Exception" occur when running crystal report

    Dear all expert,
    I had develop a CR. It is fine and I can run it. but in our remote system, there is a runtime error "RAISE_EXCEPTION" with exception condition "EXECUTION_HALTED". There is no error show to me at CR side where the report is running fine. But I wonder why the is a runtime error in the remote system.
    Thank You.

    Hi Ingo,
    I had check the transport folder in my integration solution installer kit folder. There is only Folder with name "ansi" and "unicode_compatible".
    The readme for my transport file are as below:
    There are two sets of transport files, which can be used with BusinessObjects Enterprise Integration Kit for SAP. One set is ANSI and the other set is Unicode enabled.
    The set of transports you must use depends on the BASIS system your SAP system is running on. Additionally, each transport consists of a data file and a cofile, which are listed in brackets behind the transport names.
    If your SAP system is running on a BASIS system earlier than 6.20, you must use the files listed below:
    (These files are ANSI.)
    Open SQL Connectivity transport (K900084.r22 and R900084.r22)
    Info Set Connectivity transport (K900085.r22 and R900085.r22)
    Row-level Security Definition transport (K900086.r22 and R900086.r22)
    Cluster Definition transport (K900093.r22 and R900093.r22)
    Authentication Helpers transport (K900088.r22 and R900088.r22)
    If your SAP system is running on a 6.20 BASIS system or later, you must use the files listed below:
    (These files are Unicode enabled.)
    Open SQL Connectivity transport (K900574.r21 and R900574.r21)
    Info Set Connectivity transport (K900575.r21 and R900575.r21)
    Row-level Security Definition transport (K900576.r21 and R900576.r21)
    Cluster Definition transport (K900585.r21 and R900585.r21)
    Authentication Helpers transport (K900578.r21 and R900578.r21)
    The following files must be used on an SAP BW system:
    (These files are Unicode enabled.)
    Content Administration transport (K900579.r21 and R900579.r21)
    Personalization transport (K900580.r21 and R900580.r21)
    MDX Query Connectivity transport (K900581.r21 and R900581.r21)
    ODS Connectivity transport (K900582.r21 and R900582.r21)
    The dump "raise_exception" occur when in the Crystal Report Designer.
    Thank You.

  • Getting "warning" -- "Late bound resolution, runtime errors could occur" with a line referencing a Word document

    The problem line is:
                Dim Author$ = wd.ActiveDocument.BuiltInDocumentProperties(WdBuiltInProperty.wdPropertyAuthor).value.ToString
    "wd" is my program's instance of Microsoft Word.
    I've encountered this error before and could always fix the program and get rid of the warning without having to enclose the line in a "Try..Catch" structure. I enclosed this line in a Try..Catch, but the warning still appears, and for some reason,
    I have dedicated my few remaining years to getting rid of it.
    Robert Homes

    Armin:
    That didn't work for me. I couldn't even compile it like that, and I changed it to:
    =============================================
            Dim props As Microsoft.Office.Core.DocumentProperties = _
                    DirectCast(wd.ActiveDocument.BuiltInDocumentProperties, _
    Microsoft.Office.Core.DocumentProperties)
            Dim Author$ = props(WdBuiltInProperty.wdPropertyAuthor).Value.ToString
    =============================================
    That at least allowed me to compile (and DID get rid of the warning), but then I got a runtime error:
    ========================================================
    An unhandled exception of type 'System.InvalidCastException' occurred in Share.exe
    Additional information: Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Core.DocumentProperties'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{2DF8D04D-5BFA-101B-BDE5-00AA0044DE52}'
    failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
    ================================================================================
    Robert Homes

  • Runtime error RAISE_EXCEPTION occured

    I have created a session after my LSMW is processed. I am not able to process the session in back ground. When I am trying to process that session in back ground, I am not able to do that. I am getting the errror "Runtime error RAISE_EXCEPTION has occured". But I am able to process that session in the foreground. Kindly suggest me something.

    If the session is ran in back ground, then it is throwing the error for all the records "Runtime error RAISE_EXCEPTION has occured ".

  • ABAP runtime errors    RAISE_EXCEPTION occured

    Hi all,
    I have SAP Material management landscape and user gets short dumps with exception.
    here are the detils.
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLYMQX " in
    "Y_INSERT_TO_YMTOES_INT_DTLS".
    The main program was "YM_DATA_FLEX_TO_DEMAND ".
    The termination occurred in line 73
    of the source code of program "LYMQXU06 " (when calling the editor 730)
    ========
    code extract
    ========
    insert into YMTOES_INT_DTLS values wa.
    if sy-subrc <> 0.
    raise insert_error.
    ==========
    Need help in how to see why this occuring.
    Edited by: Vijay Dhamera on Oct 24, 2008 11:53 AM

    ST22 details as follows
    Error analysis
    A RAISE statement in the program "SAPLYMQX " raised the excep
    condition "INSERT_ERROR".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Short description of exception condition:
    ERROR DURING INSERT
    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.

  • A Runtime Error occured when viewing topics

    Hi,
    I got the following message when I'm trying to view one topic
    with hyperlink :
    "A Runtime Error has occurred. Do you wish to Debug?
    Line 2393
    Error : Access is denied"
    When I click No, the entire topic displayed but the hyperlink
    didn't work.
    When I try to test the same topic in the CHM, the hyperlink
    work well.
    I'm using a lot Ctrl+W to made QA on my conditional topic and
    I will like to solve this problem.
    Can someone may help me?
    Thanks!
    TW_MaryseC

    TW_MaryseC
    It sounds like your topic has some javascript in it, is that
    the case?
    If you are not sure, try this. Create a new topic with the
    same filename except add _new. Keep cutting and pasting bits of the
    content from the problem file and previewing it in the same way you
    are now until the error occurs. Then you will know what to look at
    and be able to resolve it or post back.
    You say "I'm using a lot Ctrl+W to made QA on my conditional
    topic..." Ctrl+W is simply a means of previewing a topic. I think
    what you are saying here is that you then select a condition to
    test the topic is working. But you get the problem before you
    select any condition in the preview so I am not sure what you are
    saying here. Please clarify.
    Avalynn
    Whilst you are getting a runtime error it is a different one
    so it would have been better to create a new post rather than
    hijack this one. It's difficult to answer two people's problems in
    one thread.
    It sounds like you have a javascript function in the body of
    your topic but you do not have anything in the head section to say
    where the javascript file is located. Could that be the case?
    The trial version should allow you to see your topics
    although there is a limit to the number. How many topics do you
    have?
    Also are you generating the CHM file to your hard disk?

  • SQL error 3113 occurred when executing EXEC SQL.

    Hi,
    We are facing one typical problem, One background is failing regularly with
    below dump. as we now got all notes giving information, if database  restarted
    taking backup, these type of failures occur, but our database is only down for backup once in a week, but it is failing with frequenly.
    in this two servers are located in different place, in this job tries to connect
    another server to get material statistics.
    It is giving some error message in sm21 with
    SQL error 3113 occurred when executing EXEC SQL.
    work procees in reconnect mode.
    all notes saying these types of dump occur when database restared, but this dump
    even though database is up.
    below is short dump, please can anyone help me from this problem.
    ABAP runtime errors    DBIF_DSQL2_SQL_ERROR
          Occurred on    08.01.2007 at 00:30:28
    >> Short dump has not been completely stored. It is too big.
    SQL error 3113 occurred when executing EXEC SQL.
    What happened?
    The error occurred in the current database connection "AZ1".
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    How to correct the error
    Database error text........: "ORA-03113: end-of-file on communication channel#"
    Triggering SQL statement...: "select mara.groes, mara.brgew, mara.ntgew,
    mara.gewei, mara.volum, mara.voleh, mara.mstae, mara.mstde, mara.prdha,
    marc.matnr, marc.werks, marc.mmsta, marc.mmstd from sapr3.mara, sapr3.m
    where sapr3.mara.mandt = sapr3.marc.mandt and sapr3.mara.matnr =
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "DBIF_DSQL2_SQL_ERROR"
    "ZM2431216 " or "ZM2431216 "
    "EXTRACT_GENERAL_DATA"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
      To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
      To obtain this, call the system log with Transaction SM21
      and select the "Print" function to print out the relevant
      part.
    3. If the programs are your own programs or modified SAP programs,
      supply the source code.
      To do this, you can either use the "PRINT" command in th
      print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error o
      or which actions and input led to the error.
    System environment
    SAP Release.............. "46C"
    Application server....... "essceu3"
    Network address.......... "172.19.119.198"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C7ADBD4C00"
    Database server.......... "ukblx176"
    Database type............ "ORACLE"
    Database name............ "EU3"
    Database owner........... "SAPR3"
    Character set............ "es_ES.ISO8859-1"
    SAP kernel............... "46D"
    Created on............... "Jul 9 2006 20:26:33"
    Created in............... "AIX 1 5 00447C4A4C00"
    Database version......... "OCI_920__OCI_7_API "
    Patch level.............. "2257"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE
    8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."
    SAP database version..... "46D"
    Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
    5, , System build information:,                                      , LCHN :
    841480"
    User, transaction...
    Client.............. 600
    User................ "MPZMMES"
    Language key........ "S"
    Transaction......... " "
    Program............. "ZM2431216 "
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "ZM2431216 " in
    "EXTRACT_GENERAL_DATA".
    The main program was "ZM2431216 ".
    The termination occurred in line 980
    of the source code of program "ZM2431216 " (when callin
    The program "ZM2431216 " was started as a background jo
    Source code extract
    009500              mara.ntgew,
    009510              mara.gewei,
    009520              mara.volum,
    009530              mara.voleh,
    009540              mara.mstae,
    009550              mara.mstde,
    009560              mara.prdha,
    009570              marc.matnr,
    009580              marc.werks,
    009590              marc.mmsta,
    009600              marc.mmstd
    009610        into :w_ops-groes,
    009620              :w_ops-brgew,
    009630              :w_ops-ntgew,
    009640              :w_ops-gewei,
    009650              :w_ops-volum,
    009660              :w_ops-voleh,
    009670              :w_ops-mstae,
    009680              :w_ops-mstde,
    009690              :w_ops-prdha,
    009700              :w_ops-matnr,
    009710              :w_ops-werks,
    009720              :w_ops-mmsta,
    009730              :w_ops-mmstd
    009740        from sapr3.mara, sapr3.marc
    009750        where sapr3.mara.mandt = sapr3.marc.mandt
    009760          and sapr3.mara.matnr = sapr3.marc.matnr
    009770          and sapr3.mara.mandt = :p_mandt
    009780          and sapr3.mara.matnr = :w_ebs-matnr
    009790          and sapr3.marc.werks = :p_owerks
        >    ENDEXEC.
    009810  endform.                    " extract_general_data
    009820  *&
    009830  *&      Form  append_i_ops
    009840  *&
    009850  *      Appends W_OPS to I_OPS
    009860  *
    009870  form append_i_ops.
    009880    append w_ops to i_ops.
    009890  endform.                    " append_i_ops
    009900  *&
    009910  *&      Form  extract_material_description
    009920  *&
    009930  *      Extracts a Material Description from the remote database an
    009940  *      modifies the current record in I_OPS.
    009950  *
    009960  *        >P_SPRAS  Language Key
    009970  *
    009980  form extract_material_description using    p_spras.
    009990    EXEC sql performing set_langauge.
    Contents of system fields
    SY field contents..................... SY field contents............
    SY-SUBRC 0                            SY-INDEX 0
    SY-TABIX 1                            SY-DBCNT 1
    SY-FDPOS 18                            SY-LSIND 0
    SY-PAGNO 0                            SY-LINNO 1
    SY-COLNO 1
    Chosen variables
    Name.......................... Contents.1........2........3....+..
    W_EBS-PRAT4
                                  2
                                  0
    W_OPS-GROES
                                  22222222222222222222222222222222
                                  00000000000000000000000000000000
    W_OPS-BRGEW                    #######
                                  0000000
                                  000000C
    W_OPS-NTGEW                    #######
                                  0000000
                                  000000C
    regards,
    krishnaiah.

    Hi,
    This is usually a SERVER SIDE DATABASE PROBLEM or SQLNET LISTENER (server side) PROBLEM.  The client side should initially be ignored and instead the server should be investigated. In rare cases, this can be caused by client
    side memory or other resource problem, or a DLL version mismatch, but this is
    unlikely.
    Enlist the assistance of your DBA.  Then reproduce the ORA-3113 error on your
    client application.  Ask your DBA to look at the database side Alert.log and
    trace files and look for ANY activity.  Any activity that coincides with your
    ORA-3113 will be a clue.
    REgards
    Vinod

  • Runtime error while doing FB08

    while doing FB08 the system is creating a dump.
    Runtime errors         SYNTAX_ERROR                                                      
           Occurred on     05.08.2008 at   12:43:14                                                                               
    Syntax error in program "SAPLFMREAS ".                                                                               
    What happened?                                                                               
    The following syntax error occurred in the program SAPLFMREAS :                          
    "The obligatory parameter "C_GSBER" had no value assigned to it."                        
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLFMRI_CORE" had to be terminated because one of             
    the                                                                               
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    What can you do?                                                                               
    Please eliminate the error by performing a syntax check                                  
    (or an extended program check) on the program "SAPLFMREAS ".                             
    You can also perform the syntax check from the ABAP/4 Editor.                            
    If the problem persists, proceed as follows:                                             
    Print out the error message (using the "Print" function)                                 
    and make a note of the actions and input that 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
    The following syntax error was found in the program SAPLFMREAS :
    "The obligatory parameter "C_GSBER" had no value assigned to it."
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.

    Hi,
    Run time error occurs when certain info objects are activated or if the patches for a certain standard program or tcode has to be applied. Please refer to the SAP Notes for the error mentioned by you and apply the related support package for the same. You can co ordinate wiht your Basis as well as Abap consultant to implement the correction.
    Hope this helps
    regards,
    radhika

  • Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred

    When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
    [20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
    In sm21 shows message:
    AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
    AB1 > Short dump "070316 205056 sapnw ELDA " generated
    Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
    We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
    The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
    The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
    When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
    Best Regards,
    Rogério

    Hi Ajith
    I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
    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', was
      neither
    caught nor passed along using a RAISING clause, in the procedure
      "LOG_INSERT_DB" "(FORM)"
    Since the caller of the procedure could not have expected this exception
      to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    Thanks, Raj

  • Runtime error : MESSAGE_TYPE_UNKNOWN

    We hv Solution Manager 3.2 in our scenario. Iam working on the feature Project Preparation ,in the transaction solar_project_admin inorder to create project views when i generate the IMG for logical component in Development system
    iam getting dump MESSAGE_TYPE_UNKNOWN,the detailed error message is as follows:
    <b>
    Runtime errors         MESSAGE_TYPE_UNKNOWN                                                   
           Occurred on     09.02.2007 at   12:44:06                                                                               
    Message type " " is unknown.                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLPROJECT_ADMINISTRATION" had to be terminated                    
    because one of the                                                                           
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                      
    and make a note of the actions and input that 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.                                                                               
    is especially useful if you want to keep a particular message.                                                                               
    Error analysis      
    Only message types A, E, I, W, S and X are allowed.                      
    There is probably an error in the program                                
    "SAPLPROJECT_ADMINISTRATION".                                                                               
    How to correct the error                                                                               
    Probably the only way to eliminate the error is to correct the program.  
    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:                                                                               
    "MESSAGE_TYPE_UNKNOWN" C                                                 
    "SAPLPROJECT_ADMINISTRATION" or "LPROJECT_ADMINISTRATIONU05"             
    "SPROJECT_SEND_MESSAGE"                                                  
    If you cannot solve the problem yourself, please send the                
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                             
       To obtain this, select the "Print" function on the current screen.    
    2. A suitable hardcopy prinout of the system log.                        
       To obtain this, call the system log with Transaction SM21             
       and select the "Print" function to print out the relevant         
    3. If the programs are your own programs or modified SAP programs,          
    supply the source code.                                                  
    To do this, you can either use the "PRINT" command in the editor or      
    print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred          
    or which actions and input led to the error.                                                                               
    </b>          
    Can somebody plz help me out with resolving this issue,how to tasolve it? My Email Id is [email protected]  .Requested to revert at earliest
    Regards,
    Saumya

    Hello,
    Iam using SAP GUI latest release 6.40 and latest patch level 20.Plz suggest the solution to this problem?
    Regards,
    Saumya

Maybe you are looking for