EHP3 import with SPAM/SAINT 32 - IMPORT_OBJECT_LIST error

Hi all
I am trying to import EHP3 for ECC 6.0. We are on Windows 2003 and MS SQL 2005 SP2. Kernel release is 175,  tp version is 372.04.40 and R3trans version is 186 (compiled time Nov 23 2008).
During the IMPORT_OBJECT_LIST phase, the precessing stops at random places when I start and restart SAINT. A couple examples:
Import phase 'IMPORT_OBJECT_LIST' (01.12.2008, 20:53:58)
   Error during executing the tp command 'tp GETOBJLIST SAPKW70018   ...'
   tp return code: '0212' , tp message: 'could not access file as supposed (see dev_tp or S' , tp output:
     This is tp version 372.04.40 (release 700, unicode enabled)
     \\dzs0d7e004\sapmnt\trans\tmp\SAPKKW70018.U01 for transport: SAPKW70018: Invalid argument
     HALT 20081201211431
     ERROR: \\dzs0d7e004\sapmnt\trans\tmp\SAPKKW70018.U01 : cant open
     : Invalid argument
     ERROR: EXIT(16) -> process ID is: 10924
     tp returncode summary:
     TOOLS: Highest return code of single steps was: 16
     ERRORS: Highest tp internal error was: 0212
     standard output from tp and from tools called by tp:
and
Import phase 'IMPORT_OBJECT_LIST' (01.12.2008, 22:11:45)
   Error during executing the tp command 'tp GETOBJLIST SAPK-603DFINFICAX   ...'
   tp return code: '0212' , tp message: 'could not access file as supposed (see dev_tp or S' , tp output:
     This is tp version 372.04.40 (release 700, unicode enabled)
     \\dzs0d7e004\sapmnt\trans\tmp\SAPKK-603DFINFICAX.U 01 for transport: SAPK-603DFINFICAX: Invalid argument
     HALT 20081201221847
     ERROR: \\dzs0d7e004\sapmnt\trans\tmp\SAPKK-603DFINFICAX.U 01 : cant open
     : Invalid argument
     ERROR: EXIT(16) -> process ID is: 9248
     tp returncode summary:
     TOOLS: Highest return code of single steps was: 16
     ERRORS: Highest tp internal error was: 0212
     standard output from tp and from tools called by tp:
   Abort the import due to an error situation (01.12.2008, 22:18:47)
The log file dev_tp contains several entries identical to this:
This is R3trans.exe version 6.14 (release 700 - 07.03.07 - 18:40:00).
unicode enabled version
R3trans.exe finished (0000).
while the SLOG file looks like this (only pasting the end of the log, as the preceeding entries are similar to this):
START CMDIMPORT            U01 L      20081201212953              THKJ         dzs0d7e004 20081201212952     
STOP  CMDIMPORT            U01 L      20081201212953              THKJ         dzs0d7e004 20081201212952     
HALT 20081201212953
ERROR: \\dzs0d7e004\sapmnt\trans\tmp\SAPKK-60007INFICA.U01 : cant open
: Invalid argument
ERROR: EXIT(16) -> process ID is: 3316
START MAIN IMPORT          U01 I      20081201221145              THKJ         dzs0d7e004 20081201221145     
STOP  MAIN IMPORT          U01 I      20081201221214              THKJ         dzs0d7e004 20081201221145     
START MAIN IMPORT          U01 I      20081201221214              THKJ         dzs0d7e004 20081201221214     
STOP  MAIN IMPORT          U01 I      20081201221237              THKJ         dzs0d7e004 20081201221214     
START MAIN IMPORT          U01 I      20081201221238              THKJ         dzs0d7e004 20081201221237     
STOP  MAIN IMPORT          U01 I      20081201221244              THKJ         dzs0d7e004 20081201221237     
START MAIN IMPORT          U01 I      20081201221245              THKJ         dzs0d7e004 20081201221244     
STOP  MAIN IMPORT          U01 I      20081201221248              THKJ         dzs0d7e004 20081201221244     
START MAIN IMPORT          U01 I      20081201221249              THKJ         dzs0d7e004 20081201221249     
STOP  MAIN IMPORT          U01 I      20081201221250              THKJ         dzs0d7e004 20081201221249     
START CMDIMPORT            U01 L      20081201221250              THKJ         dzs0d7e004 20081201221250     
STOP  CMDIMPORT            U01 L      20081201221250              THKJ         dzs0d7e004 20081201221250     
HALT 20081201221847
ERROR: \\dzs0d7e004\sapmnt\trans\tmp\SAPKK-603DFINFICAX.U01 : cant open
: Invalid argument
ERROR: EXIT(16) -> process ID is: 9248
I have tried to delete the queue and recreate it, stop and start the SAP instance, restarted the server and restarted SAINT several times. It stops at what seems to be random places every time. I am logged on as the <sid>adm user, and have checked that the user has full access to usr\sap\trans\ directories.
I have installed EHP3 for ECC 6.0 before without issues, the difference this time is that I am using SPAM/SAINT version 32, instead of version 30. I have seen the note 1232804 - SPAM/SAINT: TP_FAILURE 0212 in phase IMPORT_OBJECT_LIST, but the error message is not quite the same, and I am on SPAM/SAINT 32.
Has anyone experienced this, or know how it can be fixed?
Thanks!
Regards,
Thomas

