SAP DB installation failed!

Hi ,
i am installing content server & cache server on my machine.
while installing i am getting the following error:
"SAP DB installation failed"
i had uninstalled once, and renamed the SAP DB to run the installtion only to find the above mentioned error.
what could be the problem?
Any inputs would be highly appreciated.
Thanks,
Ravi

hi sunil,
I m also facing the same problem, i m installing SAP content server in a Windows XP machine with 1 GB RAM and Enough HD space.
While installtion it give me SAP DB installation (SID) Failed.
Kindly suggest ASAP

Similar Messages

  • SAP NW7.0 SR3 Java AddIn Installation failed at "Import Java dump"

    Dear all,
    I get an error at Java AddIn Installation SAP Netweaver 7.0 SR3
    (Software Life-Cycle Option -> Java Add-In for ABAP -> Oracle ->
    Central System ->)
    The first installation step "Central Services Instance (SCS) Java Add-
    In" I have installed it without errors.
    The Installation failed at 2nd step "Database Instance Java Add-In" at phase 11
    of 14 "Import java dump":
    26.05.09 15:16:46 com.sap.inst.jload.Jload main
    INFO: Jload -sec
    Q2B,jdbc/pool/Q2B,/usr/sap/Q2B/SYS/global/security/data/SecStore.properties,/usr/sap/Q2B/SYS/global/security/
    data/SecStore.key -
    dataDir /usr/sap/swdc/51033513/DATA_UNITS/JAVA_EXPORT_JDMP -
    job /tmp/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN
    /ORA/CENTRAL/DB/IMPORT.XML -log jload.log
    26.05.09 15:16:47 com.sap.inst.jload.Jload main
    SEVERE: couldn't connect to DB
    26.05.09 15:16:47 com.sap.inst.jload.Jload logStackTrace
    SEVERE: java.sql.SQLException: Io exception: The Network Adapter could
    not establish the connection
    at oracle.jdbc.driver.DatabaseError.throwSqlException
    (DatabaseError.java:112)
    at oracle.jdbc.driver.DatabaseError.throwSqlException
    (DatabaseError.java:146)
    at oracle.jdbc.driver.DatabaseError.throwSqlException
    (DatabaseError.java:255)
    at oracle.jdbc.driver.T4CConnection.logon
    (T4CConnection.java:387)
    at oracle.jdbc.driver.PhysicalConnection.<init>
    (PhysicalConnection.java:420)
    at oracle.jdbc.driver.T4CConnection.<init>
    (T4CConnection.java:165)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection
    (T4CDriverExtension.java:35)
    at oracle.jdbc.driver.OracleDriver.connect
    (OracleDriver.java:801)
    at
    com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection
    (NativeConnectionFactory.java:215)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection
    (OpenSQLDataSourceImpl.java:522)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection
    (OpenSQLDataSourceImpl.java:276)
    at com.sap.inst.jload.db.DBConnection.connectViaSecureStore
    (DBConnection.java:105)
    at com.sap.inst.jload.db.DBConnection.connect
    (DBConnection.java:149)
    at com.sap.inst.jload.Jload.main(Jload.java:580)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
    (NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sap.engine.offline.OfflineToolStart.main
    (OfflineToolStart.java:81)
    the database is up and running, the Oracle Listener is also working well.
    Any idea??
    Thanks so much in advance!
    Best Regards,
    Gerd

    Hi Sunny, hi Markus!
    many thanks for your hints!
    I've just solved the problem. The problem was, our Listener was not configured correctly.
    I've adjusted the listener.ora, tnsnames.ora to the correct hostname - cause, we had a hostname-switch last month and I had forgotten to adapt the Listener...
    now the Listener is running as well:
    mcho35au:oraq2b 120% lsnrctl status LISTENER_Q2B
    LSNRCTL for Solaris: Version 10.2.0.4.0 - Production on 30-MAY-2009
    09:52:48
    Copyright (c) 1991, 2007, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=Q2B.WORLD))
    STATUS of the LISTENER
    Alias LISTENER_Q2B
    Version TNSLSNR for Solaris: Version 10.2.0.4.0 -
    Production
    Start Date 30-MAY-2009 09:52:15
    Uptime 0 days 0 hr. 0 min. 32 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /oracle/Q2B/102_64/network/admin/listener.ora
    Listener Log
    File /oracle/Q2B/102_64/network/log/listener_q2b.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=Q2B.WORLD)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=Q2B)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mcho35au)(PORT=1527)))
    Services Summary...
    Service "Q2B" has 1 instance(s).
    Instance "Q2B", status UNKNOWN, has 1 handler(s) for this service...
    Service "Q2B.WORLD" has 1 instance(s).
    Instance "Q2B", status READY, has 1 handler(s) for this service...
    Service "Q2B_XPT.WORLD" has 1 instance(s).
    Instance "Q2B", status READY, has 1 handler(s) for this service...
    The command completed successfully
    meanwhile the step "Import java dump" has finished successfully!
    Thanks to all!
    Best Regards,
    Gerd
    Edited by: Gerd Schuster on May 30, 2009 10:29 AM

  • SAP Business One 9 on HANA - AddOn "AddOnName" Installation Failed

    Hi,
    I'm trying to install an add-on in a SAP Business One 9 on HANA (64 bits) but i'm facing a problem:
    - The add-on installation (from the add-on Manager Form) on windows finish correctly, but after a few seconds the system shows a Message box with "Please wait for add-on installation to finish .....Select Yes if installation finished succesfully, otherwise select No" . After that (YES option selection) the system shows "AddOn [AddOnName]: Installation Failed"
    The making of the .ard file (AddOn registration file) was the same that the generation of .ard file for the SAP Business One 9 for SQL Server (here the addon works correctly). The only difference was the replacement of the DI API dll, UI API dll, AddOnRegGenerator and the AddOnInstalAPI.
    Please Help!..
    Thanks...

    Hi,
    When generating the ard file for the installer, there is a property that defines whether the addon is a 64bit addon.
    https://websmp202.sap-ag.de/~sapidb/011000358700000247582013E/SDK_CompGuide_90.pdf
    Create Add On for 32 bit and 64 bit computer SAP Business One 9.0
    The above link may helpful to you.
    Regards,
    Silambu

  • Sap net Weaver Sneak preview edition installation Fails.

    Hi all,
    I couldn't finish the installation for SAP NetWeaver sneak preview installation.
    Installation failed in the IMPORT ABAP step.
    I have many Import package Errors .
    All the packages (18) SAPSSEXC, SAPAPPL1, SAPAPPL0, SAPSDIC... end up with errors.
    I have no idea Why.
    Log file is of no help to me.
    I have tried it several times already .
    But I am still stopped with the same error.
    Thanks if you have already experienced this pb .
    OS is Windows XP SP1 .
    Regards
    Yvon

    Hi All,
    We had the same problem when we installed Solution Manager 7.0, Oracle 10.2 and j2sdk 1.4.2_12.
    The problem was oracle was not running. We have to run oracle manually in command prompt.
    This is how when we resolved and worked fine. Follow these steps in command prompt.
    1. Check R3trans -d; If R3 finished with error(0012) follow the below steps.
        1.1 Check services.msc whether oracle listeners are started or not; if not please start.
    2. Go to oracle drive.    
    Use the following commands:
    3. sqlplus /nolog
    4. connect /as sysdba
    5. If result displays:
    "SQL> connect /as sysdba
    Connected to an idle instance.
    6. Use this command next: archive log list (i.e, SQL> archive log list)
    ORA-01034: ORACLE not available" - If this is the result, then startup the oracle.
    7. Use this command next: startup (i.e, SQL> startup)
    Then result should say: "ORACLE instance started."
    That means oracle instance is started successfully.
    Now, Retry the step where you left. It will work fine.
    Please let us know if you need any further details need.
    I know this thread was initiated long time back; but i want to share our experience with you. It may be helpful to someone later who encounters these kind of issues.
    Thanks and Regards,
    Sanjai Prabu Govindan

  • SAP EHP 1 for PI 7.1 Installer failed: runing 2 upgrades parallely

    Hi Friends
    I am doing an SAP EHPI Installer upgrade on one host machine from PI 7.1 to EHPi 1 PI 7.1
    while on the same host machine another upgrade is running 4.6 C to ECC 6.0.
    while i try to open my ehpi installer it opens the upgrade one with the bellow command.
    http://<host name>:4239
    can you help em out how can i run my ehpi installe without disturbing the other one.
    Regards
    Pooja

    the EHP folder creates and picks the port the one i will specify in the command line.
    Correct me if i understood you wrong.
    once i enter it that port entry will automatically get reflected in the
    D:\SP09\EHPI\sdt\htdoc\sdtdsu.jnlp
    do we have a note which says this.
    Currently it picks the default entry as shown below;
    <?xml version="1.0"?>
    <jnlp href="/sdtdsu.jnlp" codebase="http://HOSTEST.bcone.com:4239/" spec="0.2 1.0">
      <information>
        <title>SDTGui for EHPInstaller</title>
        <vendor>SAP AG</vendor>
        <description kind="short">SDTGui for EHPInstaller</description>
        <icon href="/pics/sdtgui_big.gif"/>
      </information>
      <security>
        <all-permissions/>
      </security>
      <resources>
        <j2se version="1.5+"/>
        <jar download="eager" href="/lib/sdt_compatibility.jar"/>
        <jar download="eager" href="/lib/sdt_engine.jar"/>
        <jar download="eager" href="/lib/sdt_gui.jar"/>
        <jar download="eager" href="/lib/sdt_util.jar"/>
        <jar download="eager" href="/lib/sdt_trace.jar"/>
      </resources>
      <application-desc main-class="SDTGui">
        <argument>host=HOSTEST.bcone.com</argument>
        <argument>port=4241</argument>
        <argument>service=DSUService</argument>
      </application-desc>
    </jnlp>
    Regards
    Pooja

  • Problem with services of SAP after installation of ABAP on MS SQL server

    Hi,
    I am trying top install 2004 Netweaver ABAP+ JAVA on my machine
    Following is my machine configuration -
    Machine type - Windows 2003 Standard Edition SP1
    Machine name - pun-idmqa-vm1
    SAP Instance name - QSA
    DB type - MS SQL 2000 SP4 + hotfixes and instcoll.exe is executed. After nstalling SQL shows server proper as SQL_Latin1_General_CP850_BIN2 collation
    Message port - 3600
    I could sucessfully install Database from CD and thereby could sucessfully install ABAP. During postinstall I tried to start the server. all the following services got up -
    msg_server.exe
    disp+work.exe
    igswd.exe
    But after some time 2nd service goes down. Following is the error message flashed in
    trc file: "dev_disp", trc level: 1, release: "640"
    Mon Jul 02 16:33:16 2007
    kernel runs with dp version 128000(ext=102000) (@(#) DPLIB-INT-VERSION-128000-UC)
    length of sys_adm_ext is 524 bytes
    systemid   560 (PC with Windows NT)
    relno      6400
    patchlevel 0
    patchno    31
    intno      20020600
    make:      multithreaded, Unicode
    pid        2492
    ***LOG Q00=> DpSapEnvInit, DPStart (00 2492) [dpxxdisp.c   1100]
    Mon Jul 02 16:33:17 2007
         shared lib "dw_xml.dll" version 31 successfully loaded
         shared lib "dw_xtc.dll" version 31 successfully loaded
         shared lib "dw_stl.dll" version 31 successfully loaded
         shared lib "dw_gui.dll" version 31 successfully loaded
    Mon Jul 02 16:33:21 2007
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  3886]
    MtxInit: -2 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: JAVA is not active
    DpShMCreate: sizeof(wp_adm)          10528     (1316)
    DpShMCreate: sizeof(tm_adm)          2780232     (13832)
    DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    DpShMCreate: sizeof(comm_adm)          290000     (580)
    DpShMCreate: sizeof(vmc_adm)          0     (372)
    DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 054B0040, size: 3192688)
    DpShMCreate: allocated sys_adm at 054B0040
    DpShMCreate: allocated wp_adm at 054B1B58
    DpShMCreate: allocated tm_adm_list at 054B4478
    DpShMCreate: allocated tm_adm at 054B44A0
    DpShMCreate: allocated wp_ca_adm at 0575B0E8
    DpShMCreate: allocated appc_ca_adm at 05760EA8
    DpShMCreate: allocated comm_adm_list at 05762DE8
    DpShMCreate: allocated comm_adm at 05762E00
    DpShMCreate: allocated vmc_adm_list at 057A9AD0
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 057A9AF8
    DpShMCreate: allocated wall_adm at 057A9B00
    MBUF state OFF
    EmInit: MmSetImplementation( 2 ).
    Mon Jul 02 16:33:22 2007
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 1024 kByte.
    Using implementation std
    <EsNT> Memory Reset enabled as NT default
    <EsNT> EsIUnamFileMapInit: Initialize the memory 1132 MB
    <ES> 1131 blocks reserved for free list.
    ES initialized.
    Mon Jul 02 16:33:36 2007
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 2.6.1 2.6 4.0) [dpxxdisp.c   1462]
    Mon Jul 02 16:33:38 2007
    ***LOG Q0K=> DpMsAttach, mscon ( pun-idmqa-vm1) [dpxxdisp.c   9719]
    Mon Jul 02 16:33:46 2007
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMsgAdmin: Set release to 6400, patchlevel 0
    Mon Jul 02 16:33:47 2007
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1025]
    DpMsgAdmin: Set patchno for this platform to 31
    Release check o.K.
    Mon Jul 02 16:34:20 2007
    ERROR => W0 (pid 2740) died [dpxxdisp.c   12170]
    ERROR => W1 (pid 3736) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xbf --> 0xbe
    ERROR => W2 (pid 3876) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xbe --> 0xbc
    ERROR => W3 (pid 3896) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xbc --> 0xb8
    ERROR => W4 (pid 3852) died [dpxxdisp.c   12170]
    ERROR => W5 (pid 2008) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xb8 --> 0xb0
    ERROR => W6 (pid 3776) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xb0 --> 0xa0
    ERROR => W7 (pid 4052) died [dpxxdisp.c   12170]
    my types changed after wp death/restart 0xa0 --> 0x80
    DP_FATAL_ERROR => DpWPCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    increase tracelevel of WPs
    killing W0-2740 (SIGUSR2)
    ERROR => DpWpKill(2740, SIGUSR2) failed [dpxxtool.c   2468]
    killing W1-3736 (SIGUSR2)
    ERROR => DpWpKill(3736, SIGUSR2) failed [dpxxtool.c   2468]
    killing W2-3876 (SIGUSR2)
    ERROR => DpWpKill(3876, SIGUSR2) failed [dpxxtool.c   2468]
    killing W3-3896 (SIGUSR2)
    ERROR => DpWpKill(3896, SIGUSR2) failed [dpxxtool.c   2468]
    killing W4-3852 (SIGUSR2)
    ERROR => DpWpKill(3852, SIGUSR2) failed [dpxxtool.c   2468]
    killing W5-2008 (SIGUSR2)
    ERROR => DpWpKill(2008, SIGUSR2) failed [dpxxtool.c   2468]
    killing W6-3776 (SIGUSR2)
    ERROR => DpWpKill(3776, SIGUSR2) failed [dpxxtool.c   2468]
    killing W7-4052 (SIGUSR2)
    ERROR => DpWpKill(4052, SIGUSR2) failed [dpxxtool.c   2468]
    NiWait: sleep (10000 msecs) ...
    NiISelect: timeout 10000 ms
    NiISelect: maximum fd=1629
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Mon Jul 02 16:34:30 2007
    NiISelect: TIMEOUT occured (10000 ms)
    dump system status
    Workprocess Table (long)               Mon Jul 02 11:04:30 2007
    ========================
    No Ty. Pid      Status  Cause Start Err Sem CPU    Time  Program  Cl  User         Action                    Table
    0 DIA     2740 Ended         no      1   0             0                                                             
    1 DIA     3736 Ended         no      1   0             0                                                             
    2 UPD     3876 Ended         no      1   0             0                                                             
    3 ENQ     3896 Ended         no      1   0             0                                                             
    4 BTC     3852 Ended         no      1   0             0                                                             
    5 BTC     2008 Ended         no      1   0             0                                                             
    6 SPO     3776 Ended         no      1   0             0                                                             
    7 UP2     4052 Ended         no      1   0             0                                                             
    Dispatcher Queue Statistics               Mon Jul 02 11:04:30 2007
    ===========================
    --------++++--
    +
    Typ
    now
    high
    max
    writes
    reads
    --------++++--
    +
    NOWP
    0
    3
    2000
    10
    10
    --------++++--
    +
    DIA
    5
    5
    2000
    5
    0
    --------++++--
    +
    UPD
    0
    0
    2000
    0
    0
    --------++++--
    +
    ENQ
    0
    0
    2000
    0
    0
    --------++++--
    +
    BTC
    0
    0
    2000
    0
    0
    --------++++--
    +
    SPO
    0
    0
    2000
    0
    0
    --------++++--
    +
    UP2
    0
    0
    2000
    0
    0
    --------++++--
    +
    max_rq_id          13
    wake_evt_udp_now     0
    wake events           total     9,  udp     7 ( 77%),  shm     2 ( 22%)
    since last update     total     9,  udp     7 ( 77%),  shm     2 ( 22%)
    Dump of tm_adm structure:               Mon Jul 02 11:04:30 2007
    =========================
    Term    uid  man user    term   lastop  mod wp  ta   a/i (modes)
    Workprocess Comm. Area Blocks               Mon Jul 02 11:04:30 2007
    =============================
    Slots: 300, Used: 1, Max: 0
    --------++--
    +
    id
    owner
    pid
    eyecatcher
    --------++--
    +
    0
    DISPATCHER
    -1
    WPCAAD000
    NiWait: sleep (5000 msecs) ...
    NiISelect: timeout 5000 ms
    NiISelect: maximum fd=1629
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Mon Jul 02 16:34:35 2007
    NiISelect: TIMEOUT occured (5000 ms)
    Shutdown server ...
    DpModState: buffer in state MBUF_PREPARED
    NiBufSend starting
    NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
    MsINiWrite: sent 110 bytes
    MsIModState: change state to SHUTDOWN
    DpModState: change server state from STARTING to SHUTDOWN
    Switch off Shared memory profiling
    ShmProtect( 57, 3 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RW
    ShmProtect( 57, 1 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RD
    DpWakeUpWps: wake up all wp's
    Stop work processes...
    Stop gateway
    killing process (3832) (SOFT_KILL)
    Stop icman
    killing process (3960) (SOFT_KILL)
    Terminate gui connections
    [DpProcDied] Process lives  (PID:3832  HANDLE:1600)
    waiting for termination of gateway
    NiWait: sleep (1000 msecs) ...
    NiISelect: timeout 1000 ms
    NiISelect: maximum fd=1629
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Mon Jul 02 16:34:36 2007
    NiISelect: TIMEOUT occured (1000 ms)
    Mon Jul 02 16:34:37 2007
    [DpProcDied] Process died  (PID:3832  HANDLE:1600)
    [DpProcDied] Process died  (PID:3960  HANDLE:1588)
    DpHalt: cancel all lcom connections
    MPI CancelAll 2 -> 0
    MPI DeleteAll 2 -> 0
    NiIMyHostName: hostname = 'pun-idmqa-vm1'
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
    DpConvertRequest: net size = 163 bytes
    NiBufSend starting
    NiIWrite: write 562, 1 packs, MESG_IO, hdl 3, data complete
    MsINiWrite: sent 562 bytes
    send msg (len 110+452) to name          -, type 4, key -
    detach from message server
    ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   9945]
    NiBufSend starting
    NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete
    MsINiWrite: sent 110 bytes
    MsIDetach: send logout to msg_server
    MsIDetach: call exit function
    DpMsShutdownHook called
    NiSelClear: removed hdl 3 from selectset
    MBUF state OFF
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/8
    LOCK WP ca_blk 1
    make DISP owner of wp_ca_blk 1
    DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 19)
    MBUF component DOWN
    NiBufClose: clear extensions for hdl 3
    NiBufSetStat: bufstat of hdl 3 changed from OK to OFF
    NiICloseHandle: shutdown and close hdl 3 / socket 1608
    MsIDetach: detach MS-system
    Mon Jul 02 16:34:38 2007
    EsCleanup ....
    ***LOG Q05=> DpHalt, DPStop ( 2492) [dpxxdisp.c   8478]
    Good Bye .....
    I am new to SAP EP installation. Please help me regarding this issue.
    Thanks and Regards,
    Smitha

    forgot to tell you, after that probably you will need to make the installation again.
    good luck.

  • The unattended installation failed while installing SQL Server 2008 R2 ????

    Hi gurus,
    I got an error while installing SQL Server 2008 R2 in Windows 2008 R2 standard 64 bit operating system.
    LOG file*
    Customized installation of SQL Server 2008R2 for SAP *
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlWriter_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
      MSI error description:        
      MSI status:                    Failed: see details below
      MSI error code:                0x1639
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
      MSI error description:        
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SystemConfigurationCheck_Report.htm
    1/16/2012 10:13:34 PM
    Message Box "Installation failed"
    The unattended installation failed.
      Installation Step: The unattended installation failed.
      Return Code:       -2068052377
      Log File:          C:\Windows\SQL4SAP.log
    Check the log file above.
    See SAP note 1144459 for known issues.
    Result: vbOK
    Registry settings (2/2):
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{2b9034f3-b661-4d36-a5ef-60ab5a711ace}
    WRITE(REG_DWORD): 4
    1/16/2012 10:37:32 PM
    Quit script with return code 1
    Please help me out with this issue.
    REGARDS,
    Raj

    Hello Raj,
    MS SQL DB installation specific steps for SAP system is clearly documented in SAP Installation guide. Please download from SMP, read it carefully and install as mentioned in the guide.
    Hope it helps.
    Thanks,
    Siva Kumar

  • Urgent Help :Product installation failed .Error Code 200 and Erroe code 601

    Installation failed after completing 69% ...Just after activiaing DB process...
    I need an urgent help
    (Nov 9, 2008 11:38:58 AM), Install, com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles, err, An error occurred and product installation failed.  Look at the log file C:\SAP\NSP\log.txt for details.
    (Nov 9, 2008 11:38:58 AM), Install, com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles, err, ProductException: (error code = 200; message="Java error"; exception = [java.lang.Exception])
    STACK_TRACE: 15
    ProductException: (error code = 200; message="Java error"; exception = [java.lang.Exception])
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.execute(StepWrapperInstallFiles.java:254)
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllSteps(StepWrapperInstallFiles.java:224)
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllInstallationSteps(StepWrapperInstallFiles.java:177)
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.install(StepWrapperInstallFiles.java:268)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
         at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    (Nov 9, 2008 11:39:00 AM), Install, com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct, err, An error occurred and product uninstallation failed.  Look at the log file C:\SAP\NSP\log.txt for details.
    (Nov 9, 2008 11:39:00 AM), Install, com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles, err, ProductException: (error code = 200; message="Java error"; exception = [java.lang.Exception])
    STACK_TRACE: 15
    ProductException: (error code = 200; message="Java error"; exception = [java.lang.Exception])
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.execute(StepWrapperInstallFiles.java:254)
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllSteps(StepWrapperInstallFiles.java:224)
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.executeAllUninstallationSteps(StepWrapperInstallFiles.java:192)
         at com.sap.installshield.sdcstepswrapper.StepWrapperInstallFiles.uninstall(StepWrapperInstallFiles.java:313)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.uninstallProductAction(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.processActionsFailed(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
         at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    (Nov 9, 2008 11:39:00 AM), Install, com.installshield.wizard.platform.win32.Win32PPKRegistryServiceImpl, err, java.lang.NullPointerException
    STACK_TRACE: 20
    java.lang.NullPointerException
         at com.installshield.product.service.registry.VPDDef.pack(Unknown Source)
         at com.installshield.product.service.registry.VPDDef.getId(Unknown Source)
         at com.installshield.product.service.registry.VPDDef.saveParents(Unknown Source)
         at com.installshield.product.service.registry.VPDDef.saveParents(Unknown Source)
         at com.installshield.product.service.registry.VPDDef.saveSoftwareObjectCache(Unknown Source)
         at com.installshield.product.service.registry.PureJavaRegistryServiceImpl.writeVPD(Unknown Source)
         at com.installshield.product.service.registry.PureJavaRegistryServiceImpl.finalizeRegistry(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at com.installshield.wizard.service.LocalImplementorProxy.invoke(Unknown Source)
         at com.installshield.wizard.service.AbstractService.invokeImpl(Unknown Source)
         at com.installshield.product.service.registry.GenericRegistryService.finalizeRegistry(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.finalizeRegistry(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
         at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    (Nov 9, 2008 12:09:23 PM), Install, com.installshield.product.actions.CopyFile, err, An error occurred and product installation failed.  Look at the log file C:\SAP\NSP\log.txt for details.
    (Nov 9, 2008 12:09:23 PM), Install, com.installshield.product.actions.CopyFile, err, ProductException: (error code = 601; message="err"; additional data = [Can not copy C:\SAP\NSP\_installTemp\j2ee\INSTALLER\BIN\steps.jar since C:\SAP\NSP\home\steps.jar already exists])
    STACK_TRACE: 12
    ProductException: (error code = 601; message="err"; additional data = [Can not copy C:\SAP\NSP\_installTemp\j2ee\INSTALLER\BIN\steps.jar since C:\SAP\NSP\home\steps.jar already exists])
         at com.installshield.product.actions.CopyFile.install(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
         at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    (Nov 9, 2008 2:47:09 PM), Install, com.installshield.product.actions.CopyFile, err, An error occurred and product installation failed.  Look at the log file C:\SAP\NSP\log.txt for details.
    (Nov 9, 2008 2:47:09 PM), Install, com.installshield.product.actions.CopyFile, err, ProductException: (error code = 601; message="err"; additional data = [Can not copy C:\SAP\NSP\_installTemp\j2ee\INSTALLER\BIN\steps.jar since C:\SAP\NSP\home\steps.jar already exists])
    STACK_TRACE: 12
    ProductException: (error code = 601; message="err"; additional data = [Can not copy C:\SAP\NSP\_installTemp\j2ee\INSTALLER\BIN\steps.jar since C:\SAP\NSP\home\steps.jar already exists])
         at com.installshield.product.actions.CopyFile.install(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
         at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    Edited by: Rajeev Ranjan on Nov 9, 2008 3:33 PM
    <LOCKED BY MODERATOR - URGENT, PLEASE HELP OR SIMILAR ARE FORBIDDEN>
    Edited by: Alvaro Tejada Galindo on Nov 10, 2008 9:53 AM

    AMreso wrote:
    Check this - http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-upda tes-ccm.html
    Sorry AMreso, I've already tried this and it didn't work for me:
    After reviewing the FAQ:
    https://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-upd ates-ccm.html
    I uninstalled Photoshop CC and re-installed it, after doing so the installation started the patch but failed it..

  • Solution Manager Installation Fails at step Run ABAP Reports

    I'm trying to install Solution Manager 4.0 on Windows 2003 using SQL 2005.  The installation fails at the Run ABAP Reports step: Executing ABAP report RADDBDIF
    I have logged in manually and run the RADDBDIF job in SE38 but I receive the same error message.  My SAPTRANHOST is properly defined and so are the shares.  Can anyone help? Thank!
    Here's the sapinst_dev.log:
    Calling function module: INST_RFC_GET_INTERFACE
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1065]
               CAbRfcImpl::performFunctionCall
    Function call was successful.
    TRACE      2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1066]
               CAbRfcImpl::performFunctionCall
    Function module call succesful: INST_RFC_GET_INTERFACE
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:924]
               CAbRfcImpl::getRfcInterfaceSAP
    Function interface generated successfully.
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:926]
               CAbRfcImpl::getRfcInterfaceSAP
    Technical properties of function set successfully.
    INFO       2008-10-21 14:00:34.842 [iaxxrfcfls.cpp:107]
               CRfcFuncRep::insFuncIf
    Information for application function INST_EXECUTE_REPORT copied to local repository.
    TRACE      2008-10-21 14:00:34.842 [iaxxrfcfls.cpp:108]
               CRfcFuncRep::insFuncIf
    Function interface entered into repository for INST_EXECUTE_REPORT
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:622]
               CAbRfcImpl::setFunction
    Function module INST_EXECUTE_REPORT set successfully.
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setFunction() done: true
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter(PARA, [])
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter() done: true
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter(PROGRAM, RADDBDIF)
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter() done: true
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.execute()
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1032]
               CAbRfcImpl::callFunction
    Executing function call INST_EXECUTE_REPORT.
    TRACE      2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1056]
               CAbRfcImpl::performFunctionCall
    Calling function module: INST_EXECUTE_REPORT
    ERROR      2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1089]
               CAbRfcImpl::performFunctionCall
    FRF-00025  Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
    TRACE      2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1090]
               CAbRfcImpl::performFunctionCall
    RFC failure or system exception raised
    TRACE      2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1091]
               CAbRfcImpl::performFunctionCall
    Exception condition "WRITE_FAILED" raised.
    INFO       2008-10-21 14:00:35.045 [iaxxbjsco.cpp:561]
               CIaJSCo::disconnect_nothrow(000:DDIC:EN:nath02:00::SOL:)
    RFC connection closed.
    TRACE      2008-10-21 14:00:35.45 [iaxxejsbas.hpp:408]
               handleException<ERfcExcept>()
    Converting exception into JS Exception ERfcException.
    TRACE      2008-10-21 14:00:35.045
    Function setMessageIdOfExceptionMessage: modlib.jslib.caughtException
    ERROR      2008-10-21 14:00:35.045
               CJSlibModule::writeError_impl()
    MUT-03025  Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
    TRACE      2008-10-21 14:00:35.45 [iaxxejsbas.hpp:483]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2008-10-21 14:00:35.45 [sixxcstepexecute.cpp:951]
    FCO-00011  The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR ( Last error reported by the step :Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..).
    TRACE      2008-10-21 14:00:35.61 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing service SAP Solution Manager 4.0 Support Release 4 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step :Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..). You may now </p> <ul> <li> choose <i>Retry</i> to repeat the current step. </li> <li> choose <i>View Log</i> to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS. </p> </body></html>
    TRACE      2008-10-21 14:00:35.61 [iaxxgenimp.cpp:1255]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI

    Hello Amélie,
    Check the file systems if you're not ran out of disk space.
    Second, check the database if you've enough storage space left.
    Hope it helps.
    Cheers,
    Satish.

  • IDES ECC 6.0 Installation failed at IMPORT ABAP -- Urgent pls....

    Hi Gurus,
    ecc6 installation failed at IMPORT ABAP step (to be precise - 16th step out of 19 steps) while importing  'SAPSSEXC' package .....
    snippets of following logs are below
    1> IMPORT_MONITOR.LOG
    2> SAPINST.LOG
    3> SAPSSEXC.LOG
    <h2>IMPORT_MONITOR.LOG</h2>
    ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l
    SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
    For mode details see 'SAPSSEXC.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-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is successfully completed.
    WARNING: 2008-01-08 02:42:17
    Cannot start import of packages with views because not all import packages with tables are loaded
    successfully.
    WARNING: 2008-01-08 02:42:17
    1 error(s) during processing of packages.
    INFO: 2008-01-08 02:42:17
    Import Monitor is stopped.
    <h2>SAPINST.LOG</h2>
    WARNING 2008-01-08 02:42:21
    Execution of the command "C:\j2sdk1.4.2_16-x64\bin\java.exe -classpath migmon.jar -showversion
    com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs
    F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:
    \ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F
    :\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11 -installDir
    C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS -orderBy "" -r3loadExe
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3
    -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code
    103. Output:
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.
    Loading of 'SAPAPPL2' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
    ERROR 2008-01-08 02:42:23
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s)
    import_monitor.java.log, import_monitor.log.
    ERROR 2008-01-08 02:42:24
    FCO-00011  The step runMigrationMonitor with step key
    |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|in
    d|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigratio
    nMonitor was executed with status ERROR .
    <h2>SAPSSEXC.LOG</h2>
    (DB) INFO: D301T~A created
    (DB) INFO: D345T created
    (DB) INFO: D345T~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: import of D345T completed (6585 rows) #20080107180224
    (DB) INFO: DSYST created
    (DB) INFO: DSYST~0 created
    (IMP) INFO: import of DSYST completed (54353 rows) #20080107194721
    (DB) INFO: DYNPSOURCE created
    (DB) INFO: DYNPSOURCE~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: import of DYNPSOURCE completed (190478 rows) #20080107205002
    (DB) INFO: ENHSPOTCONTRACT~1 created
    (DB) INFO: ENHSPOTHEADER created
    (DB) INFO: ENHSPOTHEADER~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: import of ENHSPOTHEADER completed (4078 rows) #20080107205109
    (DB) INFO: INDTEXT created
    (DB) INFO: INDTEXT~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (DB) INFO: PERMISSION created
    (DB) INFO: PERMISSION~0 created
    (IMP) INFO: import of PERMISSION completed (112356 rows) #20080107214109
    (DB) INFO: PERMISSION~IF created
    (DB) INFO: REPOSRC created
    (DB) INFO: REPOSRC~0 created
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    (IMP) INFO: InitFastLoad failed with <3: Can't fastload LOBs>
    (IMP) INFO: DBSL will be used
    ANY POINTERS WILL BE HIGHLY APPRECIATED
    THANKS IN ADVANCE

    no...loading was not finished....it aborted with 'Retry', 'View Log', & Stop options...i retried with no luck...
    this is 'Central system ' installation btw....
    it failed with below error
    ERROR 2008-01-08 02:42:23
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    <h2>IMPORT_MONITOR.LOG</h2>
    INFO: 2008-01-07 16:33:26
    Import Monitor is started.
    CONFIG: 2008-01-07 16:33:26
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=F:\ECC6\InstExport1\EXP1;F:\ECC6\InstExport2\EXP2;F:\ECC6\InstExport3\EXP3;F:\ECC6\InstExp4\EXP4;F:\ECC6\InstExport5\EXP5;F:\ECC6\InstExport6\EXP6;F:\ECC6\InstExport6\EXP7;F:\ECC6\InstExport6\EXP8;F:\ECC6\InstExport6\EXP9;F:\ECC6\InstExport6\EXP10;F:\ECC6\InstExport6\EXP11
    installDir=C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2008-01-07 16:33:26
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2008-01-07 16:33:26
    List of packages with views: 'SAPVIEW'.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2008-01-07 16:33:26 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\PROGRA1\SAPINS1\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2008-01-07 16:33:26
    Data codepage 4103 is determined using TOC file 'F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL1' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
    TRACE: 2008-01-07 16:33:26 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
    TRACE: 2008-01-07 16:33:28 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2008-01-07 16:33:32 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    INFO: 2008-01-08 00:15:00 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is successfully completed.
    TRACE: 2008-01-08 00:15:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is started.
    TRACE: 2008-01-08 00:15:27 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
    INFO: 2008-01-08 00:15:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is started.
    TRACE: 2008-01-08 00:15:56 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDIC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
    TRACE: 2008-01-08 00:15:58 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
    TRACE: 2008-01-08 00:16:02 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDIC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
    INFO: 2008-01-08 00:49:00 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is successfully completed.
    TRACE: 2008-01-08 00:49:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is started.
    TRACE: 2008-01-08 00:49:40 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPCLUST' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExp4\EXP4\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
    TRACE: 2008-01-08 00:50:11 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPCLUST' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
    INFO: 2008-01-08 00:53:51 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is successfully completed.
    TRACE: 2008-01-08 00:54:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is started.
    TRACE: 2008-01-08 00:54:40 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLEXC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport3\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
    TRACE: 2008-01-08 00:54:48 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLEXC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
    INFO: 2008-01-08 01:02:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is successfully completed.
    TRACE: 2008-01-08 01:02:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is started.
    TRACE: 2008-01-08 01:02:50 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSRC' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
    TRACE: 2008-01-08 01:03:11 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSRC' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
    INFO: 2008-01-08 01:09:19 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is successfully completed.
    TRACE: 2008-01-08 01:09:46 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is started.
    TRACE: 2008-01-08 01:09:51 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPPOOL' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
    TRACE: 2008-01-08 01:09:55 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPPOOL' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
    INFO: 2008-01-08 01:14:03 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is successfully completed.
    TRACE: 2008-01-08 01:14:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is started.
    TRACE: 2008-01-08 01:14:18 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDOCU' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
    TRACE: 2008-01-08 01:14:21 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDOCU' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
    INFO: 2008-01-08 01:15:50 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is successfully completed.
    TRACE: 2008-01-08 01:16:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is started.
    TRACE: 2008-01-08 01:16:19 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSPROT' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
    TRACE: 2008-01-08 01:16:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSPROT' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
    INFO: 2008-01-08 01:17:55 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is successfully completed.
    TRACE: 2008-01-08 01:18:18 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is started.
    TRACE: 2008-01-08 01:18:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLOAD' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
    TRACE: 2008-01-08 01:18:31 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLOAD' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
    INFO: 2008-01-08 01:18:43 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is successfully completed.
    TRACE: 2008-01-08 01:18:46 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is started.
    TRACE: 2008-01-08 01:18:48 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
    TRACE: 2008-01-08 01:18:50 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
    INFO: 2008-01-08 01:20:09 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is successfully completed.
    TRACE: 2008-01-08 01:20:15 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is started.
    TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDDIM' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
    TRACE: 2008-01-08 01:20:16 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDDIM' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
    INFO: 2008-01-08 01:20:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is successfully completed.
    TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is started.
    TRACE: 2008-01-08 01:20:45 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDFACT' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
    TRACE: 2008-01-08 01:20:46 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDFACT' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
    INFO: 2008-01-08 01:20:51 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is successfully completed.
    TRACE: 2008-01-08 01:21:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is started.
    TRACE: 2008-01-08 01:21:22 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDODS' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
    TRACE: 2008-01-08 01:21:23 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDODS' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
    INFO: 2008-01-08 01:21:25 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is successfully completed.
    TRACE: 2008-01-08 01:21:45 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER1' import package is started.
    TRACE: 2008-01-08 01:21:47 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER1' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport5\EXP5\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER1.TSK MSS -l SAPUSER1.log
    TRACE: 2008-01-08 01:21:52 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER1' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -loadprocedure fast
    INFO: 2008-01-08 01:21:53 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER1' import package is successfully completed.
    TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAP0000' import package:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -ctf I F:\ECC6\InstExport1\EXP1\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
    TRACE: 2008-01-08 01:22:16 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
    INFO: 2008-01-08 01:22:17 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    ERROR: 2008-01-08 01:32:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code -1,073,741,819.
    For mode details see 'SAPSSEXC.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-01-08 02:42:03 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is successfully completed.
    WARNING: 2008-01-08 02:42:17
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2008-01-08 02:42:17
    1 error(s) during processing of packages.
    INFO: 2008-01-08 02:42:17
    Import Monitor is stopped.

  • CE 7.1 sp3 installation failed in step 1: CheckDBServer...Error

    Hello,
    While trying to install CE the installation failed in Step 1. Following is the error dump:
    =====================================================
    perl: executing the following command
    C:\usr\sap\A35\home\tools\osql -E -i checkDBServer_param.txt -o version.out -r
    - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / -
    perl: command exited with status: 256
    Class[SdcHelpers]Process exit value = 256
    Class[SdcHelpers]Process exited with rc: 256
    DEBUG: rc is: 256
    ERROR: Is MSSQL DB Server running?
    class[DBHelperMssql]DWI DialogMessageID 103 set in props file
    DB Server check failed
    ERROR: Execution of step: >> CheckDBServer <<
         failed. Execution returned: RC=100
         Elapsed time:         00:00:09 [HH:mm:ss]
    Class[SdcHelpers]Process exit value = 100
    Class[SdcHelpers]Process exited with rc: 100
    ERROR: Step 'CheckDBServer' ends with rc = 100
    STEPCONTROLLER: Error while installing J2EE
    ====================================================
    My DB server is running with green status.
    Any clues in resolving this will be appreciated.
    Thanks.
    Regards,
    Gajendra.

    Hi Pankaj,
    I ran the tool but still the problem persists ;-(
    Below is the action log. Any hints from this.
    ==========================================
    ACTION: **********************************************************************
    ACTION: * Install SAP J2EE Engine 4 Web Application Server 700/710/720 ... XXX
    ACTION: *                                                                    
    ACTION: * Executing Step:   CheckDBServer
    ACTION: * User:             I034771
    ACTION: * WorkingDirectory: C:\usr\sap\A35\home\temp_j2eeinst
    ACTION: * Date:             2007.12.11 14:35:44
    ACTION: * Logfile:          steps.CheckDBServer.log
    ACTION: * Property File:    C:\usr\sap\A35\home\j2eeinst.props
    ACTION: * Tool Version:     720.2.20070320012101
    ACTION: **********************************************************************
    DEBUG: Initializing Properties.
    ACTION: Initializing steps.ini
    DEBUG: Substep readen: 1
    writePropFile: C:\usr\sap\A35\home\temp_j2eeinst\checkDBServer_param.txt
    Content:
    DECLARE @sVersion VARCHAR(1000)
    SELECT @sVersion = @@VERSION
    PRINT 'version='+@sVersion
    DECLARE @sVersion2 VARCHAR(1000)
    SELECT @sVersion2 = convert(varchar(1000),serverproperty('collation'))
    PRINT 'collation='+@sVersion2
    DEBUG: Creating script file: C:\usr\sap\A35\home\temp_j2eeinst\.\temp_j2eeinst\temp_script.2.pl
    DEBUG: Creating script with command:
         C:\usr\sap\A35\home\tools\osql -E -i checkDBServer_param.txt -o version.out -r
    Start command: C:\usr\sap\A35\home\perl\bin\perl.exe C:\usr\sap\A35\home\temp_j2eeinst\.\temp_j2eeinst\temp_script.2.pl
    Execute in current working dir: C:\usr\sap\A35\home\temp_j2eeinst
    Calling: C:\usr\sap\A35\home\perl\bin\perl.exe C:\usr\sap\A35\home\temp_j2eeinst\.\temp_j2eeinst\temp_script.2.pl
    Tokenizing cmdstring...
    Start external command...
    Using parent environment...
    DEBUG: Executing Argv:
    DEBUG: Arg[0]: C:\usr\sap\A35\home\perl\bin\perl.exe
    DEBUG: Arg[1]: C:\usr\sap\A35\home\temp_j2eeinst\.\temp_j2eeinst\temp_script.2.pl
    DEBUG: Process started. Try to get Streams..
    DEBUG: Got Streams. Try to read them...
    perl: executing the following command
    C:\usr\sap\A35\home\tools\osql -E -i checkDBServer_param.txt -o version.out -r
    perl: command exited with status: 256
    Class[SdcHelpers]Process exit value = 256
    Class[SdcHelpers]Process exited with rc: 256
    DEBUG: rc is: 256
    ERROR: Is MSSQL DB Server running?
    class[DBHelperMssql]DWI DialogMessageID 103 set in props file
    DB Server check failed
    ERROR: Execution of step: >> CheckDBServer <<
         failed. Execution returned: RC=100
         Elapsed time:         00:00:10 [HH:mm:ss]
    ====================================================
    Regards,
    Gajendra.

  • SQL SP1 Installation fail....URGENT HELP--3

    I am planning to install IDES ECC 6 on my single system for the practice; I have been installed windows server 2003 with SP1.
    I am trying to install sql2005 through the sql4sap.vbs, database was successfully installed but SP1 ended with error. I also did database install manually which was successful but SP1 ended with error.
    The Unattended installation failed.
    Installation step: SQL Server service pack – build 9.00.2047
    Return Code: 11032
    Log File:     c:\windows\sql4sap.log
    See SAP note 896566 for known issues.
    I read the note but I didn’t find any relation solution of my problem.
    I have been installed IDES – R3 & SM4 many times but this time getting stuck due to unknown reason.
    Anyone have same experience of my related problem, share me
    Regards
    Anwer Waseem
    SAP BASIS

    I have the exact same error.  Anwer Waseem did you get any help or were you able to resolve the problem.
    Cheers
    Daniel Ngu

  • SQL SP1 Installation fail....URGENT HELP

    EXPERT
    I am planning to install IDES ECC 6 on my single system for the practice; I have been installed windows server 2003 with SP1.
    I am trying to install sql2005 through the sql4sap.vbs, database was successfully installed but SP1 ended with error. I also did database install manually which was successful but SP1 ended with error.
    The Unattended installation failed.
    Installation step: SQL Server service pack – build 9.00.2047
    Return Code: 11032
    Log File:     c:\windows\sql4sap.log
    See SAP note 896566 for known issues.
    I read the note but I didn’t find any relation solution of my problem.
    I have been installed IDES – R3 & SM4 many times but this time getting stuck due to unknown reason.
    Anyone have same experience of my related problem, share me
    Regards
    Anwer Waseem
    SAP BASIS

    Hello,
    can you send me the zipped log files from \WINDOWS\Hotfix\ to clas dot hortien @ sap dot com ?
    I then will have a closer look into it.
    Do you have a virus scanner running ? Please turn it off
    as it may affect the installation.
    Best regards
      Clas Hortien
      SAP Dev. Support - SQL Server

  • SQL SP1 Installation fail....URGENT HELP--2

    expert!!!
    I am planning to install IDES ECC 6 on my single system for the practice; I have been installed windows server 2003 with SP1.
    I am trying to install sql2005 through the sql4sap.vbs, database was successfully installed but SP1 ended with error. I also did database install manually which was successful but SP1 ended with error.
    The Unattended installation failed.
    Installation step: SQL Server service pack – build 9.00.2047
    Return Code: 11032
    Log File:     c:\windows\sql4sap.log
    See SAP note 896566 for known issues.
    I read the note but I didn’t find any relation solution of my problem.
    I have been installed IDES – R3 & SM4 many times but this time getting stuck due to unknown reason.
    Anyone have same experience of my related problem, share me
    Regards
    Anwer Waseem
    SAP BASIS

    Hello,
    can you send me the zipped log files from \WINDOWS\Hotfix\ to clas dot hortien @ sap dot com ?
    I then will have a closer look into it.
    Do you have a virus scanner running ? Please turn it off
    as it may affect the installation.
    Best regards
      Clas Hortien
      SAP Dev. Support - SQL Server

  • SQL SP1 Installation fail....URGENT HELP--4

    I am planning to install IDES ECC 6 on my single system for the practice; I have been installed windows server 2003 with SP1.
    I am trying to install sql2005 through the sql4sap.vbs, database was successfully installed but SP1 ended with error. I also did database install manually which was successful but SP1 ended with error.
    The Unattended installation failed.
    Installation step: SQL Server service pack – build 9.00.2047
    Return Code: 11032
    Log File:     c:\windows\sql4sap.log
    See SAP note 896566 for known issues.
    I read the note but I didn’t find any relation solution of my problem.
    I have been installed IDES – R3 & SM4 many times but this time getting stuck due to unknown reason.
    Anyone have same experience of my related problem, share me
    Regards
    Anwer Waseem
    SAP BASIS

    Hello,
    can you send me the zipped log files from \WINDOWS\Hotfix\ to clas dot hortien @ sap dot com ?
    I then will have a closer look into it.
    Do you have a virus scanner running ? Please turn it off
    as it may affect the installation.
    Best regards
      Clas Hortien
      SAP Dev. Support - SQL Server

Maybe you are looking for