Solution manager 7.1 sp4 , error @Bytecode adpater installation

HI All,
    I am facing the below issue while executing the managed system wizard @ Bytecode adapter installation.
Error @ Managed system
Failed to create Introscope Agent Connector at: /usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors: - java.io.IOException: Cannot run program "null/bin/java" (in directory "/usr/sap/SMD/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors"): java.io.IOException: error=2, No such file or directory.
Error @ Diagnostic agent level
Jun 6, 2014 10:52:31 AM [Thread[Thread-19,5,main]
] Error
Operation Failed :
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 48161
at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94)
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:285)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.
at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.checkAuthorization(ConfigurationRuntimeInterfaceImpl.java:62)
at com.sap.engine.services.configuration.ConfigurationRuntimeInterfaceImpl.getConfigurationContext(ConfigurationRuntimeInterfaceImpl.java:48)
at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:159)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
1. As per standard note , patch levels are on sap recommended level only.
2. Created connector manually as per wily documentation , but still no use.
3. Given the permissions for temp,<SID>cluster etc.. as per sap notes and restarted all the services including sapstartsrv
4. Assigend SPML roles as suggested by note.
5. checked java environment and umask for diagnostic users , everything looks ok.
   Checked couple of notes related to the above issue ,
   1616058 - XSRF possible in SPML Services in AS Java
   1820230 - Byte Code Adapter Installation error in Solution Manager 7.1 Managed System Configuration step Configure Automatically
    1752441 - Introscope Agent Connector generation is done using JDK at: null

I would like paste few more error lines,
Jun 9, 2014 6:43:33 AM [Thread[FileSystemService_4cdecd7c,5,main]
] Error
[WHS] Failed to find javaPath for node 5818350
[EXCEPTION]
com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 58183
at com.sap.smdagent.vmmanager.impl700.VMManager._getSettings(VMManager.java:170)
at com.sap.smdagent.vmmanager.impl700.VMManager.getSettings(VMManager.java:156)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:94)
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:285)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.SecurityException: User is not authorized to access Configuration Manager.

Similar Messages

Manage Substitutes in Solution Manager 7.1 SP4