Hi.
I have checked that the <sid>adm user has full access to the share sapmnt.
I also tried to run the IMPORT_OBJECT_LIST phase again, with this result:
Import phase 'IMPORT_OBJECT_LIST' (02.12.2008, 08:11:00)
Error during executing the tp command 'tp GETOBJLIST SAPK-603DMINEAFINSRV   ...'
tp return code: '0212' , tp message: 'could not access file as supposed (see dev_tp or S' , tp output:
   This is tp version 372.04.40 (release 700, unicode enabled)
   \\dzs0d7e004\sapmnt\trans\tmp\SAPKK-603DMINEAFINSR V.U01 for transport: SAPK-603DMINEAFINSRV: Invalid argument
   HALT 20081202081659
   ERROR: \\dzs0d7e004\sapmnt\trans\tmp\SAPKK-603DMINEAFINSR V.U01 : cant open
   : Invalid argument
   ERROR: EXIT(16) -> process ID is: 9344
   tp returncode summary:
   TOOLS: Highest return code of single steps was: 16
   ERRORS: Highest tp internal error was: 0212
   standard output from tp and from tools called by tp:
As you can see, the filename seems to be a bit strange "SAPKK-603DMINEAFINSR V.U01". I would expect the filename to contain a space between R and V.U01. Is this a program error? I have not been able to find any notes on this issue.
Regards,
Thomas

