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.

Similar Messages

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

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

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

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.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 Installation error on vmware

Hi guys,
I try to install the solution Manager 4.0 SR4 in a vmware server Win2003 64bit
and get the following error message in phase 17 (import ABAP)
Execution of the command "C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 2. Output:
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Required system resources are missing or not available:
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP1' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 1\EXP2' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP3' does not exist;
Import directory '
hyperv01\c$\SAPINSTALL\SAP SOLUTION MANAGER 7.0 Installation Export 2\EXP4' does not exist.
of course the path exists and the further dvd locations where also found?
is ther something wrong with the naming of the install dir?
must I have a character for the "harddrive"
Plse help
thank you and br
Wolfgang

Hello shareef,
there is no extra recommendation from SAP regarding SolMan on vmware.
SAP supports installations on vmware wheanwhile also for productive systems (plse check PAM).
The experience I have for my installation:
I works fine til now, no probs.
cu Wolfgang

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.0 Installation Error on Import ABAP -Test DB connection

Hi, SDN fellows.
I am installing Solution Manager 7.0. In Step 16 of 44 - Import ABAP, I encountered an error when the installer was testing the database connection. It failed at this command:
R3load.exe -testconnect
Below is the error I copied from the log viewer. Thanks for all possible advices/suggestions to fix this issue.
=================
WARNING 2011-07-12 03:51:49.188
Execution of the command "C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 2. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110712035148
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 99
WARNING[E] 2011-07-12 03:51:49.188
CJS-30023 Process call 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
ERROR 2011-07-12 03:51:49.204
FCO-00011 The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|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|testDatabaseConnection was executed with status ERROR .
=============
KC

