Configure TMS in fresh installed Solution Manager system

Hi Expets,
I have fresh Installed Solution manager. Configure TMS and now want to configure solution manger so that I can monitor all our SAP system from Solution manager. How I configure our SAP system in solution manager?
Also would like to know after TMS implementation if we like to use ChaRM or CTS+ so what changes required in current TMS setting? Thanks in advance.

Hello,
No Deejoy, I provided you with how to resource to do the things you requested.
TMS is transport Management System.
If you want to manage transports with an enhanced product CTS+ I provided the configuration guide.
If you want to implement ChaRM, I pointed you to the Wiki.
If you want to inegrate CTS+ with ChaRM, I also provided you with resources.
And lastly, I directed you to RKT-SOLMAN which can help you configure any aspect of Solution Manager.
But I do not see where I said to manage TMS on Satellite systems you need to implement ChaRM.
Charm was only raised, because you raised it in your question.
You have all the resouces you require to address everything you raised.
This is what is provided in my earlier reply.
Regards,
Paul

Similar Messages

Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

Hi Folks,
While doing Managed System Configuration for Soman system i am getting error in SSO Setup
Currently I am in
8. Configure Automatically :Single Sign On Setup
This is i am going for managed System (Solution Manager System Itself)
Below is error log..
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
Screen shot attached.
Found SID for SSO ACL entry : SMP
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Exception
java.rmi.RemoteException: Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
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:331)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
... 8 more
Regards,
San

Hi Sandeep,
It seems authorization issue. Please check the below SAP Note :
1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
Hope this helps.
Thanks & Regards,
Nisha

Configure MOPZ after EHP1 in solution Manager

Dear Experts,
We have fresh installed SAP Solution Manager 4.0 on windows 2003. Now we have to update EHP1 with SP26 i.e.SAP EHP 1 for SAP Solution Manager 7.0.Now I want to configure Maintenance Optimizer in this Solution manager.So that We can downlaod Support Package via this solution Manager.
What is pre-request to configure MOPZ .When I run solution_admin transistion .it is going to portel and ask SAP Web Application ask user ID and Password.
Whats User ID will come here ?. I am giving J2EE_admin and Basis user ID. But its not taking these Users.
Whats User ID it will take.
How to configure MOPZ , Please give me step by step process . So that I can configure MOPZ.
i will give thanks in advanced for my help
regards

When I am using User ID J2EE_ADMIN and Password as below
SAP Web Application Server
User Name : J2EE_ADMIN
Password:
My default client is 100 and this user ID and password is working perfectelly in sap gui logon.
Belwo error mesee come during user ID J2EE_ADMIN and Password .
Error when processing your request
What has happened?
The URL http://testserver:8000/sap/bc/webdynpro/sap/wd_sise_main_app was not called due to an error.
Note
The following error text was processed in the system SAL : Die URL enthält keine vollständige Domainangabe (testserver statt testserver.).
The error occurred on the application server testserver_SAL_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: STARTUP_CHECKS of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SAL in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server testserver_SAL_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server testserver_SAL_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 100 -u: J2EE_ADMIN -l: E -s: SAL -i: testserver_SAL_00 -w: 0 -d: 20110813 -t: 204925 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
what it show.
regards

Error at step 42/45 while install Solution Manager 4.0

Hi SAP guru,
I'm install Solution Manager 4.0 on Windows 2003 R2 with Oracle10g
and JSDK 1_4_2_16, while facing step 42/45 (Configure System Landscape Directory). Its shown error below.
ERROR 2008-01-17 16:02:04
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile java.log: 'JSE'.
ERROR 2008-01-17 16:02:04
FCO-00011 The step configSLDMainLocalMapSecRolesToUsers with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0|configSLDMainLocalMapSecRolesToUsers was executed with status ERROR .
Any solution for this problem?
PS. I was ran sapinst.exr SAPINST_SKIP_ERROR=true on step 39 (Install Software Units) after set SDM mode = integrated.
Thanks in advance

