Codelite: Program exited with return code: 127

I installed codelite from AUR. When I try to make a simple "Hello world", this is what I get.
Not even a new window.
I try the same code in a Ubuntu machine, and it works. So I think there are some libraries missing right?

Sorry if this counts as a necropost, but I just had this same issue and managed to solve it.
Yes, the 127 means "Command not found," but it has nothing to do with user input. If you check the console, CodeLite is trying to run something like this:
/usr/bin/codelite_xterm './YourProgram ' '/bin/sh -f /usr/bin/codelite_exec ./YourProgram'
Coincidentally, if you run /usr/bin/codelite_xterm yourself with no arguments, it will still return 127. This is because it tries to invoke xterm, which isn't installed.
The CodeLite AUR package needs to depend on xterm to avoid this - I'll bother the packager.

Similar Messages

  • Transport control program ended with return code 208

    hi all please give me the solution for the transport control program ended with return code 208
    after the request released

    Hi,
    Please check the transport log at OS level. below is the path
    /usr/sap/trans/log.
    You can also check from SAP level. After the transport is import go log button in the STMS_IMPORT tcode  >>> expand all the possible values... you can find the exact reason why the transport ended with error.
    And also plesae check if nay entry exits in TRBAT table .
    Thanks,
    Phani.

  • [Error during Export] R3load exited with return code 11

    Hi guys,
    While performing and Unicode Migration, during Export Phase, Migration Monitor returned the following error while exporting a package
    ERROR: 2014-06-01 10:57:44 com.sap.inst.migmon.LoadTask run
    Unloading of 'REGUC' export package is interrupted with R3load error.
    Process '/usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error' exited with return code 11.
    For mode details see 'REGUC.log' file.
    Standard error output:
    sapparam: sapargv(argc, argv) has not been called!
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    REGUC.log details:
    (As you see, it does not provide reasons of this error, all messages are informative and alike all other Packages logs)
    /usr/sap/ECP/DVEBMGS00/exe/R3load: START OF LOG: 20140601105052
    /usr/sap/ECP/DVEBMGS00/exe/R3load: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
    /usr/sap/ECP/DVEBMGS00/exe/R3load: version R7.40/V1.8
    Compiled Jul 23 2013 21:30:53
    /usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 1160
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
    (RSCP) INFO: "REGUC001.xml" created.
    (GSI) INFO: dbname   = "ECP20030615080638
    (GSI) INFO: vname    = "ORACLE "
    (GSI) INFO: hostname = "ecp "
    (GSI) INFO: sysname  = "SunOS"
    (GSI) INFO: nodename = "ecp"
    (GSI) INFO: release  = "5.10"
    (GSI) INFO: version  = "Generic_142900-13"
    (GSI) INFO: machine  = "sun4u"
    Tried to find what does R3load Return Code 11 means, but I couldnt find further information on this.
    Any hint of what is causing this error?
    (Please disregard any Filesystem issues since all of them have available space)
    Best!

    After using latest R3load patch, it provides furher information on the log file.
    -------------------- Start of patch information ------------------------
    patchinfo (patches.h): (0.070) R3ldctl: fix CDS views creation in upgrade export mode (note 2
    017805)
    DBSL patchinfo (patches.h): (0.022) Smaller corrections in release 7.40 (th, dp, vmc, dpmon)
    (note 1821404)
    --------------------- End of patch information -------------------------
    process id 27326
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 1160
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
    (RSCP) INFO: "REGUC003.xml" created.
    (GSI) INFO: dbname   = "ECP20030615080638
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "ecp                                                             "
    (GSI) INFO: sysname  = "SunOS"
    (GSI) INFO: nodename = "ecp"
    (GSI) INFO: release  = "5.10"
    (GSI) INFO: version  = "Generic_142900-13"
    (GSI) INFO: machine  = "sun4u"
    (GSI) INFO: instno   = "6120023288"
    (RTF) ########## WARNING ###########
            Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
    (RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: cannot find version token "ver:" at line 1
    (RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: unknown file format, assuming version 2
    (EXP) INFO: table REGUC will be exported with sorting (task modifier)
    ------------------ C-STACK ----------------------
    [0] t_splay ( 0x1020df850, 0xb3, 0x4386, 0x100a02078, 0x0, 0x1020df870 ), at 0xffffffff7b9629
    94
    [1] t_delete ( 0x1020df850, 0x4348, 0x1d9870, 0x1000d0408, 0xffffffff7bb3c000, 0x0 ), at 0xff
    ffffff7b9627e4
    [2] realfree ( 0x101ee7590, 0x1f82b1, 0x1d9cd0, 0x1f82b0, 0xffffffff7bb3c000, 0x101ee7590 ),
    at 0xffffffff7b9623b0
    [3] _malloc_unlocked ( 0x7d40, 0x200000, 0x101edf840, 0x0, 0x101ee7580, 0x0 ), at 0xffffffff7
    b961eb4
    [4] malloc ( 0x7d39, 0x2388, 0x1da428, 0x10038fe84, 0xffffffff7bb3c000, 0x2000 ), at 0xffffff
    ff7b961c28
    [5] rstg_get ( 0x2, 0x0, 0x2, 0x7d10, 0x0, 0x10077d8c0 ), at 0x10038ff4c
    [6] c3_uc_new_cache ( 0x100a02078, 0x284db0, 0x284c00, 0x10077d8c0, 0x100a02108, 0xb3 ), at 0
    x1000d1ce8
    [7] c3_uc_seek_cache ( 0xb3, 0xff79, 0xffffffff7ffcae3e, 0x100a02078, 0x10189fa48, 0x10077d8c
    0 ), at 0x1000d188c
    [8] c3_uc_new_tabcache ( 0x0, 0xb3, 0x4386, 0x100a02078, 0xb3, 0x10077d8c0 ), at 0x1000d13fc
    [9] c3_uc_insert_record_in_cache ( 0xffffffff7ffcb04e, 0x10189fa48, 0x100a02078, 0x100a024c8,
    0xb3, 0x1058c8f84 ), at 0x1000d0408
    [10] c3_uc_insert ( 0x0, 0x100a02078, 0x0, 0x0, 0x10077d8c0, 0xffffffff7ffcb04e ), at 0x1000c
    f944
    [11] c3_uc_convert_table_entry ( 0x1015c61f8, 0x0, 0x100a02078, 0x0, 0x10189f408, 0x31a000 ),
    at 0x1000ce314
    [12] c3_uc_convert_logic_table ( 0x1015c61f8, 0x100a02078, 0x0, 0x4a, 0x100638dc0, 0x10077d8c
    0 ), at 0x1000cdb18
    [13] c3_uc_convert_cluster_data ( 0x100a02078, 0xffffffff7ffcbc50, 0x1015c6428, 0x1015c61f8,
    0x10077d8c0, 0x0 ), at 0x1000cd10c
    [14] c3_uc_convert_cluster_item ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x1038
    6f6e0, 0xffffffff7ffcbb8c, 0x100a02812 ), at 0x1000be1d4
    [15] process_task ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x100a02810, 0x10063
    32e0, 0x10077d8c0 ), at 0x1000b2f58
    [16] CnvCluster ( 0x1014642d0, 0x100954670, 0x100aa9610, 0x2849b8, 0x284800, 0x6cb978 ), at 0
    x1000b1f8c
    [17] cnv_clust2 ( 0x100aa9580, 0xffffffff7ffcc258, 0x100954770, 0xfc0, 0x107d00, 0x100954670
    ), at 0x100062714
    [18] cnv_cp ( 0x100aa9580, 0xffffffff7ffcc258, 0x100aa95e0, 0x0, 0x10077d8c0, 0x1d6c00 ), at
    0x100064644
    [19] process_buffer ( 0x100aa9580, 0xffffffff7ffcc258, 0xfff00, 0x100a97bd0, 0x10, 0x100aa95b
    0 ), at 0x10007162c
    [20] execute_table_unload ( 0xffffffff7ffed610, 0xffffffff7ffdc4b0, 0x0, 0x100aa9580, 0xfffff
    fff7ffcc258, 0x10077d8c0 ), at 0x10006c488
    [21] export_table_task ( 0xffffffff7ffed610, 0x0, 0xffffffff7ffdc368, 0xffffffff7ffcc330, 0xf
    fffffff7ffeedb8, 0xffffffff7ffeec60 ), at 0x10006c934
    [22] db_unload ( 0x100a97b0d, 0xffffffff7ffed610, 0x0, 0x10077d8c0, 0xffffffff7ffeec60, 0xfff
    fffff7bb47540 ), at 0x10006d148
    [23] main_r3ldmain ( 0x72ec00, 0xffffffff7ffff448, 0xffffffff7ffff228, 0xffffffff7bb47540, 0x
    1005fc290, 0x0 ), at 0x1000514e0

  • CcmSetup is exiting with return code 0 Need Help

    Installing SCCM Client on Window 7 Machine, Examining the log file, this caught my eye. 
    <![LOG[Successfully deleted the ccmsetup service]LOG]!><time="13:58:26.463-480" date="05-09-2014" component="ccmsetup" context="" type="1" thread="3656" file="ccmsetup.cpp:3345">
    <![LOG[0]LOG]!><time="13:58:26.463-480" date="05-09-2014" component="ccmsetup" context="" type="1" thread="3656" file="ccmsetup.cpp:9763">
    <![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.xml]LOG]!><time="13:58:26.463-480" date="05-09-2014" component="ccmsetup" context="" type="1" thread="3640" file="ccmsetup.cpp:9493">
    <![LOG[Task 'Configuration Manager Client Upgrade Task' does not exist]LOG]!><time="13:58:26.463-480" date="05-09-2014" component="ccmsetup" context="" type="0" thread="3640"
    file="wintask.cpp:634">
    <![LOG[CcmSetup is exiting with return code 0]LOG]!><time="13:58:26.463-480" date="05-09-2014" component="ccmsetup" context="" type="1" thread="3640" file="ccmsetup.cpp:10875">
    I search around this error code 0, But it seems mine is a different issue? The clients installs normally as usual, but can't see any software updates and such.
    Could the Error Code 0 have cause this also? Need guidance on this matter. 

    You just haven't waited long enough after agent installation. Agent installation and agent communication with the site are two separate things. After successful installation, the agent still has to find the site, register with it, download policies, and
    evaluate policies. This all takes a few minutes initially and after every reboot.
    You can check policyagent.log and policyevaluator.log to see all of the "fun" as far as policy goes.
    Jason | http://blog.configmgrftw.com
    Yea I was checking all the log files specific by everyone here, nothing seems wrong or out of the ordinary. Thanks for your help, and also everyone else here, Sorry I took so long to get back to this post.  

  • RMAN exited with return code '3' ?

    I get message bellow while oracle backup to the tape.
    (2960) Launching backup process
    (2960) Backup process failed: RMAN exited with return code '3'.
    (2960) nwora_nsrnmostart_rman: RMAN script execution is not successful. RMAN exited with return code '3'.
    There is no description for the code '3'. I think it is networker license problem but i am not sure.
    Any advice ?

    Thank you,
    yes i am. I have 10 clients and they are working fine.
    I think problem is that i have just one license of oracle module for windows. Another windows client is set and working. I can't find any documentation related to error code '3'.
    a test rman script is very simple:
    connect target sys/*****
    connect rcvcat rman/***@vas
    run {
    allocate channel d1 type 'sbt_tape';
    release channel d1;
    I get no errors in rman. It just stops at allocate channel d1 type 'sbt_tape';
    error is stored in NSR log file.

  • RMAN Backup is failling with "RMAN exited with return code '1' " via tape.

    Hi Everyone,
    Backups are getting failed continously with below error.can you plese suggest me what is problem exactly
    L1_OracleL1_Daily completed
    Failed:  ***-rac-a16-001-vip.*****.dom*
    --- Unsuccessful Save Sets ---
    ** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup savegrp: suppressed 43 lines of output.*
    ** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup*
    ** ***-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup Recovery Manager complete.*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup The backup process failed:*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup RMAN exited with return code '1'.*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup Exiting with error:*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup RMAN exited with return code '1'.*
    ****-rac-a16-001-vip.uidl1.dom: RMAN exited with return code '1'.*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup nsrnmostart returned status of 255*
    ** ***1-rac-a16-001-vip.uidl1.dom:RMAN:/nsr/res/Daily_IncrDB_Backup /usr/sbin/nsrnmobkp exiting.*
    Thanks,
    Prasanth

    Hi Hemanth/imran,
    storage team is shown below error for failure of backup in their log.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-12502: TNS:listener received no CONNECT_DATA from client
    Recovery Manager complete.
    The backup process failed:
    RMAN exited with return code '1'.
    Exiting with error:
    RMAN exited with return code '1'.
    uidl1-rac-a16-001-vip.uidl1.dom: RMAN exited with return code '1'.
    Any changes we need to do
    Thanks,
    Prasanth

  • Tranport control program ended with return code 0012

    Hi,
    When i realesed the associate transport request it went very well. Then when i try to run orginal transport request number it iam getting message as tranport control program ended with return code 0012.
    Regards,
    Asif

    Hi Asif,
    There can be many reasons behind that, check the logs file in \usr\sap\trans\log
    Check whether you have free space or not.  Check in for permission for request in data and cofiles folder.
    Check background jobs related to transport.
    Cheers
    Deepanshu

  • SAP ECC error:'Migration Monitor' exits with error code 103.

    Hi All,
    I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
    I am stuck at the import ABAP.Getting error
    ERROR 2008-08-08 16:10:53
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    1) imort_monitor.java.log-->contains
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
    Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
    Loading of 'SAPVIEW' import package: ERROR
    Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
    2)import_monitor.log
    ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPVIEW' import package is interrupted with R3load error.
    Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
    For mode details see 'SAPVIEW.log' file.
    Standard error output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    INFO: 2008-08-08 16:10:52
    All import packages are processed.
    WARNING: 2008-08-08 16:10:52
    1 error(s) during processing of packages.
    INFO: 2008-08-08 16:10:52
    Import Monitor is stopped.
    3)SAPVIEW.log
      error message returned by DbSl:
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001"  ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001",  T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
    DbSlExecute: rc = 103
      (SQL error -942)
      error message returned by DbSl:
    (DB) INFO: disconnected from DB
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
    D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
    Only SAPDB: SAPSID srvice of SAP DB is only up.
    No other services of database are  up.And i am not able to up the other services also.
    Is it required to up the other services?
    If not?
    Why this error is occuring?
    Any help will be appreciated.
    Thanks&Regards
    Manisha das

    Hello Manisha,
    The one of the possible reasons for this is due to lack of H/W.
    Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
    If the issue is with H/W, then this should fix the issue.
    Hope it helps,
    Regards,
    Satish.

  • SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

  • Test call of transport control program (tp) ended with return code 0200 Message no. TK094

    Hello Expert,
    My SAP System environment as follow
    SAP Product : SAP NetWeaver 04
    Operating System : Windows 2003 32 bit
    SAP Database : MS SQL 2005 32 bit
    I have installed SAP NetWeaver 04 system with system copy option. I have installed Application server & Database server on different physical server. App server : SSC2PAS3SFWBW and Database Server : SSC2PAS3SFSQW1.
    After SAP NetWeaver 04 installation with system copy I have done TMS configuration with virtual system for a test, It is working fine but while releasing request form SFD system (Development system) it get error  “Test call of transport control program (tp) ended with return code 0200. Message no. TK094”
    I have reconfigured the TMS and check but it can’t help. TR gets release and import with OS level but at SAP level it gets error.
    Trans --> Log
    1 ETP199 ######################################
    1 ETP199X######################################
    1 ETP182 CHECK WRITEABILITY OF BUFFERS
    1 ETP101 transport order     : "SFDK905838"
    1 ETP102 system              : "SFD"
    1 ETP108 tp path             : "tp"
    1 ETP109 version and release : "340.16.72" "640"
    1 ETP198
    2EETP128 No target system defined. "SFDK905838" is not a transport request.
    1 ETP182 CHECK WRITEABILITY OF BUFFERS
    1 ETP110 end date and time   : "20140602150208"
    1 ETP111 exit code           : "12"
    1 ETP199 ######################################
    Steps for Reconstruction                                            
    # Upgraded latest SAP Kernel Non-Unicode 640_Rel Patch level 404
    # Reconfigured the TMS
    # Full User Permission has been set to all SAP Directory.        
    Rgds,
    Ashok      

    Hi Ashish,
    I have removed virtual system form TMS and configured with Development & Production system, but the same error. Not able to release TR.
    SLOG as below.
    ERROR SFDK905832           SFD f 0012 20140602090930 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602093923 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602094059 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602102854 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602103633 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602104142 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602111140 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602112723 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113109 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113704 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113722 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113753 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905832           SFD f 0012 20140602113809 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905834           SFD f 0012 20140602125959 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905834           SFD f 0012 20140602130035 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    START EXPORT PREPARATION   SFD e      20140602132917              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    START tp_getprots          SFD E      20140602132917              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    STOP  tp_getprots          SFD E      20140602132920              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    STOP  EXPORT PREPARATION   SFD e      20140602132920              sfdadm       SSC2PAS3SFWBW 20140602132916001358
    ERROR SFDK905836           SFD f 0012 20140602133526 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905836           SFD f 0012 20140602133540 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144313 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144350 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602144430 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602150202 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140602150208 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603080634 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603081006 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603083952 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905838           SFD f 0012 20140603084005 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603091608 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603091617 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905842           SFD f 0012 20140603091826 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603093805 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603101944 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603102709 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603114753 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603121948 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603122039 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603123438 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603135937 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140114 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140233 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603140339 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603141743 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905840           SFD f 0012 20140603150924 default_user BASIS@ORIGIN SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603152403 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603152753 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603153518 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162013 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162544 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162639 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603162755 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603163347 default_user A559420      SSC2PAS3SFWBW                    
    ERROR SFDK905844           SFD f 0012 20140603163740 default_user A559420      SSC2PAS3SFWBW                    
    Rgds,
    Ashok

  • Transport control program (tp) ended with return code 0200

    Hi Gurus,
    Please help, we have a fresh system copy of our prod. I already configure new domain controller with one virtual system. it was meant for 2 system lanscape. PRD -> VIR. The problem now is everytime we try to release a config it shows an error
    "Test call of transport control program (tp) ended with return code 0200"
    System error shows that calling   "C:\>tp EXPCHK BWPK900060 pf=
    SCWOSAPBW3\sapmnt\trans\bin\TP_DOMAIN_BWP.PFL -Dtransdir=
    SCWOSAPBW3\sapmnt\trans" Error text from tp: ERROR: Buffer check failed.
    But doing it in OS level it has no issues
    C:\>tp EXPCHK BWPK900060 pf=\\SCWOSAPBW3\sapmnt\trans\bin\TP_DOMAIN_BWP.PFL -Dtr
    ansdir=\\SCWOSAPBW3\sapmnt\trans
    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.63 (release 640)
    createinfo succeeded
    Buffer check succeeded
    tp finished with return code: 0
    meaning:
      Everything OK
    STMS are all ok connection test, transport directory test and transport tool test.
    Kindly help me to resolve issue.
    OS platform is windows 2003, Netweaver 04 640, MSSQL2005.
    Thank you in advance.
    Joel

    Hi Anil,
    Here is the result after the tp check all command.
    D:\usr\sap\trans>tp check all pf=d:\usr\sap\trans\bin\TP_DOMAIN_SID.PFL
    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.63 (release 640)
    check>Log file is written to \\hostname\sapmnt\trans\tmp\CHECK.LOG
    check>
    check>Collected 3 filenames from [\\hostname\sapmnt\trans\buffer\.]
    check>Collected 2 Systemnames from [\\hostname\sapmnt\trans\buffer\.]
    check>Collected 00001 out of 00001 entries from buffer BWP.
    check>Collected 00001 entries from buffers
    check>
    check>Collected 1 filenames from [\\hostname\sapmnt\trans\cofiles\.]
    check>Found 0 invalid filenames on Cofile-directory
    check>
    check>
    check>Collected 1 filenames from [\\hostname\sapmnt\trans\data\.]
    check>Found 0 invalid filenames on Datafile-directory
    check>
    check>Collected 14 filenames from [\\hostname\sapmnt\trans\log\.]
    check>Found 2 invalid filenames on Logfile-directory
    check>
    check>Collected 3 filenames from [\\hostname\sapmnt\trans\sapnames\.]
    check>
    check>WARNING: BWPK900060 has status T_STEP_UNKNOWN in  sapnames/TEST
    check>WARNING: BWPK900058 has status T_STEP_UNKNOWN in  sapnames/TEST
    check>WARNING: BWPK900056 has status T_STEP_UNKNOWN in  sapnames/TEST
    check>WARNING: SAPKD64038 has status T_STEP_UNKNOWN in  sapnames/SAPUSER
    check>WARNING: BWPK900060 has status T_STEP_UNKNOWN in  sapnames/SUPPORT
    check>Elapsed time 0m 1s
    tp finished with return code: 0
    meaning:
      Everything OK
    Kindly advise on what to do next.
    Thank you.
    joel
    Edited by: Joel Cancio on May 31, 2010 11:47 AM

  • Error: Test call of transport control program (tp) ended with return code 0

    Hi Experts,
    When we are trying to transport Request.
    Error: Test call of transport control program (tp) ended with return code 0208
    in STMS what are the steps to fallow to just back up the code.
    Any Solutions is Greatly Appreciable...
    Thanks in Advance,
    Ram,

    Hi,
    a)If your system is UNIX check /usr/sap/trans is mounted or not?
    b)After configuring TMS did you save and activate?that can be one reason.
    c)tp might be corrupted.u need to upgrade your tp. (or you can upgrade to the latest kernel)
    Please check the below link
    could not start transport control program tp
    However as suggested by NIbu, you should restart the server once before doing any other checks
    Thanks
    Debdeep
    Edited by: Debdeep  Ray on Jul 13, 2009 4:28 PM

  • Test call of transport control program (tp) ended with return code 0249

    Hi,
    When i release a TR i get the following error
    Pls let me know of what can be the reason for the same
    I did a kernel upgrade 2 days back
    Test call of transport control program (tp) ended with return code 0249
    Message no. TK094
    Diagnosis
    Your transport request could not be exported, since all requirements were not fulfilled.
    Calling the transport control program tp
       "tp EXPCHK BWDK900308 pf=
    WDBSSAPBWD01\sapmnt\trans\bin\TP_DOMAIN_BWD.PFL -Dtransdi"
    which checks the export requirements, returned the following information:
    Return code from tp: 0249
    Error text from tp: ERROR: No connect due to DbSl Load Lib Failure
    System Response
    Further processing is terminated.
    Procedure
    Check the following points:
    u2022     Feasibility of the transport control program tp
    u2022     Parameter settings in the transport profile
    u2022     Availability of the transport directory and the subdirectories (cofiles, data, log, sapnames, bin)
    u2022     Write authorization for the subdirectories
    u2022     Write authorization for the files of the subdirectories cofiles, data, log, sapnames
    Release the request again when the error has been removed

    Hi Balaji,
    End of your question contains the areas to be varified.
    Your SAP seems to be installed in windows environment
    Check transport profile paramater and file permissions.
    Try to browse the directory
    WDBSSAPBWD01\sapmnt\trans\bin\ from start->run
    Check with tp connecting to DB  with tp connect <SID>
    chceck file permission to datafile and cofiles (in case of OS UNIX)
    Regards,
    Ganesh

  • Error in transport, ended with return code:  12,  job RDDEXECL cancelled

    Hi Friends,
    When I am trying to import a request in a BW preproduction system, it is giving below error: However, the transport is imoprted successfully in Quality.
    ===================================
    Program terminated (job: RDDEXECL, no.: 09222300)
       See job log
    Execution of programs after import (XPRA)
    End date and time : 20080509092238
    Ended with return code:  ===> 12 <===
    Job log:
    Date        Time      Message
    09.05.2008  09:22:23  Job started
    09.05.2008  09:22:23  Step 001 started (program RDDEXECL, variant , user ID DDIC)
    09.05.2008  09:22:23  All DB buffers of application server unix0001 were synchronized
    09.05.2008  09:22:25  ABAP/4 processor: UNCAUGHT_EXCEPTION
    09.05.2008  09:22:25  Job cancelled
    =======================================
    Kindly advice.
    Thanks & regards,
    Kunal Patel.

    Hello,
    I ran a search for this error and found the following notes:
    SAP Note 966234 - 70SP10: DTP transport and content error
    SAP Note - 1074388 SAPBINews NetWeaver 7.0 BI Support Package 16
    Check if they are relevant for your system.
    Regards,
    Siddhesh

  • Transport Request Ended with return code:  === 12 ===

    Hi
    Good day to you.
    We are able to move Transport Request from Development BW Client (with respect to an SEM-BCS Configuration) to Quality BW Client smoothly.
    But when we move the same TR to Production client, we are getting the following error message. I would be very grateful if somebody could throw light on why it is happening, what could be its implications and what to do to avoid the same
      Execution of programs after import (XPRA)
      Transport request   : DBWK901288
      System              : PBW
      tp path             : tp
      Version and release: 340.16.37 640
      Post-import methods for change/transport request: DBWK901288
         on the application server: sapbwpd
      Post-import method FINB_TR_AFTER_IMP_METHOD started for UCREPGROUP T, date and time: 20081029144344
      Post-processing taking place in client 300
      Import carried out using RFC destination PBWCLNT300
      Communication error: Destination PBWCLNT300 -> long text
      Errors occurred during post-handling FINB_TR_AFTER_IMP_METHOD for UCREPGROUP T
      FINB_TR_AFTER_IMP_METHOD belongs to package FINB_TRANSPORT_TOOL
      The errors affect the following components:
         FIN-FB (Financials Basis)
      Post-import method FINB_TR_AFTER_IMP_METHOD completed for UCREPGROUP T, date and time: 20081029144351
      Post-import methods of change/transport request DBWK901288 completed
           Start of subsequent processing ... 20081029144344
           End of subsequent processing... 20081029144351
      Execute reports for change/transport request: DBWK901288
         on the application server: sapbwpd
      There are no reports to execute
      Execution of programs after import (XPRA)
      End date and time : 20081029144351
      Ended with return code:  ===> 12 <===
    Regards
    Siddique

    Hi Siddique,
    Looks like your RFC destination is wrong. The proper syntax is FINBTR@<system>CLNT <client>.
    See also the note 644610.

Maybe you are looking for