SOLUTION MANAGER 7.1 install on linux/oracle java error on ABAP IMPORT

Hello sdn experts, Im trying to install the Solution Manager 7.1 on linux/oracle, but It always stops at the abap import,
The error is in the Program "Migration Monitor", that exit with error.
Reviewing the logs, it seems that is trying to execute a java command line with a unrecognized option:
"Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 1. Output:
JVMJ9VM007E Command-line option unrecognized : -Xjvm:j9vm23"
Usage : java [-options] class...
As you can see, the sdk used is from IBM, and it works for all other saps we have here.
Is the wrong jdk? Which I should use if its wrong?
If is the right jdk, how could I get rid of this option and change it?
Any idea would be appreciated.
Thank you

Hi Maurici,
have you checked this note already?
[https://service.sap.com/sap/support/notes/1159935|https://service.sap.com/sap/support/notes/1159935]
It is about your error message. ...
Best, Hannes

Similar Messages

  • SOLUTION MANAGER 7.1 install on linux/oracle SLD import error

    Hello, after the abap import, the next error that gives the installation is at Configuring the SLD
    It seems that the account j2ee_admin and sldduser are locked or wrong password:
    TYPE=A<BR>STATE=401<BR>INFO_SHORT=Error connecting to http://sapsolman:50000/ctc/ConfigServlet?param=com.sap.ctc.util.SLDConfig;CONFIGURE_DATASUPPLIER;P4HOST=sapsolman,P4PORT=50004,J2EE_ADMIN=J2EE_ADMIN,J2EE_PASSWORD=desXXX,HTTPHOST=sapsolman,HTTPPORT=50000,SLDUSER=SLDDSUSER,SLDPASSWORD=desXXX). The provided user data might be incorrect or user might be locked.<BR>CONFIGURATION=
    If I try to get into the useradmin , I cant with j2ee_admin nor Administrator
    How can I get rid of this? Any help would be appreciated
    Thank you

    > If I try to get into the useradmin , I cant with j2ee_admin nor Administrator
    Is the ABAP instance running? If yes, logon to it and unlock the user j2ee_admin using SU01.
    Markus

  • Solution Manager 3.2 installation on linux

    Hi all,
    I experience some problems when I install Solution Manager 3.2 on Redhat Linux AS 4 wtih ORACLE 9.2 (platform 64bits, X86_64). Actually i am installing the database instance and in the phase "Starting RFC Jobs" (phase 34 of 39) stop the installation and display the following error:
    <b>FRY-0001 Cannot load library iamodrfc.so: iamodrfc.so: cannot open shared object file: No such file or directory</b>
    The message is clear but i have not been able to get or to generate the file iamodrfc.so.
    Another information about the installation:
    The SAP kernel is SAP BASIS 6.40.
    Server xSeries model 346
    The central instance and the database software has been installed succesfully.
    I appreciate any help about this problem.

    Hi,
    This library is part of SAPinst. Normally the case is that it is not available, corrupt or not appropriate for your platform.
    I suggest that try to obtain the library by extracting SAPinst. You may extract SAPinst framework to any location by running SAPinst with -extract option just like :
    <b><SAPinst location>/sapinst -extract .</b>
    By default when you start an installation SAPinst is extracted to /tmp/sapinst.exe<something>
    Hope this helps.
    Best regards, Dido

  • SAP Solution Manager 4.0 Install on iSeries V5R4M0 fails on STEP 40 of 40

    During Step 40 of 40 of Solution Manager 4.0 install on iSeries running i5/OS V5R3M0 failed with the following error:
    ERROR 2006-08-18 10:00:57 [iaxxgenimp.cpp:728]
    showDialog()
    FCO-00011 The step fixTemplate400 with step key
    |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|fixTemplate400
    was executed with status ERROR .
    TRACE [iaxxgenimp.cpp:657]
    showDialog()
    <html><head></head><body><p>An error occurred while processing service
    <b>SAP Solution Manager 4.0 > SAP Systems > IBM DB2 UDB for i
    TRACE [iaxxgenimp.cpp:1093]
    showDialog()
    waiting for an answer from gui
    ***********End of Data*******************
    Searching OSS Notes, there is no reference to the FCO-00011 error code

    Hello Loli,
    I think it was me, who misunderstood.
    Now I followed your recommendations, increased virtual memory on the sapinst machine, restarted the pc and the installation and it completed successfully. Thank you very much.
    Sorry that I can't give you points for the helpfull answer, because this is not my thread.
    Kind regards,
    Jürgen Scheckelhoff.

  • Solution Manager DB was installed in 'Simple mode'

    We are just a couple months into our first SAP installation.  I just received this message from my hardware/server guy:
    "Please be aware that the Solution Manager DB was installed in “Simple mode.”  This means that we don’t have transaction logs, and will only be able to recover back to the most recent back-up."
    How critical is this for solution manager?

    Hi people!!
    i found the solution, if some one have this problem, can check the sapnote 1951729.
    if you don't see any changes, try creating the connection through  trx. dbacockpit and then  assing  the DB conection created previously  (dbco trx-sapnote). Next step check it on solman setup (enter system parameter step).
    Best regards.
    Iván.

  • I wander is it on an  Xeon based Blade possible to install an linux/oracle

    I wander is it on an  Xeon 6C X5670 95W 2.93GHz/1333MHz/12MB based Blade possible to install an linux/oracle ECC server.
    Or is Xeon only for windows?
    Thank you in advance

    Hello Jan,
    All supported platforms for IBM hardware can be found at the location SAP on Linux and this points to SAP note 171380.
    You can contact IBM for older Blade / xSeries/ Netfinity models not listed under the above URL as mentioned to confirm if supported for your planned OS install.
    Information about supported combinations and install procedure can be found at the following sources:
    SAP on Linux -> Supported Linux kernels & Supported Linux distributions.
    SAP note 407314 - Released operating systems SAP R/3 kernel 6.x ORACLE, this assumes you will be installing with Linux.
    SAP note 171356 - SAP software on Linux: Essential information
    SAP note 722273 - Red Hat Enterprise Linux 3/4: Installation and upgrade
    I hope this information helps.
    All the best,
    Cristiano

  • Install Solution Manager in RedHat Enterprise 6 with Oracle 11

    Hello ,
    In the marketplace-PAM,  RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
    Does anyone have any information on this subject?
    Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
    tks

    Yes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
    Note 1565179 - SAP software and Oracle Linux
    Thanks

  • Oracle Errors while Solution Manager 4.0 installation on linux

    While installing Oracle 10g instance for Solution Manager 4.0, The following popup message displayed. I checked the log file and not much information. Please tell me what shall I need to do.
    Error message:
    Error in invoking target 'ntcontab.o' of make file '/oracle/<sid>/102_32/network/lib/ins_net_client.mk'
    see '/oracle/orainventory/logs/installActions2006-10-08_06-39-02PM.log' for details
    Thanks in advance
    Regards
    Srinivas

    Hello, have some one solved the problem ? I have the same problem on SLES9. I have fond note #499055. There are something about relinking files during Oracle installation on Linux. Please give an information did You soled a problem.
    Best Regards
    Marcin Sobolewski

  • Solution Manager 4.0 Install Linux : UME phase 34 of 44  fails

    I am trying to install Solution Manager 4.0 on Red Hat Enterprise 4 Linux with Oracle 10.2..... I am hung up at phase 34 of 44 of the installation where the UME is being set up...... I am running Java verion 1.4.2_12....
    Any help is greatly appreciated....
    Main error message is: CJS-30059  J2EE Engine configuration error.<br>DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: '
    java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
         at com.sap.engine.offline.FileClassLoader.findClass
    UMConfigurator log file:
    java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
         at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
    SAPINST Log file:
    INFO 2007-02-28 16:36:14
    Working directory changed to /tmp/sapinst_exe.10124.1172709349.
    INFO 2007-02-28 16:36:14
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO 2007-02-28 16:36:14
    Working directory changed to /tmp/sapinst_exe.10124.1172709349.
    INFO 2007-02-28 16:36:14
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO 2007-02-28 16:36:15
    Working directory changed to /tmp/sapinst_exe.10124.1172709349.
    INFO 2007-02-28 16:36:15
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO 2007-02-28 16:36:16
    Working directory changed to /tmp/sapinst_exe.10124.1172709349.
    INFO 2007-02-28 16:36:16
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO 2007-02-28 16:36:17
    Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.12.xml'.
    INFO 2007-02-28 16:36:17
    Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.13.xml'.
    INFO 2007-02-28 16:36:32
    Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.7.xml'.
    INFO 2007-02-28 16:36:32
    Execute step runUMConfigurator of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|3|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Doublestack|ind|ind|ind|ind|1|0.
    INFO 2007-02-28 16:36:44
    Working directory changed to /tmp/sapinst_exe.10124.1172709349.
    INFO 2007-02-28 16:36:44
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO 2007-02-28 16:36:44
    Working directory changed to /tmp/sapinst_exe.10124.1172709349.
    INFO 2007-02-28 16:36:44
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO 2007-02-28 16:36:45
    Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties.
    INFO 2007-02-28 16:36:45
    Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties.
    INFO 2007-02-28 16:36:46
    Account slnadm already exists.
    INFO 2007-02-28 16:36:46
    Account 0 already exists.
    INFO 2007-02-28 16:36:46
    Account 500 already exists.
    INFO 2007-02-28 16:36:46
    Account sapsys already exists.
    INFO 2007-02-28 16:36:46
    Effective group id set to 501.
    INFO 2007-02-28 16:36:46
    Account 0 already exists.
    INFO 2007-02-28 16:36:46
    Account 501 already exists.
    INFO 2007-02-28 16:36:46
    Effective group id set to 500.
    INFO 2007-02-28 16:36:46
    Removed environment variable SSH_AGENT_PID from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable KDE_MULTIHEAD from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable HOSTNAME from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SHELL from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable TERM from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable HISTSIZE from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable GTK2_RC_FILES from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable GS_LIB from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable GTK_RC_FILES from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable WINDOWID from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SAPINST_EXEDIR_CD from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable KDE_FULL_SESSION from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable USER from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable LD_LIBRARY_PATH from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable LS_COLORS from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable XCURSOR_SIZE from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SSH_AUTH_SOCK from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable KDEDIR from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SESSION_MANAGER from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable KONSOLE_DCOP from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable MAIL from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable DESKTOP_SESSION from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable PATH from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable INPUTRC from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable PWD from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable KONSOLE_DCOP_SESSION from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable JAVA_HOME from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable LANG from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SAPINST_EXE_DIR from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable GDMSESSION from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SSH_ASKPASS from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable HOME from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SHLVL from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable XCURSOR_THEME from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable LOGNAME from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable LESSOPEN from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable DISPLAY from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable G_BROKEN_FILENAMES from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable XAUTHORITY from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable COLORTERM from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable HOSTTYPE from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable VENDOR from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable OSTYPE from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable MACHTYPE from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable GROUP from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable HOST from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SUPPORTED from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SAPSYSTEMNAME from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable DIR_LIBRARY from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable THREAD from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable dbms_type from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable dbs_ora_tnsname from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable dbs_ora_schema from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable ORACLE_SID from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable DB_SID from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable ORACLE_BASE from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable TNS_ADMIN from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable ORACLE_HOME from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable NLS_LANG from current process environment.
    INFO 2007-02-28 16:36:46
    Removed environment variable SAPDATA_HOME from current process environment.
    INFO 2007-02-28 16:36:47
    Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfigurator.log.
    INFO 2007-02-28 16:36:47
    Output of /java/j2sdk1.4.2_12/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.tools.UMConfiguratorLoad /usr/sap/SLN/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/SLN/SYS/global/security/lib/tools/w3c_http.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/oracle/client/10x_32/instantclient/ojdbc14.jar -u ADMIN_USR=J2EE_ADMIN -u XXXXXX -u ADMIN_GRP=SAP_J2EE_ADMIN -u GUEST_USR=J2EE_GUEST -u GUEST_GRP=SAP_J2EE_GUEST -u ALL_GRP=Everyone -c CLIENT=001 -c COM_USR=SAPJSF -c XXXXXX -c ASHOST=localhost -c SYSNR=$$ -a setup -p abap -f /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties is written to the logfile umconfigurator.log.
    INFO 2007-02-28 16:36:47
    Execution of the command "/java/j2sdk1.4.2_12/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.tools.UMConfiguratorLoad /usr/sap/SLN/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/SLN/SYS/global/security/lib/tools/w3c_http.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/oracle/client/10x_32/instantclient/ojdbc14.jar -u ADMIN_USR=J2EE_ADMIN -u XXXXXX -u ADMIN_GRP=SAP_J2EE_ADMIN -u GUEST_USR=J2EE_GUEST -u GUEST_GRP=SAP_J2EE_GUEST -u ALL_GRP=Everyone -c CLIENT=001 -c COM_USR=SAPJSF -c XXXXXX -c ASHOST=localhost -c SYSNR=$$ -a setup -p abap -f /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties" finished with return code 0. Output:
    java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
         at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
    ERROR 2007-02-28 16:36:47
    CJS-30059  J2EE Engine configuration error.<br>DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: '
    java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
         at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
         at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
    ERROR 2007-02-28 16:36:47
    FCO-00011  The step runUMConfigurator with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|3|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Doublestack|ind|ind|ind|ind|1|0|runUMConfigurator was executed with status ERROR .

    Hi Carol,
    Check note 716604 to see if you are using the  correct JDK version.
    The problem seem to be that JVM cannot find a class to load. This class should be
    available as part of the contents of
    /tmp/sapinst_instdir/NW04S/SYSTEM/XXX/CENTRAL/AS/install/ .
    The contents of this directory normally come via unpacking of the
    J2EEINSTALL.SAR archive from the <Java DVD>/J2EE_OSINDEP/J2EE-INST
    location.
    Need to unpack J2EEINSTALL.SAR and copy any missing files into install
    directory with correct permissions. Check J2EEINSTALL.log to see what
    files were unpacked.
    Hope this helps if not let me know.
    Best regards,
    Dolores

  • Solution manager key for installing ecc 6.0 on window 2003, oracle 10g

    Hi,
    I am installing ecc6.0 on windows 2003 platfrom with 10g oracle database.  I have problem providing solution manager key during installtion in the window.
    my db hostname is : deleted
    sap system id : deleted
    central instance number: deleted
    can any one help me please.
    Thank you
    Edited by: Eric Brunelle on Feb 8, 2010 7:53 AM

    > I am installing ecc6.0 on windows 2003 platfrom with 10g oracle database.  I have problem providing solution manager key during installtion in the window.
    >
    > my db hostname is : deleted
    > sap system id :deleted
    > central instance number: deleted
    It is illegal to provide keys here.
    You have to install a solution manager first before you can install an ERP 6.0 system - or open an OSS call if your Solution Manager is not (yet) available.
    Markus

  • Solution Manager 4.0 install Error

    I am trying to install Solution Manager 4.0 on a IA64 server running Windows 2003(64 bit edition). I have SQL Server 2005. I have JDK versionj2sdk1.4.2_12-x64.
    The sapinst.exe error log is as follows:
    +++++++++++++++++++++++++++++++++++++++++++++++++++++
    SAPINST.EXE error
    ERROR 2006-08-09 11:00: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 2006-08-09 11:00:23
    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|9|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 .
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++
    The Error entries in the Import_monitor log is as follows:
    +++++++++++++++++++++++++++++++++++++++++++++++++
    ERROR: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is interrupted with R3load error.
    Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\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: 2006-08-09 10:39:27 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is interrupted with R3load error.
    Process 'F:\usr\sap\S24\SYS\exe\uc\NTIA64\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
    ++++++++++++++++++++++++++++++++++++++++++++++++++++
    The error entry in the SAPSSEXC.log mention in the Import_monitor log is as follows:
    ++++++++++++++++++++++++++++++++++++++++++++++++++
    (DB) INFO: connected to DB
    (TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
    \AS\SAPSSEXC.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\SAPSSEXC.TSK possibly corrupted
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
    ++++++++++++++++++++++++++++++++++++++++++++++++++++
    The error entry in the SAPAPPL0.log mention in the Import_monitor log is as follows:
    +++++++++++++++++++++++++++++++++++++++++++++++++
    (DB) INFO: connected to DB
    (TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
    \AS\SAPAPPL0.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\SAPAPPL0.TSK possibly corrupted
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809103927
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: START OF LOG: 20060809111000
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Apr 3 2006 02:55:14
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
    (DB) INFO: connected to DB
    (TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL
    \AS\SAPAPPL0.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\SAPAPPL0.TSK possibly corrupted
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: job finished with 1 error(s)
    F:\usr\sap\S24\SYS\exe\uc\NTIA64\R3load.exe: END OF LOG: 20060809111001
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Please let me know.
    Thanks
    Mikir

    Hello.
    I'm currently installing SAP BW 3.50 on Oracle 10.2, Windows 2003, J2SDK 1.4.2_11. As of now, i've got an error when i put these reference:
         SAP:BW-MMR:630_SP3_REL:::*
         SAP:BW-SDK:630_SP3_REL:::*
    Kindly help on how to resolve this.
    Thanks.

  • Solution Manager 4.0 install error logging in for DDIC step 29

    Has anyone else seen the error 'Test logon to SAP System <sid> failed"? It states that it cannot login for DDIC. This is at step 29 during the install of the solution manager 4.0.
    We are running on a Windows 2003 Server/Oracle 10g.
    Any help would be greatly appreciated. We've been hitting this same error for the last couple of days.
    Thanks,
    DBB

    Dear Derrick,
    I have run into the exact same problem!!!!
    During step 29 of the install does it ask you to enter the DDIC password?
    It will ask you twice for a password if both the times the login fails then you will have no other option but to uninstall and reinstall Sol Man 4.
    The tactic that worked for me is that when it will ask u the passowrd the first time.......before you enter the password.......login in to Sol Man 4 using the default DDIC password 19920706. then change the default password. And then go back to the install and give this new ddic password.
    This is the only thing that worked with me.
    Let me know if anything else works.
    Email me @ [email protected] if you have any other questions.
    thanks
    Mikir

  • Solution Manager 4.0,  Red hat Linux 4.0 ES & AS, JSF user creation error

    Dear SAP Gurus,  Please advise.
    I have problem during the installation of SAP SOL Man4.0
    Input:
    I am using <b>SOL Man 4.0</b> with Linux version 2004s version2
    1. <b>Red Hat 4.0 ES</b> , 2. <b>Red hat 4.0 AS</b> (Tried both)
    <b>Java 1.4.2_09
    java Cripto: 1.4.2</b>
    when it go the step 34 out of 44 when it create JSF user creation, I am getting error
    It could not able to create Java user.
    It stops. this error is coming during sapjsf user creation.
    is this bug in SOL man 4.0, any one able to successfully install on Linux.
    I see lot of people had probem while doing on windows, but no one tried on Linux.
    I really appriciate, if some one can help on this.
    Thanks
    Ashok .K
    [email protected]

    Dear Raguraman C ,
    Thanks for your help, here is the log i got, during installation step of <b>Phase 33 of 45 JSF user creation</b>.
    Please analyse, advise me what Java settings need to be changed.
    Thanks
    Ashok .K
    [email protected]
    INFO       2006-12-29 00:06:38
    Execute step createJSF of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind |ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2|0.
    INFO       2006-12-29 00:06:39 [syuxcpath.cpp:351]
               CSyPath::createFile()
    Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UserCheck.jlaunch.
    INFO       2006-12-29 00:06:39 [syuxcpath.cpp:351]
               CSyPath::createFile()
    Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UserCheck.log.
    INFO       2006-12-29 00:06:39 [syuxccuren.cpp:264]
               CSyCurrentProcessEnvironmentImpl::setGroup(PSyGroup)
    Real group id set to 501.
    INFO       2006-12-29 00:06:39 [syuxccuren.cpp:543]
               CSyCurrentProcessEnvironmentImpl::setEffectiveGroup(PSyGroup)
    Effective group id set to 501.
    INFO       2006-12-29 00:06:39 [syxxccuren.cpp:105]
               CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(iastring)
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO       2006-12-29 00:06:39
               CJSlibModule::writeInfo_impl()
    Output of /usr/sap/SM1/DVEBMGS01/exe/jlaunch UserCheck.jlaunch com.sap.security.tools.UserCheck / tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/O RA/CENTRAL/AS/install/sharedlib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install -c sysn r=01 -c ashost=machine5 -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX - r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message is written to the logfile /tmp/sapi nst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UserCheck.log.
    WARNING    2006-12-29 00:09:27
               CJSlibModule::writeWarning_impl()
    Execution of the command "/usr/sap/SM1/DVEBMGS01/exe/jlaunch UserCheck.jlaunch com.sap.security.t ools.UserCheck /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir /SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS /install -c sysnr=01 -c ashost=machine5 -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SA PJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message" finished with retu rn code 4. Output:
    Dec 29, 2006 12:06:44... Info: User management tool (com.sap.security.tools.UserCheck) called for  action "checkCreate"
    Dec 29, 2006 12:06:44... Info: Connected to backend system SM1 client 001 as user DDIC
    Dec 29, 2006 12:06:45... Info: Called for user SAPJSF
    Dec 29, 2006 12:06:49... Info: Formal password check successful
    Dec 29, 2006 12:06:49... Info: Will create user SAPJSF
    Dec 29, 2006 12:09:20... Info: Created user SAPJSF of type A with reference user <none>
    Dec 29, 2006 12:09:22... Warning: Error during creation of user SAPJSF. Will remove user again to  ensure clean exit state
    Dec 29, 2006 12:09:27... Error: Exception during execution of the operation
    [EXCEPTION]
    com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Invalid request.
            at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
            at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1395)
            at com.sap.mw.jco.JCO$Client.execute(JCO.java:3917)
            at com.sap.mw.jco.JCO$Client.execute(JCO.java:3354)
            at com.sap.security.tools.UserCheck.createUser(UserCheck.java:1876)
            at com.sap.security.tools.UserCheck.main(UserCheck.java:289)
            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)
    Dec 29, 2006 12:09:27... Info: Leaving with return code 4
    INFO       2006-12-29 00:09:27 [syuxcfile.cpp:280]
               CSyFileImpl::remove()
    Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.
    INFO       2006-12-29 00:09:27 [syuxcfile.cpp:280]
               CSyFileImpl::remove()
    Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.clone.
    ERROR      2006-12-29 00:09:27
               CJSlibModule::writeError_impl()
    CJS-30196  Invalid request.
    ERROR      2006-12-29 00:09:27
    FCO-00011  The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind |ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2 |0|createJSF was executed with status ERROR .
    Ashok kalakota My coment:
    Phase 33 of 45 JSF user creation
    INFO       2006-12-29 00:06:38
    Execute step createJSF of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind |ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2|0.
    INFO       2006-12-29 00:06:39 [syuxcpath.cpp:351]
               CSyPath::createFile()
    Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UserCheck.jlaunch.
    INFO       2006-12-29 00:06:39 [syuxcpath.cpp:351]
               CSyPath::createFile()
    Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UserCheck.log.
    INFO       2006-12-29 00:06:39 [syuxccuren.cpp:264]
               CSyCurrentProcessEnvironmentImpl::setGroup(PSyGroup)
    Real group id set to 501.
    INFO       2006-12-29 00:06:39 [syuxccuren.cpp:543]
               CSyCurrentProcessEnvironmentImpl::setEffectiveGroup(PSyGroup)
    Effective group id set to 501.
    INFO       2006-12-29 00:06:39 [syxxccuren.cpp:105]
               CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(iastring)
    Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
    INFO       2006-12-29 00:06:39
               CJSlibModule::writeInfo_impl()
    Output of /usr/sap/SM1/DVEBMGS01/exe/jlaunch UserCheck.jlaunch com.sap.security.tools.UserCheck / tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/O RA/CENTRAL/AS/install/sharedlib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install -c sysn r=01 -c ashost=machine5 -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX - r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message is written to the logfile /tmp/sapi nst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/UserCheck.log.
    WARNING    2006-12-29 00:09:27
               CJSlibModule::writeWarning_impl()
    Execution of the command "/usr/sap/SM1/DVEBMGS01/exe/jlaunch UserCheck.jlaunch com.sap.security.t ools.UserCheck /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir /SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS /install -c sysnr=01 -c ashost=machine5 -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SA PJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message" finished with retu rn code 4. Output:
    Dec 29, 2006 12:06:44... Info: User management tool (com.sap.security.tools.UserCheck) called for  action "checkCreate"
    Dec 29, 2006 12:06:44... Info: Connected to backend system SM1 client 001 as user DDIC
    Dec 29, 2006 12:06:45... Info: Called for user SAPJSF
    Dec 29, 2006 12:06:49... Info: Formal password check successful
    Dec 29, 2006 12:06:49... Info: Will create user SAPJSF
    Dec 29, 2006 12:09:20... Info: Created user SAPJSF of type A with reference user <none>
    Dec 29, 2006 12:09:22... Warning: Error during creation of user SAPJSF. Will remove user again to  ensure clean exit state
    Dec 29, 2006 12:09:27... Error: Exception during execution of the operation
    [EXCEPTION]
    com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Invalid request.
            at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
            at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1395)
            at com.sap.mw.jco.JCO$Client.execute(JCO.java:3917)
            at com.sap.mw.jco.JCO$Client.execute(JCO.java:3354)
            at com.sap.security.tools.UserCheck.createUser(UserCheck.java:1876)
            at com.sap.security.tools.UserCheck.main(UserCheck.java:289)
            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)
    Dec 29, 2006 12:09:27... Info: Leaving with return code 4
    INFO       2006-12-29 00:09:27 [syuxcfile.cpp:280]
               CSyFileImpl::remove()
    Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.
    INFO       2006-12-29 00:09:27 [syuxcfile.cpp:280]
               CSyFileImpl::remove()
    Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.clone.
    ERROR      2006-12-29 00:09:27
               CJSlibModule::writeError_impl()
    CJS-30196  Invalid request.
    ERROR      2006-12-29 00:09:27
    FCO-00011  The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind |ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2 |0|createJSF was executed with status ERROR .
    [root@machine5 AS]# cat UserCheck.log
    Dec 29, 2006 12:06:44... Info: User management tool (com.sap.security.tools.UserCheck) called for action "checkCreate"
    Dec 29, 2006 12:06:44... Info: Connected to backend system SM1 client 001 as user DDIC
    Dec 29, 2006 12:06:45... Info: Called for user SAPJSF
    Dec 29, 2006 12:06:49... Info: Formal password check successful
    Dec 29, 2006 12:06:49... Info: Will create user SAPJSF
    Dec 29, 2006 12:09:20... Info: Created user SAPJSF of type A with reference user <none>
    Dec 29, 2006 12:09:22... Warning: Error during creation of user SAPJSF. Will remove user again to ensure clean exit state
    Dec 29, 2006 12:09:27... Error: Exception during execution of the operation
    [EXCEPTION]
    com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Invalid request.
            at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
            at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1395)
            at com.sap.mw.jco.JCO$Client.execute(JCO.java:3917)
            at com.sap.mw.jco.JCO$Client.execute(JCO.java:3354)
            at com.sap.security.tools.UserCheck.createUser(UserCheck.java:1876)
            at com.sap.security.tools.UserCheck.main(UserCheck.java:289)
            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)
    Dec 29, 2006 12:09:27... Info: Leaving with return code 4
    [root@machine5 AS]# pwd
    /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS
    [root@machine5 AS]#

  • Solution Manager 7.1 Install, next steps

    I completed the install of Solution Manager 7.1 on Windows x64/SQL Server, I've read through the master installation guide, but I'm not certain what the next steps will be to get initial configuration done.  I've read multiple posts that mention running SOLMAN_SETUP from SAP GUI, but at present I can't seem to log in, because it seems to require a SAP Router?
    Question is do I really need the SAP Router, am I using the correct software (SAPGUI/SAPLOGON) to login?  Is there another piece of software I need?
    Ultimately I need to install ERP 6.0 however I can't complete that install without a key from solution manager, so I'll need to get this sorted first.
    I'd greatly appreciate a push in the right direction. Thank you!

    Thanks for the response, I did manage to get connected, after a while of searching I found that the listeners were not started for some reason, which I started, and I found a resource that detailed how to get logged in via SAPLogin. 
    This was prior to your response unfortunately, so I have already started down the path of running SOLMAN_SETUP without creating a client copy.  From what I'm reading in the article you linked, that's a best practice of sorts, but for us it will not be so important as our interest is in a development system only and have no production use planned at any time.  If it's not too late to create the copy I can still do so if it's going to ultimately benefit the installation.
    I ran into some issues going through the system preparation in solman_setup, now that I've read the article you've listed I'm still confused if I need SAP Router or not, I would greatly prefer not to use it as it seems to require additional network/DMZ setup and this is sort of a rush project at the moment.  Furthermore the guide you linked for SOLMAN_SETUP references a prerequisite that RFC Destination SAPOSS uses a working connection, which again seems to rely on the SAP Router.  I'm very interested in knowing if I can avoid that step, but if it's absolutely necessary something can be done.
    I've gone through the System Preparation guide, unfortunately SP10 seems to be the latest version so I'm not sure how much of this is redundant now in SP12. 
    Other questions:
    - LMDB seems to replace SLD but still requires a functional SLD?  I opted to configure a local SLD during installation but I've not looked into any additional configuration needed to be done here, is there a good article that explains SLD?
    I just need to get far enough along to generate the key to get ERP up and running ultimately, thanks for the help.

  • Solut Manager v4.0 install. error : CJS-30022 Program 'Migration Monitor

    Hi Experts
    I am trying to install Solution Manager 4.0. I am performing installation on Windows 2003 server.
    While installing SolMan, everything goes fine, until step # 17 while importingABAP monitor jobs, then it runs into below error messages.
    ERROR 2007-08-11 18:03:25
    CJS-30022 Program 'Migration Monitor'
    exits with error code 103.
    For details see log file(s) import_monitor.java.log, import_monitor.log.
    C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\sapinst.log
    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 .
    WARNING 2007-08-11 18:03:25
    Execution of the command "C:\java\bin\java.exe -classpath migmon.
    jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs
    "C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 1\EXP1;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 2\EXP2;
    C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 3\EXP3;C:\install cd\SAP_Solution_M._4.0_SR2_Inst._Export 4\EXP4" -installDir
    "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\HSM\SYS\exe\uc\NTI386\R3load.exe -tskFiles
    yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output:
    java version "1.4.2_15"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
    Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
    Import Monitor jobs: running 1, waiting 9, completed 8, failed 0, total 18.
    Import Monitor jobs: running 2, waiting 8, completed 8, failed 0, total 18.
    Import Monitor jobs: running 3, waiting 7, completed 8, failed 0, total 18.
    Loading of 'SAPAPPL0' import package: ERROR
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 0, waiting 7, completed 8, failed 3, total 18
    Any suggesstions/ideas for this error
    Regards
    Rahul

    Check the logfile SAPAPPL0.log for errors...
    Markus

Maybe you are looking for