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

Similar Messages

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>An error occurred while processing service
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 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.

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

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

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

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 7.0 Install Error

Morning Experts,
I'm installing a central instance on windows 2003 vm, 8gb ram, 200gb disk space, MS SQl Server 2005. During install it gets to the point of starting the intance and times out. Here's the error:
This was in the startBPC log (bpc name of sapid):
running D:\usr\sap\BPC\SYS\exe\uc\NTAMD64\sapstart.exe name=BPC nr=00 SAPDIAHOST=DAL-VS-SAPMGR -wait
SAPSTART finished successfully on DAL-VS-SAPMGR_BPC_00, but at least one process doesn't run correctly:
D:\usr\sap\BPC\SYS\exe\uc\NTAMD64\sapstart.exe=>sapparam(1c): No Profile used.
any idea why it would stop the instance and not be able to start it?
Thanks,
Bart

Hello Barton,
This may be due to Message Server connection failed.
try to add the entry in the c:\windows\system32\drivers\ect\services
sapmsJ2E 3600/tcp
if your System ID is J2E and the intance no is 00
wait for some time or restart the host and try for installation.
Hope it helps.
Cheers,
Satish.

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 STATE=401 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. 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

Install ECC 6.0 and Solution Manager on same server Error (MaxDB/Linux)

I have installed Solution manager on one server and then ECC 6 also in the same server with another SID. during the installation it errored out at phase "SLD configuration" with UME error , J2EE_ADMIN locked etc..we checked the user id and noticed it got locked in ECC 6 system and we unlocked it.
But after the ECC installation the solution manager java engine is not coming up error with "com.sap.security.core.ume.service failed" error. Prior to the ECC installation the Solution Manager J2EE was working.
thanks in advance
Mathew

error in the /j2ee/cluster/server0/log/defaultTrace.1.trc
is as follows
#1.5#00137256A483001E0000001700006F190004163784D40864#1150327614343#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_61##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
When I looked at using jcmon the dispacher is up and the server0 and SDM is down

Solution Manager 7 EHP1 green/demo install

I am trying to set up a standalone SAP BI server with the demo content so I can test a product that queries InfoCubes. Windows 2003/SQL Server 2008 platform.
I am trying to follow the docs, but they assume some prerequites that are not clearly defined. I have a central system running with a license installed, but I cannot apply SNOTEs because I get an error in connection to destination SAPOSS.
Obviously I am missing something fundamental but I can't find a simple guide on what to do. The documentation seems to run in circles telling me to do things that don't work because I don't have the right SNOTEs installed.
Is there an easy way to get a SAPOSS connection for a non-production system?
Is there a guide that walks you through all the prerequisites for a Solution Manager 7 EHP1 install?

> Is there an easy way to get a SAPOSS connection for a non-production system?
In order to download the SAP Note via SNOTE, the SAP OSS RFC connection should work. If your SAP Router is working fine, then add necessary entries in Tcode OSS1>technical Parameters . Add the router in the system data of the particular system in service market place.
> Is there a guide that walks you through all the prerequisites for a Solution Manager 7 EHP1 install?
Refer the installation guide in service.sap.com/instguides > SAP components > Solution Manager EHP1 .
Regards,
Nibu Antony

Install Solution Manager 4.0 Support Release 4 ,JDK ERROR

I'm install Solution Manager 4.0 Support Release 4 on Windows 2003 Enterprise x64 Edition with Oracle10g
and JSDK 1_4_2_18,when confirm JDK DIRECTORY,Its shown error below.
ERROR 2008-07-15 09:00:21.328
FCO-00011 The step verifyPolicy with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_getJavaHome|ind|ind|ind|ind|1|0|verifyPolicy was executed with status ERROR .
SAPinst has found a valid JDK directory.The installed JDK has version 1.4.2_18,confirm that you want to use this JDK DIRECTORY.
Please help me

Oh, Sory so much
my step installer
1. pre-OS configuration parameter (solaris recomment on Master Install)
2. Installer solution manager
3. master install disk , select install solution manager 4.0, select OS(solaris) , select DB(oracle)
4.start install ,
5. error step ??? 27 "start instance server" fail ????
error detail.
error 2008-01-20
CJS-30149 ABAP Processes of Instance <SID> /Overbmgsoo (ABAP:Msncytrlinnign) class did not start after 50:00 Min Givising up
error 2008-01-20 17.52
FCD-00011 th step start with key NW_Onehost|ind|..... Nw_Onehost_system|ind|..... Nw_CI Instance |ind|.... Nw_CI instance start |ind|... start was executed with start erroe
Thank you.

Install solution manager 4.0 fail (solaris & oracle 10g)

Install solution manager 4.0 be congested "start instance serveice" step fail.
Edited by: Kraikanchit Duangdee on Jan 21, 2008 5:00 PM

Oh, Sory so much
my step installer
1. pre-OS configuration parameter (solaris recomment on Master Install)
2. Installer solution manager
3. master install disk , select install solution manager 4.0, select OS(solaris) , select DB(oracle)
4.start install ,
5. error step ??? 27 "start instance server" fail ????
error detail.
error 2008-01-20
CJS-30149 ABAP Processes of Instance <SID> /Overbmgsoo (ABAP:Msncytrlinnign) class did not start after 50:00 Min Givising up
error 2008-01-20 17.52
FCD-00011 th step start with key NW_Onehost|ind|..... Nw_Onehost_system|ind|..... Nw_CI Instance |ind|.... Nw_CI instance start |ind|... start was executed with start erroe
Thank you.

Solution Manager DB was installed in 'Simple mode'

Similar Messages

Maybe you are looking for