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.  

Similar Messages

  • 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

  • [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

  • 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.

  • 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.

  • 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.

  • Backng up failed with return code 255 ...Help!!!

    Hi,
    I am in a process of backing up Oracle application server 10g through "Configure Backup/Recovery Settings" feature of the app server, when I provide the directories for:
    1. Log File Location     
    2. Configuration Files Backup Location     
    3. Metadata Repository Database Backup Location
    4. Metadata Repository Database SID
    and click on OK it provides me the following error:
    "The command <ORACLE_HOME>/perl/5.6.1/bin/MSWin32-x86/perl.exe <ORACLE_HOME>\backup_restore/bkp_restore.pl -m configure -h <ORACLE_HOME> -f > <ORACLE_HOME>\backup_restore\logs/2008-12-06_13-36-02_output.log failed with return code 255"
    And the log file says -"Unable to get dbid from the database."
    Please Help..!!!
    Thanks

    This turns out to be a non-issue. I re-installed JDK 1.6,
    thinking this might have been the problem, but as it turns out,
    this Windows machine was a VM, and there haven't been any issues
    with other VM's, only this one, leading me to conclude the problem
    was the VM. We've since migrated off this machine and recycled
    it.

  • 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

  • Importing error Ended with return code:  === 8 ===

    Hi Experts,
    I am trying to transporting an infoobject 0EMPLOYEE from Dev to Production.While importing the request I am getting an error like
    Execution of programs after import (XPRA)
    Transport request   : BD1K901543
    System              : BP1
    tp path             : tp
    Version and release: 372.04.36 700
    Execution of programs after import (XPRA)
    End date and time : 20090206164251
    Ended with return code:  ===> 8 <===
    after expanding this error msg i am getting
    Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Activation Mode)
    Characteristic 0CM_CTAR: Unit 0UNIT_DIM no allowed in compounding
    Characteristic 0CM_SHAR: Unit 0AREA_UNIT no allowed in compounding
    by clicking on the error mag
    Diagnosis;
    If the characteristic is used in an InfoProvider with dimensions (for example, an InfoCube or MultiProvider), the compounded unit is not unique if currency key figures are used at the same time.
    System Response
    This type of modeling is not supported.
    Procedure
    Replace the currency with a different characteristic. If you nevertheless want to use a unit in the compounding, you should use the modeling of a characteristic that semantically represents a unit. To do so, copy the technical properties of the unit of measure or the currency.
    How can I solve this problem?
    Can add any other char to this compounding char is it works?if yes which currency char i need to add here?
    Thanks & Regards,
    Sridhar

    Hi Sridhar,
            I am facing the problem with 0CM_CTAR and 0CM_SHAR. both the characteristics are not allowed compouding ATTRIBUTES.
      0cm_ctar not allowed comp .attr of 0unit_dim
      0cm_shar not allowed comp.attr 0f area_unit.
    for this reason what i need to do. Please give me help on this.
    sridhar could you give me solution what i need to do. i am also implement  same sap note or any other solution you have.
    Please kindly give me reply.
    Thnaks,
    Guna.
    Edited by: gunasekhar raya on Apr 14, 2009 6:16 PM

  • Transport with return code 12 ,short dump with 'DBIF_RSQL_SQL_ERROR'

    Dear All,
    My trasnport contains infoprovider. DTP,transpformations, character realtionships , aggregation levels ,web templates, programs.
    I got a transport failed with Return code 12, and it is showing message :
    Program terminated (job: RDDEXECL, no.: 06031600)
       See job log
    Execution of programs after import (XPRA)
    End date and time : 20101026060421
    Ended with return code:  ===> 12 <===
    I have short dump with 'DBIF_RSQL_SQL_ERROR' exception 'CX_SY_OPEN_SQL_DB'.
    in how to correct the error :
    below is the detials.
    Database error text........: "ORA-01578: ORACLE data block corrupted (file #
    211, block # 79950)#ORA-01110: data file 211:
    '/oracle/RBW/sapdata15/xbw_188/xbw.data188'#ORA-26040: Data block was loaded
    using the NOLOGGING option"
    did someone has the same problem .
    Help is really appreciated.
    Regards
    Veera

    I am afraid you will need to esclate this to BASIS team.. seems some issue with database

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

    Hi all,
    When I am trying to import a request in a BW system from development to quality , it is giving below error:
    Program Terminated (job:RDDEXCEL no:11315700) messg no:TR012
    Please do needful
    Thanks and Regards,
    srinivas.m

    Hi Gurus,
    I have the same error "Error in transport, job RDDEXECL cancelled, ended with return code: 12" (Programa cancelado (job RDDEXECL, nº 09292900)).
    I have checked all the steps that are in the "Note 1101187 - The OLAP tunnel" and they are implemented.
    Find below the information about my BW system:
    SAP_ABA     700     0024     SAPKA70024     Componente multiaplicaciones
    SAP_BASIS     700     0024     SAPKB70024     Sistema Base SAP
    PI_BASIS     2005_1_700     0024     SAPKIPYJ7O     PI_BASIS 2005_1_700
    ST-PI     2008_1_700     0004     SAPKITLRD4     SAP Solution Tools Plug-In
    SAP_BW     700     0026     SAPKW70026     SAP NetWeaver BI 7.0
    BI_CONT     703     0016     SAPKIBIIQ6     Business Intelligence Content
    ST-A/PI     01N_700BCO     0000          -     Servicetools for other App./Netweaver 04
    I am trying to transport "Business Content (Statistics)", if this information can help you.
    What can i do to solve the problem? I am finding some clue and i dont find anything. It will be much appreciated any idea to solve the problem.
    Thanks in advance and kind Regards,
    Manuel
    Edited by: Manuel Guijarro on Oct 11, 2011 3:46 PM

  • Transport request migration failed with return code 12

    Hi ,
    A transport request was created to capture deletion of bex query via Tcode RSZDELETE. The deletion TR was moved to Quality box successfully and query got deleted. But when same TR was moved to Production box, TR failed with return code 12. Program terminated (job:RDDEXECL). Upon checking the job log overview for this job, runtime error ITAB_DUPLICATE_KEY happend causing session to terminate. can anyone pls suggest me how to fix this issue and why this has caused. Need to fix this immediately as it is in production environment. Please help.
    In ST22 i could see the below error details:
    Thanks,
    Vishnu

    as per the dump, system is trying to insert a unique number which is already in the system. You sure the transport is only for deletion of the query? Can you please check the import logs in the test system and should tell you what action performed during import.

  • MS14-082 (kb2596927) with return code: 17022

    The installation for MS14-082 (kb2596927) was not successful with return code: 17022. What could be the cause why the security did not install? Currently Microsoft
    Suite 2007 Service Pack 3 is installed. Thanks in advance!

    Hi Sir,
    As far as I know, if we get the return code 17022, the update usually has installed successfully and we may need to reboot the pc. Please see the part of KB2596927:
    ===
    Restart information
    You may have to restart the computer after you install this security update.
    In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message is displayed that advises you to restart the computer.
    To help reduce the possibility that a restart will be required, stop all affected services and close all applications that may use the affected files before you install this security update.
    ===
    The required files were being used with the special test-machine, thus, the return code was appeared.
    Then, do you mind telling me how do you install the update? Install them manually, use deployment tools or deployment scripts?
    If you are using deployment tools/scripts, I recommend you download the update to local disk and then install with the special test-machine. We can check it if it is installed successfully in Windows update center (Control Panel\Programs\Programs and Features\View
    Installed Updates)
    If the update still install failed, we may collect the various logs to do further troubleshooting.
    https://technet.microsoft.com/en-us/library/cc511506(v=office.12).aspx
    Hope it's helpful.
    Regards,
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Transport Ended with Return code error = 8? What we do now?

    Hi all,
    I was trying to transport the Update rules from Development system to Production system.
    But in the middle it got failed in Quality system & given the error as mentioned below.
    "Ended with Return code = 8".
    What we need to do now.
    Please Give ur valuable suggestions.
    Thanks in Advance.

    Hi,
    Pleas make sure that the target and the source for the update rules are present in the Quality sytem and are activated. if they are not present or are in inactive state then u need to transport them first and later on update rules.
    Sometimes what haapens is source and targets object for the update rules are present in the quality system and we make some changes in them in development and after making changes forget to transprt the changed request for source target and directly try to transport update rules which fails giveing an error. so jst make sure that the version in Development and the quality system for the both the source and targets objects are exactly same.
    i guess there would be one among the two cases mentioned above but still if its not the case then see wat error are u getting provide us the exact error so that we can be of more help to you.
    Assign points if applicable
    Thanks
    Puneet