Hi Snehal,
The log I paste above was too many days ago. Thus, I'm get a new one from Log Browser for you.
ERROR 2008-01-21 19:05:35
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile java.log: 'JSE'.
ERROR 2008-01-21 19:05:35
FCO-00011 The step configSLDMainLocalMapSecRolesToUsers with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0|configSLDMainLocalMapSecRolesToUsers was executed with status ERROR .
and this from sapinst_dev.log as your requested.
INFO 2008-01-21 19:05:35
 CJSlibModule::writeInfo_impl()
Execution of the command "C:\j2sdk1.4.2_16\bin\java.exe -classpath E:/usr/sap/SOL/DVEBMGS01/j2ee/cluster/server0/apps/sap.com/tclmctcutilbasic_ear/servlet_jsp/ctc/root/WEB-INF/classes/ com.sap.ctc.util.ConfigMainExt XXXXXX ahosapso:50100 J2EE_ADMIN XXXXXX" finished with return code 0. Output:
TYPE=A STATE=401 INFO_SHORT=Error connecting to http://ahosapso:50100/ctc/ConfigServlet?param=com.sap.ctc.util.SecurityRoleConfig;MAP_SECURITYROLE_TO_USER;ROLE=DataSupplierLD,USER=SLDDSUSER,COMPONENT=sap.com/com.sap.lcr*sld,HOST=ahosapso,P4PORT=50104,J2EE_ADMIN=J2EE_ADMIN,J2EE_PASSWORD=des19(66|31|151|231|117|153|233|51|218|54|). The provided user data might be incorrect or user might be locked. CONFIGURATION=
TRACE [iaxxejsexp.cpp:188]
 EJS_Installer::writeTraceToLogBook()
NWException thrown: nw.configError:
Java EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile java.log: 'JSE'.
ERROR 2008-01-21 19:05:35
 CJSlibModule::writeError_impl()
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile java.log: 'JSE'.
TRACE [iaxxejsbas.hpp:460]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2008-01-21 19:05:35
FCO-00011 The step configSLDMainLocalMapSecRolesToUsers with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0|configSLDMainLocalMapSecRolesToUsers was executed with status ERROR .
TRACE
<html><head></head><body>An error occurred while processing service SAP Solution Manager 4.0 Support Release 1 > SAP Systems > Oracle > Central System > Central System Installation. You may now<ul> <li>press Retry to repeat the current step.</li> <li>press the View Log button to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul>Log files are written to C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.</body></html>
TRACE [iaxxgenimp.cpp:1093]
 showDialog()
waiting for an answer from gui
Edited by: jitpanu sriudomwat on Jan 24, 2008 3:47 AM

Error in RFC SM_DM1CLNT800_BACK to Solution Manager System Message no. STMWFLOW025

Hi,
I am facing an issue in our Test landscape. One of our team member uninstalled solman system which was connected to all other system. CHarms was partly configured in it, so other technical team used to reach to solman for creating TR# and also release the TR from Solman. Now that the system was removed abruptly we are facing this issue and I have checked few things as below:
1) Checked for domain link entries in STMS and TP profile file, could not find anything. Nor there is any option to delete domain link as there is for create
2) Checked the RFC its was working as new Solman with the same host name and other details has been brought back with out any settings yet in it.
3) I deleted the RFC SM_DM1CLNT800_BACK in the managed system and had a backup copy created before deleting it. But still get the error "Error in RFC SM_DM1CLNT800_BACK to Solution Manager System" in more help I see this Message no. STMWFLOW025
4) Message no. STMWFLOW025 - It gives me an indication that this is something to do with the domain link and the Workflow of the TMS.
5) Checked BCOS_CUST table and it has an entry for this RFC. - Should I be removing this entry and will this resolve the issue?
I need help in resolving this issue and also if one of you could share a blog for the proper configuration removal process of a managed system from Charms and ITSM I think it would be very helpful. I could only find process and step towards configuration and not how to unconfigure the system.
Thanks in advance
Ashish