Similar Messages

  • SPAM/SAINT patch updation error

    Hello all
                When the pp consultant execute a transation code MIGO In development server then there is a run time error
    occur. After that I am try to update the patches,
    but then error is  that SAPM/SAINT  SAPKD7003 patch  is get canceled
    so I could not update the other patches, Please give me solution how to delete this canceled patch,
    or if there is any other solution please suggest me,
    my system details are
    mySAP ECC 6.0 / Windows 2003 / SQL 2005
    Thanks in advance
    G Patil

    what error do you get?? this information is not enough to suggest a solution.
    Check the import logs for more information.
    SPAM >> goto >> import logs >> spam/saint update.
    Also, check the tp system log from the same and give more information about the error.
    Regards,
    Jazz

  • Importing a SPAM/SAINT Update

    Hello,
    I am trying to update SPAM/SAINT.
    In Transaction SPAM, when I import SPAM/SAINT Update the package SAPKD70139 is proposed for the queue.
    I need to import this one SAPKD70042, that already decompressed in EPS/in.
    (Both are displaying in OCS overview)
    Could anybody help me to find the way deleting a Not imported Package (SAPKD70139) in OCS Packages / SPAM ?
    Many Thanks in advance
    Latif

    Issue is solved.
    Regards

  • Problem faced while update to spam/saint version 39 basis realease 700

    Hi
    I am a SAP BASIS Administrator at fresher level.My spam/saint version was 22 when i applied SPAM/SAINT version 39 for SAP BASIS 700 , at first time it was not imported and struck at  *Movenamespace with return code zero* phase and the import log showed error at IMPORT_PROPER phase,
    But as described in the SAP note 822379 , i followed the instruction emptied the queue and imported the spam/saint version again
    This time the import was completed and showed a green status. But next time when i wanted to apply SAP_BASIS 10 support pacake immediately it showed an runtime syntax error.
    The error is as follows
    Runtime Errors         SYNTAX_ERROR
    Date and Time          02.03.2011 11:57:31
    |Short text                                                                               
    |    Syntax error in program "CL_OCS_RT_ANALYSIS============CP ".                                 
    |What happened?                                                                               
    |    Error in the ABAP Application Program                                                        
    |                                                                               
    |    The current ABAP program "SAPLSPAM" had to be terminated because it has                      
    |    come across a statement that unfortunately cannot be executed.                               
    |                                                                               
    |    The following syntax error occurred in program                                               
    |     "CL_OCS_RT_ANALYSIS============CP " in include                                              
    |     "CL_OCS_RT_ANALYSIS============CM002 " in                                                   
    |    line 135:                                                                               
    |    "Die Transformation "RTA_TRAFO" hat keine aktive Version."                                   
    |    " "                                                                               
    |    " "                                                                               
    |    " "                                                                               
    |                                                                               
    |    The include has been created and last changed by:                                            
    |    Created by: "SAP "                                                                           
    |    Last changed by: "SAP "                                                                      
    |                                                                               
    |Error analysis                                                                               
    |    The following syntax error was found in the program                                          
    |     CL_OCS_RT_ANALYSIS============CP :                                                          
    |    "Die Transformation "RTA_TRAFO" hat keine aktive Version."                                   
    |    " "                                                                               
    |    " "                                                                               
    |    " "                                                                               
    |Trigger Location of Runtime Error                                                                
    |    Program                                 SAPLSPAM                                             
    |    Include                                 LSPAMU69                                             
    |    Row                                     364                                                  
    |    Module type                             (FUNCTION)                                           
    |    Module Name                             SPAM_PROLOGUE                                        
    |Source Code Extract                                                                               
    |Line |SourceCde                                                                               
    334
    |  335|*       and set default start options according to the new scenario                        
    |  336|        CALL FUNCTION 'OCS_SET_DEFAULT_START_OPTIONS'                                      
    |  337|          EXPORTING                                                                        
    |  338|            iv_ocs_tool = lv_tcode                                                         
    |  339|            iv_scenario = lv_scenario                                                      
    |  340|            iv_save     = on                                                               
    |  341|          EXCEPTIONS                                                                       
    |  342|            OTHERS      = 0.                                                               
    343
    |  344|*       inform the user about the scenario change                                          
    |  345|        MESSAGE i336(tn) WITH lv_inact_scenario lv_scenario                                
    |  346|                         RAISING emergency_stop.                                           
    |  347|      ENDIF.   "sy-saprl(2) < '46'                                                         
    |  348|    ENDIF.                                                                               
    |  349|*   activate all halt points for current transaction                                       
    |  350|    UPDATE patstop SET cont_step = off                                                     
    |  351|                   WHERE ocs_tool = lv_tcode.                                              
    352
    |  353|*   initialize the application specific checks                                             
    |  354|    UPDATE patcheck SET ret_code   = space                                                 
    |  355|                        reason     = space                                                 
    |  356|                        message    = space                                                 
    |  357|                        ign_in_dia = off                                                   
    |  358|                        ign_in_btc = off                                                   
    |  359|                        queue_id   = lv_queue_id                                           
    |  360|                    WHERE ocs_tool = lv_tcode AND                                          
    |  361|                          active   = on.                                                   
    362
    |  363|*   collect some source data for the runtime analysis                                      
    |>>>>>|    CREATE OBJECT lr_rt_analysis                                                           
    |  365|      EXPORTING                                                                            
    |  366|        iv_queue_id = lv_queue_id                                                          
    |  367|      EXCEPTIONS                                                                           
    |  368|        others      = 99.                                                                  
    |  369|    IF sy-subrc = 0.                                                                       
    |  370|      CALL METHOD lr_rt_analysis->collect_conf_data                                        
    |  371|        EXPORTING                                                                          
    |  372|          iv_conf_group = 'ALL'                                                            
    |  373|        EXCEPTIONS                                                                         
    |  374|          OTHERS        = 0.                                                               
    |  375|      CALL METHOD lr_rt_analysis->save                                                     
    |  376|        EXCEPTIONS                                                                         
    |  377|          OTHERS = 0.                                                                      
    |  378|    ENDIF.                                                                               
    |  379|  ENDIF.                               "SY-SUBRC = 0                                       
    380
    |  381|* (5) now start with the application:                                                      
    |  382|* - set the OCS environment                                                                
    |  383|* - read the settings                                                                      
    Can anyone please suggest a bolution on BASIS perspective

    Hi all,
    Not sure if this thread is still active at all, but just to be sure, and to close it once and for all
    to solve this issue :
    Icheck class CL_OCS_RT_ANALYSIS in TA SE24 and go to method GET_XML.
    Search for RTA_TRAFO, jump to object via doubleclick and activate it.
    Afterwards install the latest TP and R3trans tools from sapnet, and SPAM should be working again.
    Best regards,
    Menno van Rooij

  • Spam/Saint update failed

    Hello,
    My current SPAM/SAINT version is 20.
    I tried updating it to version 38.
    But while updaing m facing a runtime error  which is generating a short dump.
    Short Text of dump is as follows:
    Syntax error in program "CL_OCS_RT_ANALYSIS============CP
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLSPAM" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        The following syntax error occurred in program
         "CL_OCS_RT_ANALYSIS============CP " in include
         "CL_OCS_RT_ANALYSIS============CM002 " in
        line 135:
        "Die Transformation "RTA_TRAFO" hat keine aktive Version."
        The include has been created and last changed by:
        *Created by: "SAP "    Last changed by: "SAP "*
    Below is the status of Import phase
    SPAM/SAINT update is being processed
    SPAM status: (Red)
    Import phase:     PROLOGUE
    Please help.
    Thanks Deepak

    I have similar problem, i have the following runtime error:
    The following syntax error occurred in program
    "CL_OCS_RT_ANALYSIS============CP " in include
    "CL_OCS_RT_ANALYSIS============CM002 " in
    line 13:
    "Type "OCSRT_TOOL" is unknown"
    I have create OSS-message and SAP reply;s:
    Regarding your issue, please transport the class CL_OCS_RT_ANALYSIS
    from other system in the landscape which is on the same release and
    support package level and with the SPAM\SAINT update version as the
    PRD system to the PRD system to resolve the syntax error.
    Once the syntax error is resolved in the PRD the SPAM\SAINT update can
    be continued in the SPAM to import the SPAM\SAINT update in the system.
    For more information please refer the link specified below for
    including the objects manually in the transport request.
    http://help.sap.com/saphelp_nw70/helpdata/en/57/38e2864eb711d182bf0000e829fbfe/content.htm
    I looked to the url, but still not understanding how to add it...can someone explain me how to export it?
    Thanks,
    Cheung

  • Spam/saint update  to 40

    Hi,
              Can we update spam/saint to level 40 without use of solution manager?
    What are the requirements needed to download the spam/saint update?     
    Thanks in Advance

    Hi,
    Refer to help.sap.com for understanding the functionality of SPAM and SAINT.
    http://help.sap.com/saphelp_46c/helpdata/en/d7/56e89a884b11d2b422006094b9ea64/frameset.htm
    http://help.sap.com/saphelp_46c/helpdata/en/d7/56e89a884b11d2b422006094b9ea64/content.htm
    Can we update spam/saint to level 40 without use of solution manager?
    Specify the SAP release.
    You must use solution manager to download SPAM / SAINT update.
    Because you need to approve the download request from MOPZ.
    What are the requirements needed to download the spam/saint update?
    The basic requirement would be to import latest SPAM/SAINT package before you update your Support pack levels for ABAP system.
    [Link|http://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CDIQFjAB&url=http%3A%2F%2Fhelp.sap.com%2Fprintdocu%2Fcore%2Fprint46c%2Fen%2Fdata%2Fpdf%2FBCUPGOCSSPAM%2FBCUPGOCSSPAM.pdf&ei=4_BBT4DXI4jm2QWXwZynCA&usg=AFQjCNFWOUEaYbDCXw_1fR_gTBm-yeOXWw]
    Br,
    Venky

  • 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

  • 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

  • SPAM/SAINT update error patch 23 - 640

    Hi:
    I´m recieving the following dump when updating SPAM/SAINT patch 23 under 640:
    Syntax error in program "SAPLOCS_UI "
    Error in ABAP application program.
    The current ABAP program "SAPLSPAM" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLOCS_UI ", the following syntax error occurred
    in the Include "LOCS_UIU15 " in line 1:
    "Function "OCS_DISPLAY_WITH_USER_BUTTON" not found in Function Library."
    In program "SAPLOCS_UI ", the following syntax error occurred:
    "Function "OCS_DISPLAY_WITH_USER_BUTTON" not found in Function Library."
    Thanks a lot,
    Armenta

    Hii read modification adjustments in this document u will get a clear idea.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCUPGOCSSPAM/BCUPGOCSSPAM.pdf
    Award points if useful

  • Trigger Compilation Errors after Full Import with Datapump

    Hello All,
    We did a full import with Oracle Datapump, and encountered some errors related to triggers:
    ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT_RESET" created with compilation warnings
    ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT_RESET" created with compilation warnings
    ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT" created with compilation warnings
    ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT" created with compilation warnings
    ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT_RESET" created with compilation warnings
    ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT_RESET" created with compilation warnings
    ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT" created with compilation warnings
    ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT" created with compilation warningsWe are wondering if there is some bug with the datapump on oracle 10.2.0.2. What caused such errors and how to resolve this trigger issue?
    Thanks!

    Hello,
    Show errors / at the end of the trigger and see if any of the dependent objects is missing resulting in error at compilation.
    Also you can try manually fixing the issue
    CREATE OR REPLACE TRIGGER table1_trg
       AFTER INSERT
       ON TABLE1    REFERENCING NEW AS new OLD AS old
       FOR EACH ROW
    DECLARE
       tmpvar   NUMBER;
    BEGIN
    Trigger code
    EXCEPTION
       WHEN OTHERS
       THEN
          -- Consider logging the error and then re-raise
          RAISE;
    END table1_trg;
    SHOW ERRORS;Regards

  • SPAM/SAINT Update stuck on Import phase Epilogue

    Under status it shows that SPAM/SAINT update is being processed and SPAM status shows red light.
    Import phase is EPILOGUE.
    I got out of the SPAM and restarted it, it shows the updated SPAM version but status is still red light.
    I am updating to version 6.20/30 from 29
    Any idea or suggestion

    Hello Bill
    Do you see any processes running in SM50?
    Try to come out from SPAM and go again in SPAM and check.
    regards,
    Payal

  • Error while confirming SPAM/SAINT patch through Solution Manager MOpz

    Hi,
    When I am confirming patches (release 700) in Solman through maintenance optimizer, it is allowing to confirm all except the SPAM/SAINT update version 700/0027.
    For the SPAM/SAINT patch, it is giving error "Object <some number> update error".
    Please let me know what to do.
    Thanks & Regards,
    Kunal.

    @sean i said him alternate way of downloading the patch of SPAM/SAINT 30 when he is unable to download from MOpz
    I always try to give alternate possible ways to resolve the problem.
    Regards
    Uday

  • UPDATE SPAM/SAINT TRANSACTION (SAPKD70023)

    I am trying to Update SPAM/SAINT transaction in Client 000. The log reports finished with return code 4, but the transaction still runs and the message below is: DD IMPORT finished with retyurn code 4. But it  is working, yet.
    I am updating the SPAM/SAINT transaction in Solution Manager 4.0 and the kernel release is 7.00 with patch level 83.

    Import of the current OCS Queue (02.11.2007, 16:44:06)
    The import is continued in phase 'CHECK_REQUIREMENTS'
    Import phase 'PROLOGUE' (02.11.2007, 16:44:11)
    Import phase 'PROLOGUE' was successfully finished (02.11.2007, 16:44:12)
    Import phase 'CHECK_REQUIREMENTS' (02.11.2007, 16:44:12)
    Import phase 'CHECK_REQUIREMENTS' was successfully finished (02.11.2007, 16:44:13)
    Import phase 'DISASSEMBLE' (02.11.2007, 16:44:13)
    Import phase 'DISASSEMBLE' was successfully finished (02.11.2007, 16:44:17)
    Import phase 'ADD_TO_BUFFER' (02.11.2007, 16:44:17)
    Import phase 'ADD_TO_BUFFER' was successfully finished (02.11.2007, 16:44:18)
    Import phase 'MODIFY_BUFFER' (02.11.2007, 16:44:18)
    Import phase 'MODIFY_BUFFER' was successfully finished (02.11.2007, 16:44:18)
    Import phase 'TEST_IMPORT' (02.11.2007, 16:44:18)
    Import phase 'TEST_IMPORT' was successfully finished (02.11.2007, 16:44:23)
    Import phase 'IMPORT_OBJECT_LIST' (02.11.2007, 16:44:23)
    Import phase 'IMPORT_OBJECT_LIST' was successfully finished (02.11.2007, 16:44:28)
    Import phase 'OBJECTS_LOCKED_?' (02.11.2007, 16:44:28)
    Import phase 'OBJECTS_LOCKED_?' was successfully finished (02.11.2007, 16:44:28)
    Import phase 'SCHEDULE_RDDIMPDP' (02.11.2007, 16:44:28)
    Import phase 'SCHEDULE_RDDIMPDP' was successfully finished (02.11.2007, 16:44:28)
    Import phase 'IMPORT_PROPER' (02.11.2007, 16:44:28)
    The 'IMPORT_PROPER' phase started at 16:44:28 but at now it is still running, at status line stays - "DD Import finished with returncode 4" ...
    Can anybody helps to update SPAM/SAINT proper?

  • Update SPAM/SAINT package for release 7.00 terminated

    Hi All,
    We have installed solman 4.0 on windows environment. when i tried to import spam/saint update, it got terminated in the phase IMPORT_PROPER.
    Also, in SM50 it is showing on workprocess running for long and gets terminated. I also have run SGEN once my installation was over.
    0     DIA     4028     Running          Yes     649     SAPMS38L     000     DDIC     Delete     D010INC
    can anyone suggest what the problems would be..
    Thanks and Regards,
    sailesh K

    Hi
    I have tried three times. In fact I also restarted SAP System by changing rdisp/max_wp_runtime to 0 as there were lot of short dumps with timeouts.
    I notice that currently job RDDGEN0L is running at present.
    Also,
    1) Dialogue work process running Report SAPMS38L with action Delete on Table D0101NC (User DDIC).
    2) BGD Work process Status “On Hold” Reasn “RFC” with report SAPLSDDD (User DDIC).
    SPAM Status is "MOVE NAMETABS FINISHED WITH RETURN CODE 0". Import logs finished with error code 4.
    Regards
    Chandu
    P.S : FYI I am opening another thread with the same message.

  • How to Get Out of A SPAM/SAINT Update

    I am applying SPAM?SAINT Update No. SAPKD62020 to SAPKD62023. No. 20 is showing cancelled when I display all the Support packages loaded but will not let me go forward without getting rid of this cancelled one. How do I remove it so I can go forward with this. This is very frustrating. I tried to reset it but not succesful.
    Please help

    Thank all of you guys. Believe me I did all of these things mentioned above. I read so many threads about this particular problem and it finally becomes confusing.
    What I did:
    - Reset the SPAM/UPDATES and still did not work
    - Used tcode SEPS which I read from SAP site and remove everything and then I  got a green status - Re-applied that first patch again - Same thing it got stuck by saying again Error on: CHECK_REQUIREMENTS and QUEUE_NOT_EMPTY
    - Checked Disk space and it's ok
    - Checked Security for the log folder - ok
    - Checked RFC connection test - ok
    - Used tp connect <SID> command line - ok
    - Used tp SHOWBUFFER -D SOURCESYSTEMS= TAG=SPAM - This one never works - I always get the following below
    C:\Documents and Settings\rjoseph>tp showbuffer -dsourcesystem= tag=spam
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    This is tp version 340.16.31 (release 640)
    E-TPSETTINGS could not be opened.
    EXIT
    ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
    Error in TPSETTINGS: transdir not set.
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0208
    tp finished with return code: 208
    meaning:
      error in transportprofil (param missing, unknown,...)<b></b>
    Dont't know what to do anymore. Spent whole night researching this.
    As a matter of fact. My QAS system which is basically the same as DEV I am done with all 80 patches in less than 8 hours. Why is it DEV which is a very important system is causing me grieves.
    Anyway I opened a ticket with SAP and hope they will get back with me today.
    Once again thank you all of. If you can thing of anything else, I would really appreciate it.