Maybe you are looking for

  • Installed new hard drive, can't install OSX - help!

    I just installed a new 500GB hard drive in my 2008 late model unibody MacBook (not pro). I inserted the original OSX install disk (snow leopard, I think), but the disk isn't recognized. The screens white, with a blinking gray folder icon with a quest

  • How to make use of communication method in output type for new smartform?

    Hi all, My requirement, send the smartform to the carrier by fax/email/print based on the output condition records created. Here are the things that I had done. 1) created a ZSMARTFORMS - smartforms 2) created a ZPRINTPROGRAM - print program 3) creat

  • Display problem

    Product name-15-p001TX Operating systems-Windows 8.1  Respected to whom so ever is concern,      In my notebook pc i have an display problem, some times while working on it, it blinks automatically. sometimes it is bright and some times it is lite. T

  • WiFi or Safari?

    I don't think I'm having problems with the Wi-Fi but instead this is a Safari problem. When I'm at the university, they have this login screen to input your username and password, nothing new, I do it everyday either on the Macbook or in the iPhone.

  • Problems with restoring - computer or iphone??

    I have recently had my iphone repaired after a few knocks and bangs. When turning it back on it says i have to connect to itunes. but when i do (and try to restore the iphone) it just keeps saying it wont. an error message comes up saying it wont res