Hello,
I made configuration according to pdf:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a026ba4e-d5fa-2d10-4995-8e516dd372b0
It works fine in tx. SOLMAN_WORKCENTER but it is possibility to working at web browser ITSM Solution Manager 7.1 SP4 ?.
Please advise, if this functionality is possible at web browser.
Further information [here|http://pokazywarka.pl/3k9td2/] and [here|http://pokazywarka.pl/e5bars/] .
Thank you in advance.
Best regards,
SAPFan

Hello
How about asking Tammy Powlas, she is a SAP Mentor, volenteer for ASUG and highly active within the SAP community. I'm sure she wouldn't mind answering your question. You can even tweet iher this question url as she is also active on Twitter @tpowlas.
I can't help you out though by giving a meaninful answer to the question since I'm not familiar with these settings.
Best regards
Tom
PS: While SAPFan sounds cool I prefer writing a response to a person instead of an avatar, just a hint, if you use your real name people will take you more seriously on SCN.

Solution Manager 7.1 SP4: Session Timeout during SOLMAN_SETUP

Hello Experts,
We recently installed Solution Manager 7.1 SP4 on Linux/Oracle. We also completed the System Preparation and Basic Configuration part of the SOLMAN_SETUP wizard as well (which includes applying the Central Correction Note and other steps).
During the Managed System Setup Part, as soon as we click on the Configure System for a managed system - a new window opens up and immediately we get the below timeout messages:
This session will terminate due to inactivity in 0:00 minutes
To continue working in this session, choose 'Continue Session'
The above is immediately followed by the actual session timeout message:
This session terminated due to inactivity.
Click Close Popup
or to start new session, press F5.
Now even if we press F5/Refresh, the same cycle repeats.
I already checked the ICM timeout parameters as mentioned in the Guide and further findings with regards to ITS update as in thread WEBGUI Timeout immediately after logging in
Applying the latest kernel patch also did not help. The strange issue is that the session timeout occurs only the LMDB related services, wherease normal services like WEBGUI etc work fine.
Please suggest if anyone came across this issue, especially after update to SP04.
Thanks and Regards,
Srikishan

Hi,
Thanks, I will check the note steps and close this thread accordingly.
Perhaps I need to hone my notes searching skills !
Regards,
Srikishan

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

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 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 SR2: Error during step 1 installPolicyArchive

Hi,
I faced a really annoying problem in first step of Installation of a SAP Solution Manager 4.0 SR2 on Suse Linux Enterprise Server 10.
The Installation hangs in Phase 1 installPolicyArchive.
I think i have passed all prerequisites before starting the Installation.
Perhaps for help:
i set the Environment Variables as follows:
JDK_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
JRE_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre
JAVA_BINDIR=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/bin
JAVA_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
SAPINST_JAVA_HOME=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
JAVA_ROOT=/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/
As you see Java Version is java-1_4_2-sun-1.4.2.11.
The Error in sapinst.log is as follows:
ERROR 2009-03-03 15:58:44
FSL-00001 System call failed. Error 2 (No such file or directory) in execution of system call 'realpath' with parameter (/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre/lib/security/local_policy.jar), line (346) in file (syuxclink.cpp).
ERROR 2009-03-03 15:58:44
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2009-03-03 15:58:44
FCO-00011 The step installPolicyArchive with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|1|0|NW_getJavaHome_jcePolicy|ind|ind|ind|ind|0|0|installPolicyArchive was executed with status ERROR .
Can anyone help me solve the problem?
Thanks beforehand and Best Regards,
C. Peifer

> I'm on 32 bit
Ok - then the JDK correct.
sapinst searches for a policy file, is the given filename there?
/usr/lib/jvm/java-1_4_2-sun-1.4.2.11/jre/lib/security/local_policy.jar

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 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.
<i><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 .</i>
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 Diagonostic Agent:Start Error

Hi All,
We are facing problem while starting SMD agent in Solution Manager System in I series.
The Landscape browser in the Solution Manager Diagnostics shows SMD Agent Status : Agent not found.
We tried starting the same through: \usr\sap\SMD\J98\script but while doing so we were getting following error:
Starting at 2010/01/14 16:24:21
Startup Profile: "/usr/sap/SMD/SYS/profile/START_J98_SPLBWPRD"
Starting Programs
14.01.2010 16:24:21
ShmDetach
FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fop
en()
(2465) Spawning program "/usr/sap/SMD/exe/jcontrol pf=/usr/sap/SMD/SYS/profil
e/SMD_J98_SPLBWPRD" asynchronously...
Any inputs are much appreciated.
Regards,
Prasad

I just saw a different forum with NIECONN_REFUSED, his was fixed after the port number was corrected.
Try 5xx04.
Edited by: Ryan Cossette on Jan 18, 2010 6:47 PM

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.

Error in Import JAVA DUMP phase in Solution Manager installation.

Hi,
when i am installing Solution manager i am getting error in import java dump phase on windows and oracle database. i installed java 1.4.2_09 . plz anybody give the solution. Its very urgent.
Thanks,
Venkat.

Hi,
1. Did you select java path (Export CD/DVD) while intsallation? Check once again.
2. Add JAVA_HOME = Java path in environment variable.
3. What is the exact error, you got it, post error here.
Regards,
Srini Nookala

ARIS Solution manager synchronization error

Hi all,
we have integrated ARIS software with solution manager for the business process modelling.
the problem is data is getting synchronized from solution manager to ARIS. no error is coming.
but when we make some changes in the ARIS structure and tried to synchronize back to solution manager.
the changes are not getting reflected in solution manager.
kindly advice in this regard.
Regards,
Subhashini

Hi Solmaic,
Thanks for your reply.
ya that is what exactly is happening.
we have just now started working on ARIS. so we have synchronized a project from solution manager.
the possiblities we tried are
1. synchronized the project and changed the name of the project. and synchronized back but nothing is changed in solution manager.
2. Changed the anme of a scenario and changed a document and synchornized back but that change is also not reflected.
3. we have created a VACD, made the process type as scenario. but in the log we have got an information that it has skipped the scenario.
kindly guide in this regard.
Regards,
Subhashini.

Error during installing Solution Manager at step 18 of 25 (import ABAP)

During installing Solution Manager, I got following errors and can't compleate installing.
==========================
ERROR 2007-02-15 11:05:22
CJS-30022 Program 'Migration Monitor' exits with error code 2. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-02-15 11:05:22
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 .
==========================
and the import_monitor.java.log says,
========================
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
Required system resources are missing or not available:
Import directory '
jlc-w1\DVD.image\SolutionManager\InstallationExport\EXP1' does not exist;
Import directory '
jlc-w1\DVD.image\SolutionManager\InstallationExport\EXP2' does not exist;
Import directory '
jlc-w1\DVD.image\SolutionManager\InstallationExport\EXP3' does not exist;
Import directory '
jlc-w1\DVD.image\SolutionManager\InstallationExport\EXP4' does not exist.
====================================
The folder
jlc-w1\DVD.image\SolutionManager\InstallationExport\EXP1 ,2 , 3 ,4 exists, and can be accessed. (In previouse steps, those folders are accessed, correctly)
Strictly speaking,
jlc-w1\DVD.image\ is mapped as drive z:
I also tried put InstallationExport\EXP1 , 2, 3 and 4 at local drive c:
However the result is same, I got same error.
Does anyone know this problem?
Please help me.

Thank you for the information,
I have tried with following condition.
I've copied image from DVD to
C:\EXP1
C:\EXP2
C:\EXP3
C:\EXP4
(C: is local drive)
Then compared all copied files in the local drive and DVD image. Verified all files are identical. also made all files and folder under those folder have R/W permission.
However I still get same error. ( I did this from fresh OS and new installation as well)
I used filemon.exe during installation to monitor file access. During other step of the installation, files under EXP1,2,3,4 were accessed successfully.

Solution manager 7.1 sp4 , error @Bytecode adpater installation

Similar Messages

Maybe you are looking for