Maybe you are looking for

  • HT1933 I am unable to open iTunes on my iPhone 4S after downloading iOS7. How can I fix this or report it to Apple?

    After downloading iOS7 on my iPhone 4S, I can not open the iTunes app. When I click on the app, the "page" pops up but then quickly crashes.

  • XML Publisher Version Mismatch Issue

    Hi, I am using XML Publisher 5.62 and deploying in XML Publisher 4.5 Server, for a standard Invoice report using XML Publisher. The requirement is that i have to have a logo and some invoice header details repeating for every page ,then ofcourse foll

  • Computer sees monitor-but monitor does not see computer.

    I have a MacBookPro with the older 29 pin DVI out. I own an 8.4" HD monitor for video production and want to use it for editing. I am trying to get my Marshall V-R84DP-HD monitor to see the computer and it does not recognize it. I have Mac OS X Versi

  • Why are the fonts so ugly?

    When I'm using the Adobe Acrobat Reader plugin (10.1.8.24) in Firefox (25.0.1 in this case) I'm getting terriby ugly fonts from domcuments I'm invoking from sites. In MSIE 11.0.9600 the fonts look fine and anti-aliased. Not so in FF. Example (ugly ca

  • Ical alarms still opening off screen

    Are other people still having problems with Ical alarms opening up off screen After the 10.4.9 update? Why would Apple say that it is finally fixed in their descriptions when it is Not? I wonder who at Apple tests these things and how they get their