Hi
The issue is now resolved, this is how I did it.
1) Removed entries from BCOS_CUST from client 000 for OSS_MSG which was pointing to the RFC name
Then got another error:
No RFC connection to the central lock information management system.
The project lock functionality is active in the local system, but there is no RFC connection to the Solution Manager system.
2a) Ran the report in SA38 TMW_CONTROL_PROJECT_LOCK with selection for Deactivate the "project lock functionality".
2) Filled the "Deactivate Project Lock" field with "X" then clicked EXECUTE.
Problem got Solved.
Thanks
Ashish

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.

I am trying to install solution manager 7.1

Hi,
I am trying to install solution manager 7.1
platforn O.S Windows X86_64 2008 server
              D B orcale 11.2
Install has got stuck in the phase 33 "install java engine"
when I check sapinst_dev.log it stopped updating any log after the step
TRACE      2011-07-06 09:19:12.984 [syxxcnode.cpp:454]
           CSyNodeImpl::move(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/SDMKIT.2.log, ISyNode::CopyMoveMode_t 0x3)
           lib=syslib module=syslib
Moved C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/SDMKIT.log to C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/SDMKIT.2.log
INFO       2011-07-06 09:19:12.984 [synxcpath.cpp:814]
           CSyPath::createFile() lib=syslib module=syslib
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ORA\CENTRAL\AS\SDMKIT.log.
INFO       2011-07-06 09:19:13.000
processing bar shows "Extracting pack/sdmrepository.sdc"
Has any one come across this issue....
thank you so much
Regards,
Jay

Hello,
The default parameters for the JVM are not adaquate for an X64 system, and seem to be for 32 bits systems.
This means when the J2ee folder is created in usr\sap...and the JVM is started with the default java parameters on an X64 system, it will fail. The installation guide should refer you to the JVM settings, but if you are using SAPJVM, then Note 1603093 has the required parameters.
As an example the maxheap needs to be set to 2048, but it will only be set to 1024.
In order to resolve, you need to find the Note for the Java parameter settings for your JVM, be it Oracle (Sun), IBM or SAP, run the configtool to modify them accordingly.
Then once this is done re-start the install, using the existing configuration file, it will advance rapidly to the point it failed, and then start he JVM successfully. Or you can start it in the SAPMMC and once you are satisfied it will start with the parameters, restart the install. This is a better method because
it is much faster if you make a mistake and it fails on a typo in a parmeter setting.
Unfortunately you cannot set the JVM paramters prior to the JVM being created, and it has just been created at the phase in which your install has failed.
Hope this insight gets you going again.
Regards,
Paul

Question for installing Solution Manager & ECC 5.0

Any idea for installing Solution Manager 3.2 on Windows server 2003 with Oracle9i problem when install Database Instance. Installation failed when the intallation progress went to Oracle Post-Load Action.
The message from startsap log file is
"running C:\usr\sap\T01\SYS\exe\run/sapstart.exe name=T01 nr=03 SAPDIAHOST=saptest02 -Wait
start service SAP01_03 on machine
saptest02
OpenService of SAPT01_03 failed. Error#: 1060
CreateNamedPipe for
saptest02\pipe\SAP01_03 Failed, Extended Error #2
start service SAP01_03 on machine
saptest02
OpenService of SAPT01_03 failed. Error#: 1060
C:\usr\sap\T01\SYS\exe\run/sapstart.exe=>sapparam(1c): No Profile Used."
Another question is about installing the Oracle database software: should we choose Create Databse or not when install Oracle Server Software only?
Is my installation process as following correct?
->SELECT A PRODUCT TO INSTALL:
Oracle9i Database 9.2.0.1.0
->WHAT TPYE OF INSTALLATION DO YOU WANT:
Enterprise Edition
->SELECT A DATABASE SUITED TO YOUR NEEDS:
Software only
After end of installation
install Oracle9i Client 9.2.0.1.0->Administrator
Thanks a lot

