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

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

How to install Linux on UEFI systems where GRUB fail to install?

A few of us are asking:
How to install Linux on UEFI systems where GRUB fail to install? Because after installing Linux, my MBR is messed up, and I get a "no operating system found" at system startup.
abvasili
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.
Solved!
Go to Solution.

Hi again,
I would like to answer to another question, just in case:
Question: Can I dual boot Win7 and Linux on a UEFI capable bios?
Answer: Yes you can. If your HDD is formatted in MBR partition table (or msdos) than you can install first windows 7 and than the distro of your choice. BUT, careful, if you install windows from a DVD media it will convert your HDD in GPT partition table and dual boot will be almost impossible... (or will give you a lot of headache) to avoid this, dump the win7 iso to an usb using Windows 7 USB/DVD Download Tool. Installing from USB will not change the hdd in GPT partition table.
take care
abvasili
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

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

Solution Manager upgrade issue on Linux

Hi Alll,
Need your inputs/thoughts on this issue.
We are planning for Solution Manager upgrade from 3.1 to 4.0 and for this the setup and plan is as below:
The production data of the solution manager has been copied as a VMX FILE(VM Player) file on to a test server and we have plans to upgrade that and check and then upgrade on the production system.
The test machine has got a different IP address and hostname. From the test machine when I start the sap instance its affecting the Production machine and dueto which the production will not work until I stop the SAP Instance on the test machine.
It cannot be a IP conflict or hostname conflict as we have them differently on the test machine. But still there is an issue. The IT dept says the issue is with the starting up of the instance and we dont know where to see what exactly is the problem.
I am new to upgradation stuffs, this is my 1st assignment and I am not sure from where to start!!
Can anyone of you tell me where to check for the details?
SOLMAN is installed on a unix machine with oracle 9.2 and we are planning to upgrade it to SOLMAN 7.0
any suggestions on where to look out for the possible issue?

Hi,
I did this a lot and know the side effects a little.
My recipe:
1. Start the copy without network and manage it from the VMWare Console. Change the IP address and make sure all references to the hostname (DNS and /etc/hosts) point to the new one. I hope you're working consistently with hostnames and no IP addresses.
2. Configure the firewall (iptables) on the copied system to block all requests from and to the original production server. If there is any communication with other SAP servers (like monitoring agents, SLD, or others) block this too!
3. Re-enable the network in VMWare.
Alternatively: Can't you simply put this in a VLAN or a real seperated network with just the server and a management workstation?
Hope that helps..
Nikolaus

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

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.

OBIEE11g Enterprise install Linux-64 - Error in Creating ASInstance failed

HiAll,
I am trying to install OBIEE 11.1.1.5.0 Enterpise install on Linux-64 bit system.
It got failed at "Configuration Action : Creating ASInstance has failed "
Can anybody help me here.
Note: RCU step is done already.

Hi,
I am also facing the similar issue.The configuration is failing at Creating AS instance step.I tried editing the host file as requested in the post still no luck.
Following is the error in the installation log.
oracle.as.provisioning.engine.CfgWorkflowException
at oracle.as.provisioning.engine.Engine.processEventResponse(Engine.java:596)
at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstance(ASInstanceProv.java:178)
at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstanceAndComponents(ASInstanceProv.java:116)
at oracle.as.provisioning.engine.WorkFlowExecutor._createASInstancesAndComponents(WorkFlowExecutor.java:523)
at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:439)
at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
at oracle.as.install.bi.biconfig.standard.InstanceProvisioningTask.doExecute(InstanceProvisioningTask.java:81)
at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:112)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.as.provisioning.util.ConfigException:
Error creating ASInstance instance1.
Cause:
An internal operation has failed: Error in starting opmn server
Operation aborted because of a system call failure or internal error
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.fmwadmin.ASInstanceProv._createInstance(ASInstanceProv.java:317)
at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstance(ASInstanceProv.java:166)
... 18 more
Caused by: oracle.as.management.opmn.optic.OpticException: Error in starting opmn server
Operation aborted because of a system call failure or internal error
at oracle.as.management.opmn.optic.OpmnAdmin.executeCommand(OpmnAdmin.java:310)
at oracle.as.management.opmn.optic.OpmnAdmin.startOpmnServer(OpmnAdmin.java:87)
at oracle.as.provisioning.fmwadmin.ASInstanceProv._createInstance(ASInstanceProv.java:254)
... 19 more
Following is the entry in my host file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
172.20.114.46 AZVBIAPPDEV01.aspirezone.azf.local AZVBIAPPDEV01
172.20.116.52 AZVBIDBDEV01.aspirezone.azf.local
Could some one help me fixing this issue.....
Regards
Raj