cont....
4 ETW000 33 1.576524
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 1112312
4 ETW000 24 1.576548
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on open 19 1.576567
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 19 1.576586
4 ETW000 [dev trc ,00000] DbSlRead - Error 103 (dbcode 208) on fetch 13 1.576599
4 ETW000 [dev trc ,00000] DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
4 ETW000 18 1.576617
4 ETW000 [dblink ,01299] ***LOG BZA=>table SVERS does not exist on database [dblink#5 @ 1299]
4 ETW000 8060 1.584677
4 ETW000 [dev trc ,00000] Wed Jul 13 23:41:19 2011 41342 1.626019
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000002234118
4 ETW000 25 1.626044
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 3649 1.629693
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.629726
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629745
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 27 1.629772
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
4 ETW000 19 1.629791
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "DDNTT" ]
4 ETW000 28 1.629819
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.629839
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM DDNTT FAILED 277 1.630116
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000003234118
4 ETW000 44 1.630160
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 459 1.630619
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 33 1.630652
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 18 1.630670
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 29 1.630699
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
4 ETW000 23 1.630722
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "DDNTT" ]
4 ETW000 29 1.630751
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 20 1.630771
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM DDNTT FAILED 267 1.631038
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000004234118
4 ETW000 43 1.631081
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 436 1.631517
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.631549
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 18 1.631567
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
4 ETW000 58 1.631625
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
4 ETW000 19 1.631644
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "DDNTT" ]
4 ETW000 28 1.631672
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.631693
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM DDNTT FAILED
4 ETW000 284 1.631977
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 31 1.632008
4 ETW000 [twdydbacc.c ,00568] i:0 8690 1.640698
4 ETW000 [twdydbacc.c ,00569] db_fd_p.fname: PGMID 20 1.640718
4 ETW000 [twdydbacc.c ,00570] db_fd_p.is_key: 0 11 1.640729
4 ETW000 [twdydbacc.c ,00571] db_fd_p.offset: 0 10 1.640739
4 ETW000 [twdydbacc.c ,00572] db_fd_p.db_length: 0 10 1.640749
4 ETW000 [twdydbacc.c ,00573] db_fd_p.fixed_length:4 10 1.640759
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000005234118
4 ETW000 40 1.640799
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 434 1.641233
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.641265
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 75 1.641340
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 31 1.641371
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
4 ETW000 18 1.641389
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 COMPCNT FROM "XXXXT" ]
4 ETW000 28 1.641417
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.641438
4 ETW000 [dev trc ,00000] NTAB: SELECT COMPCNT FROM XXXXT FAILED 269 1.641707
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000006234118
4 ETW000 44 1.641751
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 437 1.642188
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.642220
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 18 1.642238
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.642266
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
4 ETW000 19 1.642285
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM "XXXXT" ]
4 ETW000 27 1.642312
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 70 1.642382
4 ETW000 [dev trc ,00000] NTAB: SELECT VERSION FROM XXXXT FAILED 273 1.642655
4 ETW000 [dev trc ,00000] DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000007234118
4 ETW000 44 1.642699
4 ETW000 [dev trc ,00000] ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
4 ETW000 435 1.643134
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
4 ETW000 32 1.643166
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 19 1.643185
4 ETW000 [dev trc ,00000] sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
4 ETW000 28 1.643213
4 ETW000 [dev trc ,00000] Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
4 ETW000 20 1.643233
4 ETW000 [dev trc ,00000] ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 DBASE FROM "XXXXT" ]
4 ETW000 30 1.643263
4 ETW000 [dev trc ,00000] Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
4 ETW000 21 1.643284
4 ETW000 [dbntab.c ,00000] *** ERROR => NTAB: SELECT VERSION/DBASE FROM XXXXT FAILED
4 ETW000 324 1.643608
4 ETW000 [dbntab ,01276] ***LOG BZY=>unexpected return code 103 calling NTAB [dbntab#4 @ 12761]
4 ETW000 27 1.643635
2EETW000 sap_dext called with msgnr "2":
2EETW000 -
db call info -
2EETW000 function: db_ntab
2EETW000 fcode: NT_RDTDESCR
2EETW000 tabname: TADIR
2EETW000 len (char): 5
2EETW000 key: TADIR
2EETW000 retcode: 2
4 ETW000 [dev trc ,00000] db_con_rollback (con_da={R/3,0,0},th_rollback=1,tx=0)
4 ETW000 9946 1.653581
4 ETW000 [dev trc ,00000] Rollback: TestConnection(1) successful 36526 1.690107

Solution Manager Learning Map http error 403

Hi,
I created a new learning map in solution manager using solar_learning_map, when I attempted to display the learning map in the web browser i received the following error.
<URL> call was terminated because the corresponding service is not available.
The termination occurred in system ISD with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
If anyone else has experienced this error before can you please give me some guidance on resolving this issue.

The Note exists in service marketplace. (Topic is Inactive services in the Internet Comm Framework).Here is the solution as per the Note.
Solution
Listed below are some services that must be activated in the system
depending on the operational scenario:
Support for the Internet protocol (HTTP, HTTPS and SMTP) in the SAP Web Application Server
/default_host/sap/public/icman
Note: After you have installed SAP Web Application Server, you must ensure that this service is activated in transaction SICF. Through this the ICMan process can (for example) make decisions concerning the distribution of HTTP requests to the corresponding server.
Using load distribution
with the message server
/default_host/sap/public/icf_info
/default_host/sap/public/icf_info/logon_groups
/default_host/sap/public/icf_info/urlprefix
with the Web Dispatcher
/default_host/sap/public/icf_info
/default_host/sap/public/icf_info/icr_groups
/default_host/sap/public/icf_info/icr_urlprefix
Using Business Server Pages (BSP)
/default_host/sap/bc/bsp/sap
/default_host/sap/bc/bsp/sap/system
/default_host/sap/bc/bsp/sap/public/bc
/default_host/sap/public/bc (available for 620 with Support Package 34)
/default_host/sap/public/bc/ur (available for 620 with Support Package34)
/default_host/sap/public/bsp/sap/public
/default_host/sap/public/bsp/sap/public/bc
/default_host/sap/public/bsp/sap/system
/default_host/sap/public/bsp/sap/htmlb (as of Release 620 Support Package SAPKB62026)
Note: In addition to these general BSP services, you still have to activate the corresponding application services in the ICF tree. The service for the application is generally found under the ICF node /default_host/sap/bc/bsp/sap/<application>.
Using the BSP logon procedure
/default_host/sap/public/bsp/sap
/default_host/sap/bc/bsp/sap/system
/default_host/sap/public/bsp/sap/public
/default_host/sap/public/bsp/sap/system
BSP test applications for troubleshooting
/default_host/sap/bc/bsp/sap/it00
/default_host/sap/bc/bsp/sap/sbspext_htmlb
/default_host/sap/bc/bsp/sap/sbspext_xhtmlb
/default_host/sap/bc/bsp/sap/htmlb_samples
As of Release 6.30:
/default_host/sap/bc/bsp/sap/bsp_verificatio
Using Business Information Warehouse (BW)
/default_host/sap/bw
Web Applications
/default_host/sap/bw/BEx
/default_host/sap/bw/Mime
Reporting agent preliminary calculation
/default_host/sap/bw/ps
Drag and Relate in the portal
/default_host/sap/bw/dr
Data access using XMLA
/default_host/sap/bw/xml and all subordinate subservices
Document integration in the BEx Analyzer and Web Applications.
/default_host/sap/bw/doc and all subordinate subservices
Formatted reporting
/default_host/sap/bw/ce_url
Assignment of SAP icons
/default_host/sap/public/bc
/default_host/sap/public/bc/icons
/default_host/sap/public/bc/icons_rtl
/default_host/sap/public/bc/webicons
/default_host/sap/public/bc/pictograms
Assignment of Web Dynpro ABAP (WDA) applications
/default_host/sap/bc/webdynpro
/default_host/sap/public/bc
/default_host/sap/public/bc/ur
/default_host/sap/public/bc/icons
/default_host/sap/public/bc/icons_rtl
/default_host/sap/public/bc/webicons
/default_host/sap/public/bc/pictograms
/default_host/sap/public/bc/webdynpro/* (ssr, mimes, and so on)
/default_host/sap/public/myssocntl
Note: In addition to these general WDA services, the corresponding application services in the ICF tree also need to be activated. The service for the application is generally found under the ICF node /default_host/sap/bc/webdynpro/sap/<application>.
Assignment of Web Dynpro ABAP (WDA) development environment
/default_host/sap/bc/webdynpro/sap/public/bc/viewdesigner/
/default_host/sap/bc/wdvd/
/default_host/sap/bc/webdynpro/sap/configure_application
/default_host/sap/bc/webdynpro/sap/configure_component
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_appl
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_comp
/default_host/sap/bc/webdynpro/sap/wd_analyze_config_user
Note: These ICF nodes are used for the WDA configuration editor ONLY. The nodes are only allowed to be active in a development system, and under no circumstances in a production system (due to a security risk).
WDA test applications for troubleshooting
/default_host/sap/bc/webdynpro/sap/wdr_test_events
/default_host/sap/bc/webdynpro/sap/wdr_test_ui_elements
/default_host/sap/bc/webdynpro/sap/wdr_test_table
/default_host/sap/bc/webdynpro/sap/wdr_test_popups_rt
ICF test applications:
/default_host/sap/bc/echo
Among other things, this service returns information about the registration procedure being used, the header and form fields, and the generated SSO cookie for the executed request. Therefore, this service should only be activated for troubleshooting purposes.
/default_host/sap/bc/error
This service generates some error situations in the system and should only be activated for troubleshooting purposes.
/default_host/sap/bc/srt/xip/sap
You want to fix the Web service error message "Could not determine WSDL address (ICF_ERROR), SRT_REG038" in connection with XI services.
Using Support Package SAPKB62006, the following problems were solved in connection with inactive services:
The "RAISE_EXCEPTION" ABAP runtime error no longer occurs for an inactive host.
The error text "Forbidden" was replaced with "Service is not active" for an inactive service.
Thanks
Sudhan Shan

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 Diagnostics Self Check Error with Enterprise Manager

I'm trying to get the Solution Manager Self Diagnostics Self Check running,
but I'm always getting the follwing Error:
The Enterprise Manager on host 'hdeas81' and port '6443' cannot be reached.
The Log File of the Introscope Manager shows the following line:
6/29/09 01:15:36 PM CEST [INFO] [Manager.PostOfficeHub] Server listening for incoming ssl socket connections on port 6443
Netstat -a is also showing that Port 6443 is open and Listening.
The Port is also reachable via telnet.
any suggestions what might be the problem?
Thanks in advance
Marco

thanks, but i'm trying to get a ssl connection on port 6443.
I have also another error in the diagnostics check (maybe related)
An unexpected error occured
in Detail i get the error:
java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connection refused: connect
     at org.w3c.www.protocol.http.HttpURLConnection.error(Unknown Source)
     at org.w3c.www.protocol.http.HttpURLConnection.checkReply(Unknown Source)
     at org.w3c.www.protocol.http.HttpURLConnection.getResponseCode(Unknown Source)
     at com.sap.sup.admin.selfcheck.checks.helper.HttpHelper.getHttpResponseCode(HttpHelper.java:48)
     at com.sap.sup.admin.selfcheck.checks.wily.em.UICheck.process(UICheck.java:78)
     at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165)
     at sun.reflect.GeneratedMethodAccessor541.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
     at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)
     at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
     at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
     at java.lang.Thread.run(Thread.java:534)

Solution Manager 4.0 Installation Error

am doing the Solution Manager 40 installation on AIX as root.
FYI: We are using central SLD.
During the installation in phase 30 "check DDIC password"
Sapinst stops with the following error.
In sapinst.log the error is:
In the installation log it says ERROR 2006-09-01 16:53:47
FRF-00025 Unable to call function. Error message: Large time
difference between application server a .
INFO 2006-09-01 16:53:47
RFC connection closed.
In sapinst_dev.log the error is:
FCO-00011 The step runRUTTTYPSET with step key
|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_I
nstance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|1|0|runRUTTTYPSET
was executed with status ERROR .
I did tried retry,stopped exit out and stopsap and stared again.
Even I upgraded it to the latest kernel(75) and tried again but no luck.
I see the follwoing error in dev_w0:
A Large time difference between application server and database..
A
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 13155]
A *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY
MODE. [zdate.c 1390].
Should I rollback to the old kernel which was 52, which came with
installation DVD's ?
The permissions of /usr/sap/trans and files and dir below is ok and owned by sidadm.
Does anyone has any idea ?
Thanks & Regards
Haq

Hi,
Could you please tell me what was the solution to this error. I am facing the similar issue.
Please help, thanks
Regards,
Nitin Nayyar

Solution Manager 4.0 install Error

Similar Messages

Maybe you are looking for