Hi Shusen, I´m trying to do the same think (Install ECC IDES with Oracle 9i in one computer for educational propose), can you help me with this:
1.I made the same Oracle install process because when I tried with sapserver.cmd nothing happened, for that reason i made:
SELECT A PRODUCT TO INSTALL:
Oracle9i Database 9.2.0.1.0
->WHAT TPYE OF INSTALLATION DO YOU WANT:
Enterprise Edition
->SELECT A DATABASE SUITED TO YOUR NEEDS:
Software only
After end of installation
I did not install client, is this correct?
2.After install this, I run the sapins.exe but show me this error: INSTALL FIRST SAP J2EE ENGINE, I download the JAVA SDK from JAVA page (java_ee_sdk-5-windows) but did not fix the problem: Do you know what file is this? Or, where is it in the DVD installation?
Thanks in advance if you or somebody can help me and excuse me if the answers are obviously, but I´m not a system engineer I´m only try to install IDES for learn SAP WM.
Thanks.

Support message not getting reflected in Solution manager system

Hi,
In satellite system support message is getting created, message number"...." successfully created in service desk.
When i check in solution manager system in crm_dno_monitor the message that i created in satellite system is not getting reflected in solution manager. I removed the varients and then executed . The result is still the same.
Service desk was configured from our Development system (Client 320) to solution manager. I wanted the support desk to work from my another cleint in same system to Solution manager.
What can be the possible problem.
Thanks & Regards,
Balaji.S

Hi Gurus,
Issue got resolved, the problem was with the variant which was assigned as default for the tcode.
Thanks & Regards,
Balaji.S

Error while installing Solution manager

Hi,
It is urgent Please.
I am trying to install Solution manager 4.0 on Linux and Maxdb.
But during Phase Configure UME i am getting below error.
ERROR 2007-12-17 16:48:16
 CJSlibModule::writeError_impl()
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)
TRACE [iaxxejsbas.hpp:460]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2007-12-17 16:48:16
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 .
Can anybody please give me the solution on this.
Vinnu.

1. Check the rights of the user with which you are installing.
2. Check if any firewall is running.
3. Check the JDK version, you should go with j2sdk1.4.2_09.
regards
tamilboy

Error on install Solution Manager : Jcmon(error 4). No space left on device