Service Manager Data Warehouse Install - Analysis Server Configuration For OLAP Cubes Fail

Hello everyone,
I have an issue with my installation of the Data Warehouse for System Center Service Manager 2012 SP1.
My install environment is the following:
Windows Server 2012 – System Center Service Manager (Successfully Installed) - Virtual
Windows Server 2012 – System Center Data Warehouse (Pending) - Virtual
Windows Server 2012 – MS SQL Server 2012 – Physical, Clustered 1st of Four Servers
The SQL Server is a clustered installation with named instances, specifically for SharePoint and Service Manager. Each instance has its own IP address and dynamic ports are turned off. I’m installing using the domain administrator account and I also chose
to run the installer as administrator. The domain admin has sysadmin rights to the service manager server and instance I’m trying to install on. However, the account does not have sysadmin rights to some of the other instances.
The install is smooth up until it needs to connect to the Analysis server database. I have tried connecting to the analysis servers on other SQL servers on site and all were successful. The only difference between the older SQL servers, the SQL 2012 development
server and the SQL 2012 Production server I’m trying to install to is that the that the domain admin account doesn’t have sysadmin access on all the databases on the new production server. The SQL server is being installed and configured by a contractor so
if you all have troubleshooting suggestions, I’ll need to coordinate with the contractor.
Starting with the screen below, I began searching for help online. There seems to be no one else with this issue or it is not documented properly. I opened a ticket with MS, called the contractor and troubleshot with him, troubleshot as far as I could on
my own and I’m still at a loss as to what is preventing the installer from connecting specifically to the analysis server.
I first thought the installer was at issue or that the data warehouse sever was at issue. But all signs are pointing at the SQL server. The installer is able to connect to all the other SQL servers – including other 2012 servers (same versions) – so it can’t
be the installer. I’m pretty sure the SQL server is going to be at issue.
After looking at this error, I opened the resource monitor and clicked the dropdown to see if it was trying to connect to the correct server and it was. I then connected to the old and new test and development servers successfully. Then connected to the
SQL 2008 R2 production cluster successfully. I then compared the two servers. The only difference other than the version numbers is that the admin account doesn’t have sysadmin rights on all the SQL 2012 database servers. But the database servers are not the
problem. The analysis servers are.
I then checked the event logs and they are empty as far as this issue is concerned. Actually, there are no errors on the SQL 2012 production box and the Data Warehouse box. I then checked the log that the installer creates during every step of the installation
and this is what is created when the dropdown is clicked for the analysis server configuration screen. The log file location is:
“C:\Users\admin\AppData\Local\Temp\2\SCSMSetupWizard01.txt”
In the file is the following text.
01:03:34:Attempting connection to SQL Server 2012 management scope on SCSMSQL2012
01:03:34:Using SQL Server 2012 management scope on SCSMSQL2012
01:03:36:Collecting SQL instances on server SCSMSQL2012
01:03:36:Attempting connection to SQL Server 2012 management scope on SCSMSQL2012.johnsonbrothers.com
01:03:36:Using SQL Server 2012 management scope on SCSMSQL2012.johnsonbrothers.com
01:03:38:Found SQL Instance: SCSMSQL2012\PWGSQL2012
01:03:38:Found SQL Instance: SCSMSQL2012\SCSMSQL2012
01:03:39:Error:GetSqlInstanceList(), Exception Type: Microsoft.AnalysisServices.ConnectionException, Exception Message: A connection cannot be made. Ensure that the server is running.
01:03:39:StackTrace: at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)
 at Microsoft.AnalysisServices.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo)
 at Microsoft.AnalysisServices.XmlaClient.OpenConnection(ConnectionInfo connectionInfo, Boolean& isSessionTokenNeeded)
 at Microsoft.AnalysisServices.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
 at Microsoft.AnalysisServices.Server.Connect(String connectionString, String sessionId, ObjectExpansion expansionType)
 at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.GetASVersion(StringBuilder sqlInstanceServiceName)
 at Microsoft.SystemCenter.Essentials.SetupFramework.HelperClasses.SetupValidationHelpers.GetSqlInstanceList(String sqlServerName, Int32 serviceType)
