QUEUE_NOT_EMPTY Error in SPAM

Hello,
I am doing a test run to import BASIS pkg level 10 but geting error
Error in phase: CHECK_REQUIREMENTS
Reason for error: QUEUE_NOT_EMPTY
How to resolve it?? Actually eralier i was importing ADD-ons via SAINT which went in error so i hav deleted it and starting it again.
pls help
Thanks,
Ankita

Hi,
In Se37,Use the function module OCS_RESET_QUEUE -> Single Test
with the parameters
IV_TOOL=SPAM, IV_FORCE=X
Deleted all the files from \usr\sap\trans\tmp.Please make sure thatthere is no TP process
or R3trans process running in the system at Operating system level.
If any process exist, Please kill the process.
Scheduled the program RDDIMPDP using Report RDDNEWPP in se38.
PS:Better Contact SAP to Reset the Queues in The Live Systems as this may cause inconsistencies in the system.
Regards
Ram

Similar Messages

  • Check_Requirement &Queue_Not_Empty error in SPAM

    Hi Experts, I'm strucked at the middle stage of support packages applying in solution manager. below patches are in the spam queue Abap-16,Basis-16,BW-17 ST-427 and KU50012. I have downloaded proper files and extracted into EPS/in. still i'm getting queue_not_empty error during the patching. trans log is showing as listed below.
    Directory:  /usr/sap/trans/log
    Name:       SLOG0939.SMP
    ERROR: SAPKU50012 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    HALT 20090922183306
    ERROR: tpsettainfo: /usr/sap/trans/cofiles/KU50012.SAP contains no valid information
    ERROR: EXIT(16) -> process ID is: 733188
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    ERROR: SAPKA70016 : couldn't locate TA-info in .../cofiles
    (illegal format detected)
    2. I have executed > tp showbuffer SMP tag=spam pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL
    This is tp version 372.04.40 (release 700, unicode enabled)
    SMP buffer:
    SMXK900045          |                    | |will not be imported because it is n
    ot tagged.
    TASK                |PROJECT             |P|CMD Im|DD Im |DD Act|MainIm|Enq.Ac|A
    DO Im|VersFl|Deploy|XPRA  |Gener |UMODE|TAGS
    ---------------+--+--+----+-
    ----------+--+--+-+--
    SAPKB70016          |                    | |1     |1200  |1200  |1     |2     |
    7586
    1719
    3674
    1
    D
    SAPKW70017
    1
    242
    242
    1
    7
         |4112  |      |553   |2895  |1    |D
    that makes 2 transports to be imported.
    tp finished with return code: 0
    meaning:
      Everything OK
    3.I have tried to clean buffer via dangerous function module OCS_RESET_QUEUE but still problem persists.. Env: AIX/DB2/Kernel-185-700_Unicode/tp:372.04.40/spam:35 and stms configuration is fine/RFC's are also fine.
    Please provide me your advice to finish task successfully.
    thanks-Nani

    Hi Ashok,
    Thanks for your advice. I had deleted those files from the directory 'cofiles and data' and deleted those  .ATT and .PAT files from EPS/in also even though SPAM was showing those patches in "new patches  list'.How it is possible? I have deleted those files from PAT01,PAT03 and TEPSIN tables.
    anyway now am downloading again those patch files into server 'EPS/in'  to upload files from the option 'frontend'
    Thanks.
    Nani

  • Tp error during spam update

    Hi,
    I got an error during spam update. The version is ECC 6.0. It got terminated during the phase IMPORT_OBJECT_LIST. how it can rectified.
    Pls help me in resolving the issue.
    Regards,
    Kris

    Hi,
    ERROR: No connect due to DbSl Load Lib Failure
    ERROR: environment variable DIR_LIBRARY is not set.
    ERROR: Connect to DEV failed (20071118181034).
    This is the error i got when i checked the tp log
    can any one suggest a resolution?
    Regards,
    Kris

  • Error in spam/saint update TP_CANNOT_CONNECT_SYSTEM TP_INTERFACE_FAILURE

    Dear All,
    while i am updating spam / saint in saint t code I am facing an error TP_INTERFACE_FAILURE and reason for the error is TP_CANNOT_CONNECT_SYSTEM
    the error details are
    The installation was stopped, since an error occurred during the phase
    CHECK_REQUIREMENTS, which the Add-On Installation Tool is unable to
    resolve without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Continue in the queue display.
    The following details help you to analyze the problem:
        -   Error in phase: CHECK_REQUIREMENTS
        -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
        -   Return code:
        -   Error message: TP_INTERFACE_FAILURE
    Notes on phase CHECK_REQUIREMENTS
    n this phase the system checks the various requirements for the add
    nstallation. The following are reasons why this phase may fail:
       TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log on to the system
       database.
       Check the action log (in the menu, choose Goto -> Action Log). Y
       may be able to use the detailed tp error message in this log to
       identify and remove the cause of the error.
       QUEUE_NOT_EMPTY: There are still OCS requests in the transport
       buffer which are not completed. You can show these requests with
       following tp command:
       tp SHOWBUFFER <SID> -DSOURCESYSTEMS= TAG=SPAM
       These requests have to be completed or deleted from the buffer
       before you can continue importing the queue.
    o   CANNOT_DROPBUFFER: tp cannot delete old, incompletely processed
         Support Packages from the tp buffer.
         Check the action log (in the menu, choose Goto -> Action Log). You
         may be able to use the detailed tp error message in this log to
         identify and remove the cause of the error.
    The Add-On Installation Tool requires that the Change and Transport
    System (CTS) be configured correctly. For more detailed information,
    read the online documentation available from Help -> SAP Library ->
    mySAP Technology Components -> SAP Web Application Server -> BC Change
    and Transport System .
    A list of the most important SAP Notes for Online Correction Support
    (OCS) is available in SAP Note 97620, which is updated regularly.
    please help me, its very important to complete this job i am in a critical position
    Thanks
    Senthil

    Dear,
    Please refer these links,
    tp_cannot_connect_system
    Problem loading a package in the SAINT transc. (TP_CANNOT_CONNECT_SYSTEM)
    Regards,
    R.Brahmankar

  • Queue_not_empty error while applying patch

    I am getting the following error message while applying SEM patch on IDES BW3.5/SEM 4.0  on Windows 2003 server and having Oracle 9i as database
    Error in phase : Check_Requirement
    Reason for error : Queue_Not_Empty
    Please resolve this issue as I require to apply the patch urgently .

    Hello Sunil,
    CHECK_REQUIREMENTS
    This phase checks various requirements for importing a Support Package. It may terminate for the following reasons:
    &#9675;       TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log on to the database of the system.
    &#9675;       QUEUE_NOT_EMPTY: The tp buffer contains incompletely processed OCS requests.
    Use the following tp command to display these requests:
         tp SHOWBUFFER <SID> -D SOURCESYSTEMS= TAG=SPAM
    You can only continue to import the queue after these requests have been completely processed, or deleted from the tp buffer
    Not recommended but to clear the queue:
    Tables PAT01 and PAT03 stores the support package list and its phase respectivily. You can delete table contents for PAT03 using DB procedures
    Regards,
    Ammey Kesarkar
    <i>'Award points for useful info'</i>
    NB: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/7e/c6c2ad98a711d2b429006094b9ea64/content.htm">Errors During Support Package Manager Phases</a>

  • Error in Spam / saint update TP_STEP_FAILURE and DDIC_ACTIVATION

    Dear All,
    While updating spam/ saint update I am facing  this error 
    Details of Error:
    The installation was stopped, since an error occurred during the phase
    DDIC_ACTIVATION, which the Add-On Installation Tool is unable to resolve
    without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Continue in the queue display.
    The following details help you to analyze the problem:
        -   Error in phase: DDIC_ACTIVATION
        -   Reason for error: TP_STEP_FAILURE
        -   Return code: 0008
        -   Error message:  tp step A, return code
            0008
    Notes on phase DDIC_ACTIVATION
    In this phase the system activates the imported Data Dictionary objects.
    This phase may terminate for several reasons:
    o   TP_INTERFACE_FAILURE: The system was unable to call the tp
         interface.
    o   TP_FAILURE: The system was unable to execute the tp program. For
         more information, see the SLOG or ALOG log file.
    o   TP_STEP_FAILURE: The system was unable to perform the tp step DDIC
        activation successfully. To see the cause of the problem in the
        activation log, choose Logs.
        If you import two or more OCS packages in one installation queue,
        and activate the Data Dictionary objects in the incorrect sequence,
        this can cause errors. In this case, the activation errors disappear
        if you repeat the activation run. To do this, choose Continue.
    The Add-On Installation Tool requires that the Change and Transport
    System (CTS) be configured correctly. For more detailed information,
    read the online documentation available from Help -> SAP Library ->
    mySAP Technology Components -> SAP Web Application Server -> BC Change
    and Transport System .
    A list of the most important SAP Notes for Online Correction Support
    (OCS) is available in SAP Note 97620, which is updated regularly.
    Please  help me
    Thanks
    Senthil

    Hi,
    i am having the same problem with SPAM
    Error in phase: DDIC_ACTIVATION                                                                               
    Reason for error: TP_STEP_FAILURE                                                                               
    Return code: 0008                                                                               
    Error message: OCS Package SAPKA70012, tp step A, return code
    0008  
    however i dont have the option to continue..  Please help
    thanks

  • Support Pack error in SPAM

    Hi
    I am importing a group of Support Packs into our DEV environment to bring the landscape uptodate, we are running NW04 on Windows 2003 64 bit & SQL Server 2000, I've updated to the latest SPAM and Kernel before the Support Packs.
    When importing in SPAM I have used the calculate queue method, all looks ok, when I perform the import, in the phase TEST IMPORT i get the following error for Support Pack SP 12 for EA-FINSERV 5.00 :
    <b>
    Function MAP2I_BAPICMS_STR_MOV_INS_CRT (CMS_BUSISB104_MAPPI does not fit into the existing function group ((CMS_BUSISB10)</b>
    The only option I am given is to repeat the phase, I've repeated this a few times and get the same error on TEST IMPORT. I'm new to NW04 640 BASIS, but I know from running 4.6X system that you can re-run phases and quite often they work correctly 2nd time round, is it worth changing SPAM to not stop on test import errors ? as I know objects required can be in earlier support packs (i'm applying supports pack EA-FINSERV 5.00 08 to 11 as part of the queue before 12 which is giving me the error.
    I've checked on OSS and cannot find any notes on this error/support pack.
    Thanks.

    nope, not tried with ignore test errors yet, wanted to check opinions here to see if thats the next step to try, or if there's anything else I could try ?

  • SAP_BASIS IMPORT_PROPER Error during SPAM for CRM Upgrade

    Hi All,
    During SPAM IMPORT_PROPER for component SAP_BASIS, encountered error. Checking the Import Logs of the queue, we see error logs in Activate inactive runtime objects. Sample message below.
    May we ask how to fix the error for us to be able to continue the upgrade? Thanks.
       Activation of sample nametabs with appended fields
       06:17:30: Retcode 512: error in DDL statement for ALCCMCUSTP                     - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of ALCCMCUSTP
       06:17:42: Retcode 512: error in DDL statement for ALCCMCUSTV                     - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of ALCCMCUSTV
       06:17:55: Retcode 512: error in DDL statement for ARC_DESTR_VETO                 - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of ARC_DESTR_VETO
       06:18:07: Retcode 512: error in DDL statement for DB6_OPTPROFILE                 - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of DB6_OPTPROFILE
       06:18:19: Retcode 512: error in DDL statement for FDT_TRACE_0200                 - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of FDT_TRACE_0200
       06:18:31: Retcode 512: error in DDL statement for FDT_TRACE_0201                 - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of FDT_TRACE_0201
       06:18:43: Retcode 512: error in DDL statement for GE071KF_OLD_NT                 - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of GE071KF_OLD_NT
       06:18:55: Retcode 512: error in DDL statement for GTABKEYEXC20                   - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of GTABKEYEXC20
       06:19:07: Retcode 512: error in DDL statement for GTABKEY_CASCADE                - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of GTABKEY_CASCADE
       06:19:19: Retcode 512: error in DDL statement for GTABKEY_COMPEXCL               - repea
       t
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of GTABKEY_COMPEXCL
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of GTABKEY_COMPSETS
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of GTABKEY_C_SYS
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of GTABKEY_EXT
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLS
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of IACXU
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLS
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of IACXUT
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLS
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of IACXU_C1
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of IACXU_C_TEMP
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of STORE_HELP
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of STORE_LINK_IND
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of SWWOUTBOX
       Error -204-SQL0204N when executing ADD-FIELD of  is an undefined name.  SQLSTA
       Error  in DDL statement for when executing ADD-FIELD of
               (dummy, do not translate)
       No DDL commands found for activation of SWWWITEXT
               21 shadow nametab activations resulted in errors
       Begin:  Activation of shadow nametabs with DDL (2014/03/19 06:17:30)
       End:    Activation of shadow nametabs with DDL (2014/03/19 06:19:31)
       Begin:  Activation of shadow nametabs with DDL (2014/03/19 06:19:31)
               (dummy, do not translate)
    Regards,
    Philip

    Hi Philip,
    Could you please check the below SAP Note. It is a composite notes which has listing of various errors during upgrade
    822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
    Hope this will be useful
    Thanks and Regards
    DJ

  • Error Applying SPAM

    Hi Guys,
    Really need someone help on this, I try to apply the ABAP Support pack but got this error :
    Import phase 'DISASSEMBLE' (28.11.2007, 13:44:30)
    Disassemble OCS package SAPKA70009
    Create data file
    PMBIPSMS01\sapmnt\trans\data\RA70009.SAP
    Unknown OCS file format 'ii' in OCS Package SAPKA70009; SPAM/SAINT Update required
    Error during disassembling the EPS parcel of OCS Package SAPKA70009: 'PATCH_FILE_ERROR'
    Interrupt the import due to an error situation (28.11.2007, 13:44:38)
    Display detailed informations concerning the error in phase 'DISASSEMBLE'
    Abort the import due to an error situation (28.11.2007, 13:44:46)
    What is it means? I've tried dloading the new one but it still the same..pls points will be given.
    TQ.

    Hi,
    re-download support pack and try again.
    Hope this solves your problem.
    Feel free to revert back.
    --Ragu

  • Error updating SPAM

    Hi,
    Updating SPAM to patch SAPKD64036 I get the error message:
    Retcode 1: error in DDL statement for  VE071LOCKFLAG                         - repeat
    Error 1031-ORA-01031: insufficient privileges when executing ADD-FIELD of             
    Error  VE071LOCKFLAG when executing ADD-FIELD of                                       
            (dummy, do not translate)                                                     
    No DDL commands found for activation of VE071LOCKFLAG
    Any idea?
    Regards.

    Hi,
    Please let us know which version of oracle you are running. Assuming it
    is 10, please review the following notes :
    - 1028220 -  ORA-01031: Insufficient privileges despite SAPCONN role
    - 985607  -  ORA-01031 Creating views after upgrade to Oracle 10g;
    It is probable that the database user does not have required privileges.
    After executing SAPCONN_ROLE.SQL, restart the SAP system. Otherwise, the
    connected WP still will use the old authorizations.
    After you try the above, continue the SPAM import again.
    Aidan

  • SPAM ERROR WITH CHECK_REQUIREMENTS-QUEUE_NOT_EMPTY

    hi friends, i have applied sapke60028 in dev,qly suceessfully. when iam trying to apply same patch in prd iam getting queue_not_empty error. i have checked tp and rfc connections ...everything is fine. how can i solve this error? plz give your adivce.my platform is db2/aix.(spam version 700/026)
    thanks-nani

    Hai,
    Please try the follwoing:
    in Se37,Use the function module OCS_RESET_QUEUE --- >execute --->IV_TOOL=SPAM, IV_FORCE=X
    Deleted all the files from \usr\sap\trans\tmp..
    Please make sure thatthere is no TP process
    or R3trans process running in the system at Operating system level.
    If any process exist, Please kill the process.
    Regards,
    Yoganand.V

  • SPAM/SAINT error/completion flag?

    Good afternoon,
    My company is currently going through an upgrade in a sandbox system to get to EHP3.  During every upgrade it seems we will run into an error and we have to monitor the system often to see if the upgrade has stopped or if it has completed.
    Is there a standard table or flag set in SAP when SPAM or SAINT is run that could be monitored?  I could write a program to run in the background every 15 minutes to monitor this table entry or flag and e-mail the "Basis" team if an error occurs or if it's completed.  This would save our team from having to constantly monitor issues.
    If anyone has any suggestions I'd appreciate it.  If someone finds something and I can write an ABAP program to get it to work I'm willing to post it here for everyone else to use too.
    Thanks,
      Jonathan

    Thanks to all for your suggestions.  I was able to write the program and it actually work for us during our testing. 
    I wasn't able to upload to the code snippet section so I'm going to try to cut and paste in multiple sections here by using the "<code>" display as code option.  If I add too many line items it just runs together and is unusable.
    Feel free to use and modify for your own purposes.
    PART 1 of code
    *& Report  ZBAS_SUPPORT_PACK_CHECK
    *& Purpose: To monitor the SPAM and SAINT transactions during an upgrade
    *&          for any errors.  SPAM and SAINT often run into errors that
    *&          need to be reviewed before the upgrade can continue.  This
    *&          program will e-mail employees in case any error messages are
    *&          found.
    *&          Create a batch job to run every 10 minutes during the
    *&          upgrade process
    *& History: Initial Creation - 09/10/09 - Jonathan Kullgren
    REPORT  ZBAS_SUPPORT_PACK_CHECK.
    constants:
          c_yes     type c length 1 value 'X'.
    data: zpat like patlog3 occurs 0 with header line.
    data: l_log_name like patlog3-log_name,
          l_curdate like patlog3-curdate,
          l_curtime like patlog3-curtime.
    data: l_flag type c.
    * Definitions for emailing
    data: itab_text type table of tline with header line,
          itab_objpack type table of sopcklsti1 with header line,
          itab_objtxt type table of solisti1 with header line,
          itab_reclist type table of somlreci1 with header line,
          l_doc_chng type sodocchgi1,
          l_counter type i.

  • SPAM XPRA_EXECUTION ERROR for SAPKIBIIP5- SAPKIBIIQ4(BI CONT 703)

    Hi
    I am doing the support packs for my SAP BW 7.0 system.
    I have successfully completed the SAP_ABA, SAP_BASIS, SAP_BW.
    I am currently doing the SAP BI CONT 703 from SAPKIBIIP5- SAPKIBIIQ4.
    I am getting the error in the XPRA_EXECUTION ERROR in SPAM.
    I have successfully completed the same task for my BW development
    system.
    The short dump and the SPAM Log are both attached.
    The SPAM version and the kernel version are up to date as suggested.
    Runtime Errors SYNTAX_ERROR
    Date and Time 11/27/2009 20:10:04
    |Short
    text
    |
    | Syntax error in
    program "SAPLRZD1 ".
    |
    |What
    happened?
    |
    Error in the ABAP Application
    Program
    |
    |
    The current ABAP program "SAPLRZTR" had to be terminated because
    it has
    come across a statement that unfortunately cannot be
    executed.
    |
    |
    The following syntax error occurred in program "SAPLRZD1 " in
    include "LRZD1U19
    | "
    in
    |
    | line
    291:
    |
    "Different number of parameters in FORM and PERFORM (routine:
    PROP_VALU"
    "E_GET, number of formal parameters: 5, number of actual
    parameters: 6)"
    | " "
    |
    | " "
    |
    |
    |
    The include has been created and last changed
    by:
    | Created
    by: "SAP "
    |
    | Last changed
    by: "SAP "
    |
    Error in the ABAP Application
    Program
    |
    |
    The current ABAP program "SAPLRZTR" had to be terminated because
    it has
    come across a statement that unfortunately cannot be
    executed.
    |What can you
    do?
    |
    Please eliminate the error by performing a syntax
    check
    (or an extended program check) on the
    program "SAPLRZD1 ".
    You can also perform the syntax check from the ABAP
    Editor.
    |
    |
    If the problem persists, proceed as
    follows:
    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
    |
    The following syntax error was found in the program
    SAPLRZD1 :
    "Different number of parameters in FORM and PERFORM (routine:
    PROP_VALU"
    "E_GET, number of formal parameters: 5, number of actual
    parameters: 6)"
    | " "
    |
    | " "
    |
    |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 and want to send an
    error
    Runtime Errors SYNTAX_ERROR
    Date and Time 11/27/2009 20:10:04
    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.

    Log File:               
    sapsolmgr\sapmnt\trans\log\SAPRIBIIP5.BWQ
    Execution of programs after import (XPRA)
    Transport request   : SAPKIBIIP5
    System              : BWQ
    tp path             : tp
    Version and release: 372.04.70 700
    Post-import methods for change/transport request: SAPKIBIIP5
    Post-import method ENHO_AFTER_IMPORT started for ENHO L, date and time: 20091127185403
    Post-import method AFTER_IMP_SXSD started for SXSD L, date and time: 20091127185403
    Post-import method RSA2_DSOURCE_AFTER_IMPORT started for OSOD L, date and time: 20091127185403
    Post-import method RS_AFTER_IMPORT_D started for DSPT L, date and time: 20091127185403
    Routines were successfully imported in version D: (Routine: 00DREO59YUHGNHXQYOEA1ELGX)
    Routines were successfully imported in version D: (Routine: 019BOVVIWIG2F7XGR0NQ2S0WM)
    Routines were successfully imported in version D: (Routine: 06LF0BE6BKCYDE0WW51WF8I7L)
    Routines were successfully imported in version D: (Routine: 06RXUO122ZPH30HFLNIUKDIY9)
    Routines were successfully imported in version D: (Routine: 090FDIDUSEBUARM758K61X43G)
    Routines were successfully imported in version D: (Routine: 0D8H7ZXMRO3QKU4UCORFU0712)
    Routines were successfully imported in version D: (Routine: 0F4BLN8JT3BMY2R5QRVZSJ2UP)
    Routines were successfully imported in version D: (Routine: 0PHMCO4KHYIECNW3NM96G4OJ5)
    Routines were successfully imported in version D: (Routine: 10253VAWT2S8WKJA3J4SD5VVC)
    Routines were successfully imported in version D: (Routine: 14DXP50VMPLP8C635A6KHKYLT)
    Routines were successfully imported in version D: (Routine: 15R4I74SYRIT5HE4SJ4O2X8YE)
    Routines were successfully imported in version D: (Routine: 1AS454WNQUTPNUPRS9B50JW35)
    Routines were successfully imported in version D: (Routine: 1BDI1HOJH9NWVUWAZ3BL7QOZG)
    Routines were successfully imported in version D: (Routine: 1JA0778MVOE0NTY6XUBNY1OCQ)
    Routines were successfully imported in version D: (Routine: 1KOW8NSVTHLCTKZRWO0TQ0IVR)
    Routines were successfully imported in version D: (Routine: 1KVA8IX4PZYWE4O4YAR7D93KS)
    Routines were successfully imported in version D: (Routine: 1LEQCJ78924OT04R5I16SDBII)
    Routines were successfully imported in version D: (Routine:
    Routines were successfully indicated as SAP objects
    Routines were successfully indicated as SAP objects
    Routines were successfully indicated as SAP objects
    Update rules 0FFQWWTK5RXR6223S5OTLDPV5 read in version D
    Update rules 2B5Y7C1QT47J0E2VZGVE90YKW read in version D
    Update rules 3816CVITIYJH7FR04D3OPVZBQ read in version D
    Update rules 4AE90UTI7TVJSJ13Y7V3VPK7Q read in version D
    Update rules 4PHJIV23JPXLMV5AFYHKF6CF0 read in version D
    Update rules 51SVOFKKV5GP7BNSF16IT42RG read in version D
    Update rules 5QO90JJ10JJMHPR7DHZEF7OVD read in version D
    Update rules 62MT6EKF0X0UCRSQBSFQJ2H06 read in version D
    Update rules 63ZOE8TL14W62X6WX2SFSNN75 read in version D
    Update rules 66SVSMMC9NGQRNQEH10FYWFA4 read in version D
    Update rules 6AY5JIWPKD3KZGVRKJ6T7SEHN read in version D
    Update rules 6MJH6VK2SEAC215SK02V4M4GG read in version D
    Update rules 6Y88R0XONAZW6ST1KOBQMZBKS read in version D
    Update rules 7NCH0HPBKYKBF273IEMTKLHEK read in version D
    Update rules 840SQXVZEGK41X5U1IWOK87CX read in version D
    Update rules 8FD8BYQ8DZGO5OLINVPJ3I72Z read in version D
    Update rules AHVPAZZ729MEF4FFZMEOAV9J0 read in version D
    Update rules AU1VRYF63PZP91L7P8YOOEAUT read in version D
    Update rules CDVLJ47K24BQ176JEABQLBMFV read in version D
    Update rules CKMKT7OXYI8A2SQ3EH19H4W0G read in version D
    Update rules CMLUMYKKG0AJLAZNNBXIMIFB0 read in version D
    Update rules CZORWJOL0XOQ40KTR1HIOIRVC read in version D
    Update rules DXD1W8JF3X5O3XVXQLIDV5RG1 read in version D
    Update rules EAA6S9H6UP1BM43DLRS67KFSS read in version D
    Update rules EEEV2W862Z319BCFFV6KLQWQ9 read in version D
    Program terminated (job: RDDEXECL, no.: 18540200)
    See job log
    Execution of programs after import (XPRA)
    End date and time : 20091127190007
    Ended with return code:  ===> 12 <===
           |   ######################################

  • SPAM support packages error

    Hi,
    I've tried to upgrade CRM 5.0 SR 1 to SR 2, during  the operation I had error during the phase TP_IMPORT, the error was an buffer inconsistency. It was impossible to reset the queue during this phase. So I deleted entries in the database table PAT01-PAT02-PAT03, now queue is empty but I've internal error of spam check when I try to reload this package.
    In the background, I've the job still running RDDGENOL (triggered RAISE_EXECPTION, and timeout) created by ddic during the SP, who lock tables for SP, I can't stop it.
    Furthermore, a dialogue process running with a BDG process waiting for RFC, which is also impossible to cancel.
    Any help will be thankful.

    hi people,
    we have checked for the status of support package in Transaction SPAM traffic signal is still red and in the Phase RUN_SPAU_?  it is stuck and even after restarting import it shows clean-up phase is left and it ends with same error mention above
    the support package name is SAPKB70014 size is 116266 MB now after restarting the Import the following error message comes
    The import was stopped, since an error occurred during the phase
    RUN_SPAU_?, which the Support Package Manager is unable to resolve
    without your input.
    After you have corrected the cause of the error, continue with the
    import by choosing Support Package -> Import queue from the initial
    screen of the Support Package Manager.
    The following details help you to analyze the problem:
         -   Error in phase: RUN_SPAU_?
         -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
         -   Return code: 0255
         -   Error message: Could not connect to semaphore server
    we run all the phase in background, and even after entering the support package number in transaction SPAU there it is showing
    "No objects within selected filter parameteres"
    Q.1 Any idea what went wrong and how to fix that?
    Q.2 Is there any problem if we run the all four phases of support package in background or it should be run in dialog ?
    latest tp & R3trans updated

  • SPAM Update needed for Upgrade Assistent

    For updating a SAP System (IDES 4.7) I assume I need the Upgrade Assistant!? I installed the UA-Server and connected with a browser to the local Service (http://x.x.x.x:4239/ua/UaGUI.html). After a few steps in the phase "PREPARE", the assistand is running into the following error: "The SPAM Version 15 of your system is too low!!!". I downloaded the newest SPAM-Package and unpacked it. The resulting files are "CSR0120031469_0026199.ATT" and "CSR0120031469_0026199.PAT". I copied them to \usr\sap\trans\EPS\in but the error still appears...
    Any hint how to get 'em working? Am I totally wrong with this solution?

    Hi Thomas
    I think for upgrading an IDES system you need to install it again. Anyway , this note 164244 says you can ask SAP for an upgrade if necessary.
    Regards
    Jose Luis Valverde

Maybe you are looking for