Installation of SAP SolMan 4.0 SR2 on AIX 5.3/Oracle

We have already installed SolMan 4.0 successfully in our dev sys--so we know this can be done. Now we are trying to start the sapinst to install our prod system and can't get the SAPInstGUI to recognize the sapinst running on the same server.
We have:
-installed the newest IBM JDK 1.4.2 SR8
-set SAPINST_JRE_HOME=/usr/java14_64/
-set TEMP, TMP and TMPDIR
When we run ./sapinst as root, it stops, apparently waiting for the GUI:
Starting GuiServer using:
/usr/java14_64/bin/java -cp /mnt/temp/sapinst_exe.360628.1190411815/JAR/instgui.jar:/mnt/temp/sapinst_exe.360628.1190411815/JAR/inqmyxml.jar -Djava.security.egd=file:/dev/urandom SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200
load resource pool /mnt/bs2005/BS_2005_SR2_SAP_Installation_Master/IM_AIX_PPC64/resourcepool.xml
guiengine: no GUI connected; waiting for a connection on host r09prd01, port 21200 to continue with the installation
We have als attempted to start using ./sapinst -nogui and ./sapinst SAPINST_START_GUI=false, which gives the same message. We then try to start the SAPInstGUI as <SID>adm, the GUI will generate a screen with the following message:
"Could not connect to host r09prd01 on port 21212. java.net.ConnectException: A remote host refused an attempted connect operation."
What are we missing to get this install started?

Hi,
I am trying tom install SOLMAN4.0SR2 for ERP2005 IS RETAIL, here i am getting java error and i am not able  to continue installation. Error is java JDK does not a valid directory i am getting
Os: SUN10/AMD64MACHINE
Patches : followed as per sap note 908334
Java version tried : 1.5.0,1.4.2_09,1.4.2_13,1.4.2_12 also.
I am struggling since 3 days, please some one respong i am very much greatful to your hlep ... please help me
Error:
INFO 2007-09-27 21:38:08
Execution of the command "/usr/jdk/j2sdk1.4.2_09/bin/java -classpath /tmp/sapinst_exe.4931.1190909239/JAR/ins-j2ee.jar -d64 com.sap.ins.j2ee.GetSystemProperty" finished with return code 1. Output: Unrecognized option: -d64Could not create the Java virtual machine.
ERROR 2007-09-27 21:38:08
MUT-03023  Directory /usr/jdk/j2sdk1.4.2_09 is not a valid JDK directory: execution of "/usr/jdk/j2sdk1.4.2_09/bin/java -classpath /tmp/sapinst_exe.4931.1190909239/JAR/ins-j2ee.jar -d64 com.sap.ins.j2ee.GetSystemProperty" finished with return code 1.
ERROR 2007-09-27 21:38:08
FCO-00011  The step setDefaults with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|1|0|setDefaults was executed with status ERROR .
Regards,
Sankaranarayanan.G
BASIS CONSULTANT
CHENNAI,INDIA