I’m now investigating the issue according to this output, and decided to ask you all if you’ve run into this issue and found a resolution.

I am running into same issue . But I don't anything in the instances section related to portipv6 . I do see in the listener section , I tried to remove it . But it comes up again . Please help
<ConfigurationSettings>
<Security>
<RequireClientAuthentication>0</RequireClientAuthentication>
<SecurityPackageList/>
</Security>
<Network>
<Listener>
<RequestSizeThreshold>4095</RequestSizeThreshold>
<MaxAllowedRequestSize>0</MaxAllowedRequestSize>
<ServerSendTimeout>60000</ServerSendTimeout>
<ServerReceiveTimeout>60000</ServerReceiveTimeout>
<IPV4Support>2</IPV4Support>
<IPV6Support>2</IPV6Support>
</Listener>
<TCP>
<MaxPendingSendCount>12</MaxPendingSendCount>
<MaxPendingReceiveCount>4</MaxPendingReceiveCount>
<MinPendingReceiveCount>2</MinPendingReceiveCount>
<MaxCompletedReceiveCount>9</MaxCompletedReceiveCount>
<ScatterReceiveMultiplier>5</ScatterReceiveMultiplier>
<MaxPendingAcceptExCount>10</MaxPendingAcceptExCount>
<MinPendingAcceptExCount>2</MinPendingAcceptExCount>
<InitialConnectTimeout>10</InitialConnectTimeout>
<SocketOptions>
<SendBufferSize>0</SendBufferSize>
<ReceiveBufferSize>0</ReceiveBufferSize>
<DisableNonblockingMode>1</DisableNonblockingMode>
<EnableNagleAlgorithm>0</EnableNagleAlgorithm>
<EnableLingerOnClose>0</EnableLingerOnClose>
<LingerTimeout>0</LingerTimeout>
</SocketOptions>
</TCP>
<Requests>
<EnableBinaryXML>0</EnableBinaryXML>
<EnableCompression>0</EnableCompression>
</Requests>
<Responses>
<EnableBinaryXML>1</EnableBinaryXML>
<EnableCompression>1</EnableCompression>
<CompressionLevel>9</CompressionLevel>
</Responses>
<ListenOnlyOnLocalConnections>0</ListenOnlyOnLocalConnections>
</Network>
<Log>
<File>msmdredir.log</File>
<FileBufferSize>0</FileBufferSize>
<MessageLogs>Console;System</MessageLogs>
<Exception>
<CreateAndSendCrashReports>0</CreateAndSendCrashReports>
<CrashReportsFolder/>
<SQLDumperFlagsOn>0x0</SQLDumperFlagsOn>
<SQLDumperFlagsOff>0x0</SQLDumperFlagsOff>
<MiniDumpFlagsOn>0x0</MiniDumpFlagsOn>
<MiniDumpFlagsOff>0x0</MiniDumpFlagsOff>
<MinidumpErrorList>0xC1000000, 0xC1000001, 0xC100000C, 0xC1000016, 0xC1360054, 0xC1360055</MinidumpErrorList>
<ExceptionHandlingMode>0</ExceptionHandlingMode>
<MaxExceptions>500</MaxExceptions>
<MaxDuplicateDumps>1</MaxDuplicateDumps>
</Exception>
</Log>
<Memory>
<HandleIA64AlignmentFaults>0</HandleIA64AlignmentFaults>
<PreAllocate>0</PreAllocate>
<VertiPaqPagingPolicy>0</VertiPaqPagingPolicy>
<PagePoolRestrictNumaNode>0</PagePoolRestrictNumaNode>
</Memory>
<Instances/>
<VertiPaq>
<DefaultSegmentRowCount>0</DefaultSegmentRowCount>
<ProcessingTimeboxSecPerMRow>-1</ProcessingTimeboxSecPerMRow>
<SEQueryRegistry>
<Size>0</Size>
<MinKCycles>0</MinKCycles>
<MinCyclesPerRow>0</MinCyclesPerRow>
<MaxArbShpSize>0</MaxArbShpSize>
</SEQueryRegistry>
</VertiPaq>
</ConfigurationSettings>

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

Similar Messages

Maybe you are looking for