Hi
I am having a problem installing Solution Manager 7.0 EHP1- AIX 6.1 DB2 9.7
During the unpacking phase error:
FCO-00011 The step unpack with step key was executed with status ERROR (Last error Reported by the step: Execution of the command "/ tmp/sapinst_exe.4325530.1325543592/SAPCAR-x-v-i-r / usr / sap / SMG / SYS / exe / run-f / MidiasInstall / IMKernel/DATA_UNITS/K_701_U_AIX_PPC64/DBINDEP/SAPEXE.SAR, "finished with return code 4. Output
<html> <head> </ head> <body> An error occurred while processing option EhP1 SAP Solution Manager 7.0> SAP Systems> IBM DB2 for Linux, UNIX, and Windows> Central System> Central System (Reported by the last step error: Execution of the command "/ tmp/sapinst_exe.4325530.1325543592/SAPCAR-x-v-i-r / usr / sap / SMG / SYS / exe / run-f / MidiasInstall/IMKernel/DATA_UNITS/K_701_U_AIX_PPC64 / DBINDEP / SAPEXE.SAR, "finished with return code 4. Output:
Sapce: processing archive / MidiasInstall/IMKernel/DATA_UNITS/K_701_U_AIX_PPC64/DBINDEP/SAPEXE.SAR (version 2.01)
x jcmon
Sapce: error writing to / usr / sap / SMG / SYS / exe / run / jcmon (error 4). No space left on device).
Note: I downloaded the newest sapinst but not resolved.
SAPinst build information:
abi version: 722
make variant: 720_REL
build: 1296039
compile time: 26 Dec 2011 02:46:25
Media used:
51041320 - DB2 9.7 - Client
51041317_1 DB2 9.7 - RDBMS
51040438 - Export
51040437 - Installation Master
51040439 - Java SW Comp
51040584 - Kernel
Filesystem GB blocks Free% Used Iused% Iused Mounted on
/ dev/hd2 5:00 49 709 2.76 45% 8% / usr
/ dev/fslv00 15:00 15:00 15 1% 1% / usr / sap / SMG
any idea ?

Hi,
The /usr/sap file system looks fine.
Could you also check the file space on the /tmp file system? This is usually less and SAPInst can fill this up very quickly.
Ideal to create a seperate SAPInst directory rather than use the default /tmp/sapinst_instdir.
Regards,
Srikishan

In solution manager system not showing all the system in SLD

Dear Gurus,
During the installation of solution manger sysyem i selected as a Central SLD as solution manager
Later installed ECC 6.0 and EP systems selected SLD as solution manager system during the instllation.
If i login in to http://hostname:50000/sld (solution manger system) and the screen also not showing all the options also. some options missing in the tab. Wat I need to do to see all the options clearly.
It is not showing all the systems if i check in EP and ECC for SLDCHECK it is not givng any errror.
But if i login into solution manger not able to see all the system in SLD.
Regards

Thanks for reply
it is not showing all the systems

Can't Install Solution Manager on Suse Linux Enterprise Server 10 - JAVA

Hello everyone!
I've been trying to complete the pre-requisites in order to install Solution Manager SR2 on Suse Linux Enterprise Server 10 x64 - SP1.
There's only one last condition that I haven't met, and it's the Java Runtime Environment version...
I checked the recommended note 867110 and it says that i need to have installed the J2SDK 1.4.2_08.
SLES10 includes the 1.4.2_13, so I had to uninstall it, and download the right version from Sun Microsystem's official webpage.
When I installed the version 1.4.2_08, i'm not able to run SAPINST because there's no Java Runtime Environment running on the server.
I started to investigate and I found in some forums [NOT EXPLICITLY] that there's no port for J2SDK 1.4.2_08 on x64 linux systems.
I can't believe this is true because SLES10 is recommended by SAP to install Solution Manager, so I hope somebody can help me on this.
My specific question is: Does anybody know if is true that J2SDK 1.4.2_08 is NOT COMPATIBLE with x64 Linux?
In case of being true, is there any way to be able to run SAPINST ? because if I enable the version SLES brings built in, i'm able to run the SAPINST but it detects that i'm not running version 1.4.2_08 and doesn't allow me to continue installation.
I hope somebody can help me soon...
Regards!

> SAPINST_JRE_HOME=/opt/IBMJava2-s390-142/jre/bin:$PATH
>
> JAVA_HOME=/opt/IBMJava2-s390-142/jre/bin:$PATH
You downloaded the wrong version - the one you have is for Z-Linux(Linux running on the mainframe - not for x64).
You need to download the x86_64 (or AMD64) version.
Install the correct one and try on a new console:
export JAVA_HOME=/opt/IBMJava2-amd64-142
export PATH=$JAVA_HOME/bin:$PATH
Then execute
java -fullversion
and it should show the correct version.
Markus

Can I install Solution Manager 7.0 in Window Server 2008 R2 Enterprise ed.?

Hi, SDN experts.
I am trying to install Solution Manager 7.0 in in Window Server 2008 R2?
I checked the the software requirement for SAP Solution Manager 7.0, it only mentioned Window Server 2003 and 2008 enterprise edition.
I am trying to install Solution Manager 7.0 in in Window Server 2008 R2 enterprise edition?
When I ran the Solution Manager Master Installer, the Pre-requisite Checker gave a warning message saying that it detected incompatible server version, that the server version is Windows NT 6.1 (Build 7601: Service Pack 1) (I guess it meant Window Server 2008 R2).
=======
The following Windows operating system version is supported: Windows Server 2003 (i.e. Version 5.2) and Windows Server 2008 (i.e. Version 6.0).
Current Windows version: Version 6.1, Service Pack 1.0, productive type: Server.
You can check the current version of you operating system by runningu2026u2026..
========
Can I actually install Solution Manager 7.0 in Window Server 2008 R2? Will this cause problem during the installation/post-installation if I ignore this message?
Thanks,
KC

Hi,
I think it is not straight forward to install SAP Solution Manager 7.0 in MS Window Server 2008 R2.
I am installing Solution Manager 7.0 , the installation encountered error on Create Java Users step (Phase 31 of 44). When I login to SAP solution Manager system through SAP GUI. I encountered this error:
"OS release Windows NT 6.1 7601 Service Pack 1 4x AMD64 Level 6 (Mod 44 Step 2) is not supported with this kernel (700)'
I found that it is because I am installing SAP Solution Manger 7.0 in MS Window Server 2008 R2, which the existing kernel version does not support.
Do you know which kernel I should install?
I browsed in:
SAP Application Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0" Entry by Component" Solution Manager ABAP Stack
SAP KERNEL 7.00 64-BIT UNICODE --> Windows Server on x64 64bit -->MS SQL SERVER
I downloaded:
SAPEXEDB_291-20001361.SAR Kernel Part II (for Basis 7.00) 291
Is this the right Kernel patch I should use?
If it is the right kernel patch file, how do I apply the latest kernel to existing Solution Manager system? Can you give me some guidance on this?
Thanks,
KC

Solution manager system log - strange entries

Hi Everyone,
the problem we are facing in Solution Manager system log every five minutes appears a new error message:
2 Database error -30082 at CON
0 > SQL30082N Security processing failed with reason "24"
0 > ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
First of all the landscape: ECC, BI, CRM, PI and Solman. Each system is DEV, QUA, PRD - except Solution Manager.
Result of going to see the logs within work directory:
Connect to %_DCR_XXXXX as db2dcr with DB6_DB_NAME=DCR;DB6_DB_HOST=xxxxxx;DB6_DB_SCHEMA=SAPSR3;DB6_DB_SVCENAME=5912
C *** ERROR in DB6Connect[dbdb6.c, 1727] CON = 1 (BEGIN)
C &+***      DbSlConnectDB6( SQLDriverConnect ): [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USE
C &+***      RNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
C &+***
C &+***
C &+***      ABAP location info 'CL_SQL_CONNECTION=============CP', 337
C &+***
C *** ERROR in DB6Connect[dbdb6.c, 1727] (END)
C *** ERROR => DbSlConnect to 'DCR' as 'db2dcr' failed
[dbdb6.c      1732]
Some of the systems are being connected successfully and the error messages in SM21 are not related to those systems. But some of the systems like DCR cannot be reached. And this fact causing the error messages.
I haven't configured Solution Manager because I have joined the project later. I would like to know what job is trying to access the satellite system and for what purpose.
On solution manager side I have checked all the scheduled background jobs - all of them have been executed successfully.
There some of them are scheduled but it is hard understand what is purpose of the job.
I have checked and corrected system landscape through SMSY and have maintained all the RFCs. They all OK now.
What else could force to make a connection to satellite system? And where is the place where it is hardcoded local(satellite) db2 connection entry?
Like I said before, some of the systems are being connected but some not. The one which has not been connected - there was recently changed SAP master password. I believe this is the key to resolve the problem. But the system itself operating 100% correctly.
Perhaps it could be CCMS that makes some extra connections to collect the data from the monitored systems. But I have checked all the RFC's in SM59 and they were OK.
Any ideas or suggestions would be appreciated.
Thanks in advance,
Kind regards,
Artjom.

Kaustubh Krishna,
thank you for respond.
It was dbacockpit. The connection was maintained with old db2sid password. And it was causing problematic log entries.
Problem was solved.
Points awarded.
Thanks,
kind regards,
Artyom

Configure TMS in fresh installed Solution Manager system

Similar Messages

Maybe you are looking for