Similar Messages

  • Installing SAP CRM 5.0 SR2 ABAP+JAVA on Windows:Oracle

    Hi,
    I want to start installation of the below
    Installing SAP CRM 5.0 SR2 ABAP+JAVA on Windows:Oracle
    will anyone please tell me the brief procedue or if you have any documents or snapshots other what is there in service market place please mail me to
    [email protected]
    Thanks a lot in advance.

    Hello Mohan ,
    Please download the latest installation guide for SAP CRM 5.0 SR2 ABAP+JAVA  for NT / ORA from instguides .
    Regards,
    Santosh Karadkar

  • Java instance installation fails for EP 6.0 SR1 on AIX 5.1/Oracle 9.2

    Hi Friends
    I am currently installing EP 6.0 SR1 on NW04 on AIX 5.2 & Oracle 9.2.0.1, last few steps of installation I applied Oracle patchset 9.2.0.5. I am using the option SAPNW SR1-> Java system -> Central system ->custom installation-> Java system, the installation stops at step 30(Load Java database content) of 36 giving the message "java.sql.SQLException:Ioexception: The Network adapter could not establish the connection.
    I am also attaching the contents of log jload.log & jload.java.log. Really appreciate if somebody who has faced similar problem or knows the solution can provide a tip, thanks in advance.
    CDBAXD08:oraepd 27> more jload.log
    11.03.05 20:05 com.sap.inst.jload.Jload main
    INFO: Jload -sec
    EPD,jdbc/pool/EPD,/sapmnt/EPD/global/security/data/SecStore.properties,/
    sapmnt/EPD/global/
    security/data/SecStore.key -dataDir /epinst/was_java/J2EE_OSINDEP/J2EE-
    ENG/JDMP -job /tmp/sapinst_instdir/N
    W04SR1/WEBAS_JAVA/CENTRAL/ONE_HOST/IMPORT.XML -
    log /tmp/sapinst_instdir/NW04SR1/WEBAS_JAVA/CENTRAL/ONE_HOST
    /jload.log
    11.03.05 20:05 com.sap.inst.jload.Jload main
    SEVERE: couldn't connect to DB
    java.sql.SQLException: Io exception: The Network Adapter could not
    establish the connection
    CDBAXD08:oraepd 28> more jload.java.log
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
    ClassicVM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM)
    build caix64142ifx-20041126 (JIT en
    abled: jitc))
    Mar 11, 2005 8:05:10 PM com.sap.inst.jload.Jload main
    INFO: Jload -sec
    EPD,jdbc/pool/EPD,/sapmnt/EPD/global/security/data/SecStore.properties,/
    sapmnt/EPD/global/
    security/data/SecStore.key -dataDir /epinst/was_java/J2EE_OSINDEP/J2EE-
    ENG/JDMP -job /tmp/sapinst_instdir/N
    W04SR1/WEBAS_JAVA/CENTRAL/ONE_HOST/IMPORT.XML -
    log /tmp/sapinst_instdir/NW04SR1/WEBAS_JAVA/CENTRAL/ONE_HOST
    /jload.log
    Mar 11, 2005 8:05:15 PM com.sap.inst.jload.Jload main
    SEVERE: couldn't connect to DB
    java.sql.SQLException: Io exception: The Network Adapter could not
    establish the connection
    FYI the SID name given to the Java instance is EPD & the output of
    java -version of the 3 id's root, epdadm & oraepd is as attached.
    CDBAXD08:epdadm 1> java -version
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
    Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM)
    build caix64142ifx-20041126 (JIT enabled: jitc))
    Thanks & Rgds,
    Abhishek

    Hi Abhishek,
    I'm trying to install EP 6.0 SR1 on Aix and DB2.   I'm having problems with Secure Store installation step (Encryption: JCE and Crypto Toolkit).
    Did you have any problems with this ?   From which place did you get the JCE file ? 
    Thanks for your help, I really appreciate it !
    Regards from Mexico,
    Diego

  • Solution Manager 4.0 Installation Error  AIX 5.3 / Oracle 10.2.0.1

    Hi All,
    I am facing an error in the installation step of Solution Manager 4.0 on AIX 5.3 / Oracle 10.2.0.1
    Hostname : INXXXXSAPIDES
    The ABAP instance is not coming up  and the Installation failed.I tried to bring up the instance manually.But was not successful.
    <b>Workprocess traces :</b>
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 0x7000001732fa070
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 0x7000001732fa470
    S    using messages for server info
    S  size of spec char cache entry: 297032 bytes (timeout 100 sec)
    S  size of open spool request entry: 2176 bytes
    S  immediate print option for implicitely closed spool requests is disabled
    A
    A  -PXA--
    A  PXA INITIALIZATION
    A  System page size: 4kb, total admin_size: 5720kb, dir_size: 5664kb.
    A  Attached to PXA (address 0x7000001e0000000, size 150000K)
    A  abap/pxa = shared unprotect gen_local
    A  PXA INITIALIZATION FINISHED
    A  -PXA--
    A
    Signal 6 encountered.
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = unlimited
    => Core limit      = unlimited
    => File size limit = unlimited
    => Heap address  = 0x0x113a1f5c0
    => Stack address = 0xfffffffffffded0
    => Stack low     =  0xfffffffffffb5e0
    => Stack high    =  0xffffffffffff810
    => Stack Trace:
            pthread_kill() at 0x900000000490650
            praise() at 0x900000000490070
            raise() at 0x900000000059624
            abort() at 0x900000000084a90
      TrThHookFunc: called for WP dump
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  ThErrPrivHandle: set th_errno (11)
    M  Entering ThReadDetachMode
    M  *** ERROR => ThIErrHandle: bad value for th_act_em_hdl (8), detach T0/M0 [thxxhead.c   10721]
    <b>
    DEV_DISP </b>
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMsgAdmin: Set release to 7000, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    DpMsgAdmin: Set patchno for this platform to 102
    Release check o.K.
    Sat Jul 28 22:41:18 2007
    ERROR => W0 (pid 442462) died [dpxxdisp.c   14319]
    ERROR => W2 (pid 635048) died [dpxxdisp.c   14319]
    ERROR => W3 (pid 598164) died [dpxxdisp.c   14319]
    ERROR => W4 (pid 770084) died [dpxxdisp.c   14319]
    ERROR => W5 (pid 815142) died [dpxxdisp.c   14319]
    ERROR => W6 (pid 761862) died [dpxxdisp.c   14319]
    my types changed after wp death/restart 0xbf --> 0xbd
    ERROR => W7 (pid 671804) died [dpxxdisp.c   14319]
    my types changed after wp death/restart 0xbd --> 0xb9
    ERROR => W8 (pid 630958) died [dpxxdisp.c   14319]
    ERROR => W9 (pid 622786) died [dpxxdisp.c   14319]
    ERROR => W10 (pid 549070) died [dpxxdisp.c   14319]
    my types changed after wp death/restart 0xb9 --> 0xb1
    ERROR => W11 (pid 544802) died [dpxxdisp.c   14319]
    my types changed after wp death/restart 0xb1 --> 0xa1
    ERROR => W12 (pid 508062) died [dpxxdisp.c   14319]
    my types changed after wp death/restart 0xa1 --> 0x81
    Sat Jul 28 22:41:55 2007
    ERROR => W1 (pid 802934) died [dpxxdisp.c   14319]
    my types changed after wp death/restart 0x81 --> 0x80
    DP_FATAL_ERROR => DpWPCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    increase tracelevel of WPs
    <b>stderr1</b>
    Command:  dw.sapSM4_DVEBMGS10
               pf=/usr/sap/SM4/SYS/profile/SM4_DVEBMGS10_INSISCSAPIDES
    ICM up and operational (pid: 675892) ***
    timezone value meaningless.  BSD libraries linked?
    work process W1 died => ThSigHandler: signal
    timezone value meaningless.  BSD libraries linked?
    work process W2 died => ThSigHandler: signal
    timezone value meaningless.  BSD libraries linked?
    work process W12 died => ThSigHandler: signal
    timezone value meaningless.  BSD libraries linked?
    .timezone value meaningless.  BSD libraries linked?
    work process W4 died => ThSigHandler: signal
    work process W8 died => ThSigHandler: signal
    timezone value meaningless.  BSD libraries linked?
    Can someone please help me in this.
    Thanks
    Siva
    Message was edited by:
            siva sakthi

    I found the solution..
    There was a a problem in the timezone setting for the server.After changing it and rebooting  it worked perfectely.

  • SOLMAN 4.0 SR2 connect to SAP R/3 Three System landscape (DEV QA and PRD)

    Hi,
    We have successfully installed SOLMAN 4.0 SR2 (ABAP + JAVA) on
    WIN2003 SP2 EE MSSQL 2005 EE SP1.
    I just want to activate the service so that SOLMAN could see my existing SAP R/3 4.6 C Three system landscape (DEV QAS PRD).
    I heard settings should be done on SPRO IMG configs. Could anyone tell me the exact procedure to navigate on it. I see a lot of buttons to config and execute, Just want to make sure everything will be in order.
    My SLD is directly installed locally on my SOLMAN server.
    Thanks,
    Simoun

    Hello Simoun,
    Telling from your last sentence I assume that you would like to connect SolMan (transaction SMSY) to your locally installed SLD or in other words: replicate SLD system data into SOLMAN system landscape SMSY.
    Please check this document:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000538663&_SCENARIO=01100035870000000202&_OBJECT=011000358700000530282007E
    Here you find information covering prerequisites, required SAP Solution Manager IMG configuration to connect SLD and SMSY and frequently ask questions (FAQ-like).
    I hope this helps you to get started.
    Regards,
    Doreen

  • SAP Solman Installation

    I need to install SAP Solman 7 + EHP1; AS ABAP +DB on one server and java on other server, based on Windows 2K3 Ent Server 64bit and Oracle 10.2. This is because of the limited hardware resources on a single server.
    Is it mandatory to have ABAP and JAVA on same box with Solman ? I know you can add dialog instances later.
    When I try to install using sapinst --> SAP Systems --> --> --> Oracle and Central System; it asks me for Java component. It does not proceed further unless I mention the java export location. Same happens if I select a distributed installation ?
    Can someone please help me understand this behavior ?
    Thanks,

    For Solution Manager it's not possible to separate ABAP + Java due to technical restrictions.
    Markus

  • ERROR INSTALLATION ERROR SAP NetWeaver 7.0 (2004s) SR2

    Hi Gurus,
    We are busy installing SAP NetWeaver 7.0 (2004s) SR2  (ABAP+JAVA) with an Oracle 10.2 DB.
    We get the following error during the installation.
    WARNING 2008-09-12 08:02:52.947
    Execution of the command "C:\j2sdk1.4.2_18-x64\bin\java.exe -Xmx64M -Djava.ext.dirs=K:\usr\sap\CR1\DVEBMGS00\SDM_tmp\lib -jar K:\usr\sap\CR1\DVEBMGS00\SDM_tmp\SDM.jar autoinstall sdmHome=K:\usr\sap\CR1\DVEBMGS00\SDM\program popDir=K:\usr\sap\CR1\DVEBMGS00\SDM_tmp sdmRoot=K:\usr\sap\CR1\DVEBMGS00\SDM\root javaHome=C:/j2sdk1.4.2_18-x64 Sdmadminport=50017 Sdmguiport=50018 Sdmhttpport=50019 hostname=csiides extractpackedinst=true" finished with return code 12. Output:
    Invalid parameter "hostname" for SDM command "autoinstall"
    Syntax error. Return code: 12
    ERROR 2008-09-12 08:02:52.947
    MUT-01014  Call of SDM API autoinstall ends with error code 12. Log file SDMautoinstall.log, log file content: \n
    Invalid parameter "hostname" for SDM command "autoinstall"
    Syntax error. Return code: 12

    Hi,
    I had this same problem when installing CRM 2007.
    To solve it, I had to edit the file
    C:\Program Files\sapinst_instdir\CRM2007\SYSTEM\MSS\CENTRAL\AS\control.xml
    Use the search function from notepad to find the string "autoinstall".
    Modify this paragraph
      var callArgs = ["autoinstall",
                      "sdmHome=" + FSPath.getPath(sdmHome + "/program").toStringOS(),
                      "popDir=" + tempPath.toStringOS(),
                      "sdmRoot=" + FSPath.getPath(sdmHome + "/root").toStringOS(),
                      "javaHome=" + javaHome,
                      "Sdmadminport=" + ports.adminPort,
                      "Sdmguiport=" + ports.guiPort,
                      "Sdmhttpport="  + ports.httpPort,
                      "hostname=" + hostname,
    To remove the line   * "hostname=" + hostname,*
    Save the control.xml file, relaunch sapinst.exe and choose "Continue old installation".
    It worked for me !
    Olivier

  • Error in installing Solman 4.0 SR2

    Hi,
    An Error occured during the installation of Solman 4.0 SR2 in import ABAP phase.
    Sofware and Hardware configurartion:
    Java 1.4.2_12
    Database MSSQL 2005 SP2
    Solution manager 4.0 SR2
    Dual core 2.6 GHZ
    2 gb ram
    160gb hard drive
    Plz find attached the sapinst.log file and import_monitor.log file.
    Needfull help in this regard would be highly appreciated. Deserving points will be rewarded.
    Best Regards
    Omeir.
    *import_monior.log*
    INFO: 2007-09-21 01:21:36
    Import Monitor is started.
    CONFIG: 2007-09-21 01:21:36
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-09-21 01:21:36
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-09-21 01:21:36
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2007-09-21 01:21:36
    Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-09-21 01:21:37
    Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-09-21 01:21:37
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is started.
    TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDIC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
    TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDIC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
    INFO: 2007-09-21 01:25:22 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDIC' import package is successfully completed.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSEXC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP1\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL0' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL1' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
    TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2007-09-21 01:25:38 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    INFO: 2007-09-21 13:22:54
    Import Monitor is started.
    CONFIG: 2007-09-21 13:22:54
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-09-21 13:22:54
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-09-21 13:22:54
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2007-09-21 13:22:54
    Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-09-21 13:22:58
    Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-09-21 13:22:58
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL0.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
    ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL1.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
    ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
    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
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is started.
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is started.
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPAPPL2' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is started.
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSSRC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPPOOL' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPPOOL' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSRC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
    TRACE: 2007-09-21 13:23:25 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL2' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
    INFO: 2007-09-21 13:24:19 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPPOOL' import package is successfully completed.
    TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is started.
    TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSPROT' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
    TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSPROT' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
    INFO: 2007-09-21 13:25:38 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSPROT' import package is successfully completed.
    TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is started.
    TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSDOCU' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
    TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSDOCU' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
    INFO: 2007-09-21 13:26:05 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSDOCU' import package is successfully completed.
    TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is started.
    TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLEXC' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
    TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
    INFO: 2007-09-21 13:26:30 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLEXC' import package is successfully completed.
    TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is started.
    TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPCLUST' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
    TRACE: 2007-09-21 13:26:56 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPCLUST' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
    INFO: 2007-09-21 13:27:12 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPCLUST' import package is successfully completed.
    TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is started.
    TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPSLOAD' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
    TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSLOAD' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
    INFO: 2007-09-21 13:27:28 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSLOAD' import package is successfully completed.
    INFO: 2007-09-21 13:27:40 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSRC' import package is successfully completed.
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is started.
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is started.
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDDIM' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDFACT' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDDIM' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
    TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDFACT' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
    INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDDIM' import package is successfully completed.
    INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDFACT' import package is successfully completed.
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is started.
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is started.
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPUSER' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAPDODS' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPDODS' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
    TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPUSER' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
    INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPUSER' import package is successfully completed.
    INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS' import package is successfully completed.
    TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAP0000' import package:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
    TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
    INFO: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    INFO: 2007-09-21 13:34:56 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL2' import package is successfully completed.
    WARNING: 2007-09-21 13:35:24
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2007-09-21 13:35:24
    3 error(s) during processing of packages.
    INFO: 2007-09-21 13:35:24
    Import Monitor is stopped.
    INFO: 2007-09-21 13:38:06
    Import Monitor is started.
    CONFIG: 2007-09-21 13:38:06
    Application options:
    dbCodepage=4103
    dbType=MSS
    extFiles=no
    importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
    installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
    jobNum=3
    loadArgs= -loadprocedure fast
    monitorTimeout=30
    orderBy=
    r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
    sapinst=
    trace=all
    tskFiles=yes
    CONFIG: 2007-09-21 13:38:06
    List of packages with table structure: 'SAP0000'.
    CONFIG: 2007-09-21 13:38:06
    List of packages with views: 'SAPVIEW'.
    TRACE: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
    INFO: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
    Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
    Primary key creation: before load.
    Index creation: after load.
    INFO: 2007-09-21 13:38:06
    Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
    INFO: 2007-09-21 13:38:06
    Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    INFO: 2007-09-21 13:38:06
    Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is started.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is started.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPSSEXC' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL1' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
    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
    ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL1' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL1.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
    ERROR: 2007-09-21 13:38:08 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is interrupted with R3load error.
    Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
    For mode details see 'SAPAPPL0.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
    WARNING: 2007-09-21 13:38:36
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2007-09-21 13:38:36
    3 error(s) during processing of packages.
    INFO: 2007-09-21 13:38:36
    Import Monitor is stopped.
    sapinst.log
    INFO 2007-09-21 13:22:26
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.2.xml'.
    INFO 2007-09-21 13:22:27
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.3.xml'.
    INFO 2007-09-21 13:22:29
    Execute step
    Component  W2K_ServicePack_Check|ind|ind|ind|ind
    Preprocess  of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
    INFO 2007-09-21 13:22:40
    Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.2.xml'.
    INFO 2007-09-21 13:22:41
    Execute step runMigrationMonitor of component |NW_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.
    INFO 2007-09-21 13:22:51
    Switched to user: prdadm.
    INFO 2007-09-21 13:22:51
    Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
    INFO 2007-09-21 13:22:51
    Switched to user: prdadm.
    INFO 2007-09-21 13:22:51
    Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
    INFO 2007-09-21 13:22:51
    Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
    WARNING 2007-09-21 13:35:24
    Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
    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 16, completed 1, failed 0, total 18.
    Import Monitor jobs: running 2, waiting 15, completed 1, failed 0, total 18.
    Import Monitor jobs: running 3, waiting 14, completed 1, failed 0, total 18.
    Loading of 'SAPAPPL0' import package: ERROR
    Loading of 'SAPAPPL1' import package: ERROR
    Import Monitor jobs: running 1, waiting 14, completed 1, failed 2, total 18.
    Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
    Import Monitor jobs: running 1, waiting 13, completed 1, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 12, completed 1, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 11, completed 1, failed 3, total 18.
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 2, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 10, completed 2, failed 3, total 18.
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 3, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 9, completed 3, failed 3, total 18.
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 4, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 8, completed 4, failed 3, total 18.
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 5, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 7, completed 5, failed 3, total 18.
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 6, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 6, completed 6, failed 3, total 18.
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 7, failed 3, total 18.
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 1, waiting 6, completed 8, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 5, completed 8, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 4, completed 8, failed 3, total 18.
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 9, failed 3, total 18.
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 1, waiting 4, completed 10, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 3, completed 10, failed 3, total 18.
    Import Monitor jobs: running 3, waiting 2, completed 10, failed 3, total 18.
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 11, failed 3, total 18.
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 1, waiting 2, completed 12, failed 3, total 18.
    Import Monitor jobs: running 2, waiting 1, completed 12, failed 3, total 18.
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 13, failed 3, total 18.
    Loading of 'SAPAPPL2' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
    ERROR 2007-09-21 13:35:24
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2007-09-21 13:35: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|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 .
    INFO 2007-09-21 13:38:06
    An error occured and the user decided to retry the current step: "|NW_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".
    INFO 2007-09-21 13:38:06
    Switched to user: prdadm.
    INFO 2007-09-21 13:38:06
    Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
    INFO 2007-09-21 13:38:06
    Switched to user: prdadm.
    INFO 2007-09-21 13:38:06
    Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
    INFO 2007-09-21 13:38:06
    Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
    WARNING 2007-09-21 13:38:36
    Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
    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 3, completed 14, failed 0, total 18.
    Import Monitor jobs: running 2, waiting 2, completed 14, failed 0, total 18.
    Import Monitor jobs: running 3, waiting 1, completed 14, failed 0, total 18.
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 2, waiting 1, completed 14, failed 1, total 18.
    Loading of 'SAPAPPL1' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 14, failed 2, total 18.
    Loading of 'SAPAPPL0' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
    ERROR 2007-09-21 13:38:36
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2007-09-21 13:38:36
    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|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 .
    INFO 2007-09-21 13:38:40
    An error occured and the user decide to stop.\n Current step "|NW_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".
    Edited by: mohammed  omeir on Dec 31, 2007 2:30 PM

    Hi Markus,
    Its says a previous run may not have finished clearly.
    What i need to do now?
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921132313
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Sep  1 2006 00:38:35
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    Hi Markus,
    Its says a previous
    (DB) INFO: connected to DB
    (TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
                 a previous run may not have been finished cleanly
                 file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921132321
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921133807
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Sep  1 2006 00:38:35
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
    (DB) INFO: connected to DB
    (TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
                 a previous run may not have been finished cleanly
                 file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921133807

  • Installation of SAP NetWeaver on Windows 2003 Server ( 32 Bit )

    Hello Gurus,
    I am planning installation of SAP Net Weaver - SR2 on Windows Server 2003 ( 32 Bit ) and oracle 10g is my database.
    can anybody guide me from where I can install the software coz in the market place SAP N/W-SR3 is available.
    Is SAP N/W - SR3 is recommeded for Windows 2003 Server ( 32 Bit ).
    Can any body guide me the process & my qurey.
    Thanks & Regards
    Shishir

    Read SAp note Note 1108852 - SAP NetWeaver 7.0 / Business Suite 2005 SR3: Windows
    it says:
    21/MAY/08
    SAP system installation only supported on 64-bit operating systems, except for  dialog instances
    As of SAP NetWeaver 7.0 SR3 and Business Suite 2005 SR3, SAP only supports to install dialog instances on 32-bit operating systems. All remaining SAP system instances (central instance, database instance, central services instance (SCS), ABAP central services instance (ASCS)) must be installed on 64-bit operating systems. Therefore the folder "SAP Systems" is not available on the "Welcome screen", when you start the installation from a installation master DVD for 32-bit.
    You might need to install dialog instances on 32-bit if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. We recommend, however, to first check whether these 32-bit components can run on 64-bit operating systems. If so, we recommend to also use 64-bit systems for these components, including the dialog instance.
    If you want to install a non-productive SAP NetWeaver 7.0 SR3 based system (test systems or development are normally productive systems)  on 32-bit, proceed as follows:
          1. Install a SAP NetWeaver 7.0 SR2 (SAP ERP 2005 SR2, SAP CRM 5.0 SR2 SAP SCM 5.0 SR2, SAP SRM 5.0 SR2) system.
          2. Patch this system to SAP NetWeaver 7.0 SR3 (SAP ERP 6.0, SAP CRM 5.0 SR3, SAP SCM 5.0 SR3, SAP SRM 5.0 SR3).

  • Multiple clients on one instance of SAP SolMan

    Hello,
    I have doubt about the conductibility of SAP Solution Manager to support more than one client, as an example, ones for Development and the other for production. I think that the limitation is due to the Java side which does not allow to perform more than one client.
    Up to know, I have browsed SAP Solution documents and have not found any indication about this kind of restriction, more than 1 client per instance of SAP SolMan.
    Look forward in hearing from your insight comments.
    Regards,
    Rodolfo Neuhaus

    Installation guide:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000718044&_OBJECT=011000358700000291922009E
    page 37:
    4.1.7 SAP Solution Manager Client Strategy
    SAP delivers a client with a standard configuration for SAP Solution Manager as part of the installation
    process. Client 000 is the initial configuration client, and client 001 is provided for productive use.
    Additional clients can be created if desired
    So I don't see an issue...but i would not recommend it...

  • EHP4 on SAP ECC 6.0 SR2

    Hello all,
    I am planning to install EHP4 on SAP ECC 6.0 SR2.
    Can you please help me out with the basic steps that need to be done for DOING EHP4
    I am going through the guide on Marketplace but just need some help from you all if you can outline the basic steps that need to be done
    Rohit

    Hi Rohit,
    > is it necessary to use solution manager for downloading the EHP4 support files
    > Is it not possible through Marketplace directly
    >
    Yes it is necessary to download files for EHP4 from solman..you cannot download it from market place...
    > Also what do you mean by technical usage,it comes when I am trying to download files through Solution Manager
    >
    Technical usage means..e.g you want to install learning solution patch but in your system configuration in solman (SMSY transaction) it is not maintained then you will not be able to select this patch in MOPZ .. this is just an example....
    for more information check SAP note 1139602 and 1287216...
    Thanks
    Sunny

  • SAP SOLMAN - SECURE STORE FILES MISSING

    Hi SDN,
    while installing SAP SOLMAN 4.0 CI the sapinst asks me for the secure store files that didn't exist in the data directory, i found the same issue in the forums but none solved my problem.
    someone knows how can i create this secure store files manually ?
    thanks and best regards,
    Pedro

    Quite the same thing for me with a JAVA MCOD installation. Were you able to find out a solution ?
    Best regards.
    David.

  • Can I cange IP address and Domain name after installation of SAP?

    Hello Gurus,
    I have present situation like this-
    SAP System - Solution manger 4.0 ( Installation is completed)
    Workgroup - MSHOME
    Ip - 80.0.0.10
    I need to change like
    Ip- 172.165.0.10
    Domain - XYZ.com
    Now my question is wheather this is possible? If yes or not please explain. If I change the IP address then is the system in SLD of solution manger and RFC connections for this systems would work prprly or not? PLease tell me the proper solution.
    Thanks and Regards,
    Suhas.

    Hi,
    you perform local installation for SAP  so you can not include this system into domain it's create problem
    now if you want to cahnge ip address of your SAP Solman host that you can do and also if you want FQDN for your SOLMAN host it's also possible
    first create this parameter in your instance profile using RZ10
    icm/host_name_full   --> solmanhost.xyz.com
    save and activate profile
    now stop the SAP system change the ip of you SAP solman host
    create the following entry on solman host in hosts file
    /windows32/drivers/system32/etc
    172.165.0.10  -tab   solmanhost -tab-   solmanhost.xyz.com
    start sap system
    regards,
    kaushal

  • Problem on Installation of SAP NW testdrive 7 on Linux!!

    Hy, i have started the installation of SAP 7 Linux testdrive but i have received this message:
    unpacking sqd_env.tar.bz2
    bzip2: compressed file ends unexpectedly
               peraphs it is corrupted)
    bzip2: Inappropriate ioctl for device
               Input file = (stdin). output file =(stdout)
    It is possible that the compressed file have become corrupted.
    After these messages the installation has continued with unpacking other tar file.
    I try to open the sqd_env.tar.bz2 but the system has sad to me that the file is corrupted.
    How can i resolve this problem?
    Thank's a lot.
    Sincerely yours,
    Andrea Maraviglia

    Thanks for the tip - that was my problem exactly!
    One of the segments didn't copy correctly and the filesize was off.  I downloaded the file again and recombined them into a new .ISO file.   When I mounted .ISO and restarted the install process, I immediately got past the previous sticking point.

  • Unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    Hi,
    For SU01 role removal, you do not need S_USER_AGR with 02, and as you mentioned both authorizations available in production, if so trace should not show you the S_USER_AGR with 02 with RC=04.
    I would recommend to do role comparison for the user performing the activity. and then check if you have the S_USER_AGR with 02 in user buffer SU56.
    But ideally it should not ask you S_USER_AGR for 02 through SU01, so please take help of abaper to debug it.
    Also put trace in non-prd to see if S_USER_AGR is getting checked with 02 for removal through SU01.
    BR,
    Mangesh

Maybe you are looking for

  • Query to find the difference between the last date and the second to the last date

    Hi all, Hope all is well. I am working on the following problem because I am trying to improve my MS SQL skills. But I am stuck at the moment and I wonder if you could provide some assistance please. Here is the issue: Table 1: Dividends divId ExDate

  • Use emoji characters in 10.6.8

    I've tried to install this symbols but there is no chance for my system. However I learnt this emoticones were standarized on 2010! How come we cannot see / type them? It should be as simple as install a new font. All apps in the App Store ask for 10

  • Facing Problem in getting WSRP folder inside Portal_Home/j2ee folder.

    Hi friends, Currently i am facing problem in getting "WSRP" folder inside Portal_Home/j2ee folder.Let me explain in detail.While installing oracle portal i tried to upgrade from 10.1.2 to 10.1.4.Where mura.bat was executed fine.I got the message that

  • LR Does not use 1:1 previews in Develop mode?

    LR2 and LR2.1 are still terribly sluggish for me. My current example is I'm just trying to flip through photos and blanket paste some copied settings across the majority of a 1900 photo wedding. It's taken about 6 hours to flip through ~1000 photos..

  • What are third party compatible DVD burners?

    I can't seem to find a clear answer to this question: What is a "third party compatible" DVD burner that I can use with iMovie/iDVD? I don't have an internal DVD burner, so I'm thinking of picking up an external one. Problem is, I don't know which on