Solution Manager 4.0 SR1 installation error

Hi there,
I am getting eblow error for Solution Manager 4.0 SR1 installation on aix-ora.
Any help much appreciated. Thanks.
Regards
Anil
INFO       2008-05-19 14:15:56 [syuxccuren.cpp:119]
           CSyCurrentProcessEnvironmentImpl::removeEnvironmentVariable
Removed environment variable SAPDATA_HOME from current process environment.
INFO       2008-05-19 14:15:58 [iaxxgenimp.cpp:630]
           showDialog()
Execute step PrepareOraCreateTablespace of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0.
ERROR      2008-05-19 14:15:59 [iaxxejsbas.cpp:178]
           EJS_ErrorReporter
FJS-00003  TypeError: sapdataNodeInfo[idx] has no properties (in script NW_Onehost|ind|ind|ind|ind, line 51567: ???)
ERROR      2008-05-19 14:15:59 [iaxxgenimp.cpp:728]
           showDialog()
FCO-00011  The step PrepareOraCreateTablespace 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_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|PrepareOraCreateTablespace was executed with status ERROR .

Why not use SR3 release? It contains MANY more fixes and will prevent you from the need of installing a bunch of support packages after your installation...
For your error: please check ora_sql_result.log
Markus

Similar Messages

  • Solution Manager 4.0 SR1 on iseries - Error on step CallOfflineCTC

    I'm installing a Solution Manager 4.0 SR1 on iseries using SAPinst/TMKSRV from Windows XP client.
    In the step Configure UME the installation stopped. As describe in SAP note 927734 I changed the control.xml in the SAPinst directory with the control.xml attached in this note.
    So, the installation continue with success.
    Then, in the phase 40 of 40 (the LAST!!!!), "Prepare to install minimal configuration", the installation stopped with the following error messages:
    <b>sapinst.log</b>
    Execution of the command "\usr\sap\S22\DVEBMGS08\j2ee\ctc\LaunchOfflinectc.sh" finished with return code 127. Output:
    /usr/sap/S22/DVEBMGS08/j2ee/ctc/LaunchOfflinectc.sh: 001-0014 Comando Z:/QIBM/ProdData/Java400/jdk14/bin/java non trovato.
    ERROR 2007-05-11 17:35:21
    CJS-00030  Assertion failed: in
    function NW_Call_Offline_CTC_ind_ind_ind_ind_SubComponentContainer_callOfflineCTC() {
        var nw = NWInstall.getSystem(context.get("sid"));
        var ctcDirFs = nw.getCI().getInstanceDir().concat("j2ee", "ctc");
        var ctcExeFile = installer.onWindows() ? "LaunchOfflinectc.bat" : "LaunchOfflinectc.sh";
        var ctcCall = ctcDirFs.concat(ctcExeFile);
        installer.writeTrace("CTC is in" + ctcCall);
        ASSERT(arguments.callee, ctcCall.isExisting(), "CTC executable cannot be found in " + ctcCall.toString());
        if (installer.onOS400()) {
            var ctcCallFile = ctcCall.getNode();
            ctcCallFile.saveVersion();
            var ctcCallStream = ctcCallFile.getFileStream("READ");
            var ctcCallStreamNew = new StringStream();
            ctcCallStreamNew.copy(ctcCallStream);
            ctcCallStream.close();
            ctcCallStream = ctcCallFile.getFileStream("TRUNCATE");
            for (var it = ctcCallStreamNew.getIterator(); !it.isDone(); it.next()) {
                ctcCallStream.putLine(it.get().replace(/\/bin\/csh/g, "/bin/sh"));
            ctcCallStream.close();
            ctcCallStreamNew.close();
        var pmgt = new ProcessMgt();
        var app = pmgt.createChildApplication(ctcCall, []);
        var userData = nw.getUsers().getAccountData(NWUsers.roles.SIDAdm);
        var user = (new AccountMgt()).getUser(userData.name);
        var env = pmgt.getProcessEnvironment();
        if (installer.onUnix()) {
            env.setUser(user);
        env.setWorkingDirectory(ctcDirFs.getNode());
        env.setEnvironmentVariable(new Property("JAVA_HOME", nw.getJavaHome().toString()));
        installer.writeTrace("For the Offline CTC Call, JAVA_HOME is set to " + env.getEnvironmentVariable("JAVA_HOME"));
        app.setEnvironment(env);
        var retval = app.run([], true);
        ASSERT(arguments.callee, retval == 0, "CTC retval is not 0 but " + retval);
        installer.writeTrace("CTC has been called in Offline Mode.");
    CTC retval is not 0 but 127
    ERROR 2007-05-11 17:35:21
    MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
    ERROR 2007-05-11 17:35:21
    FCO-00011  The step callOfflineCTC 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|callOfflineCTC was executed with status ERROR .
    <b>LaunchOfflinectc.sh.log</b>
    /usr/sap/S22/DVEBMGS08/j2ee/ctc/LaunchOfflinectc.sh: 001-0014 Command Z:/QIBM/ProdData/Java400/jdk14/bin/java not found.
    "Z:" is the drive letter in the client Microsoft XP that mapped the root on the iseries.
    The JAVA_HOME enviroment in the client Microsoft XP where I run the SAPINST is "C:\Programmi\Java\j2re1.4.2_03"
    Can you please help me to solve the problem??
    Thanks in advanced.
    Moreno

    The following Note is verey usfull to solve this issue.
    Note:1094628
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1094628&nlang=EN&smpsrv=https%3a%2f%2fwebsmp210%2esap-ag%2ede
    Best Regard

  • Solution Manager 4.0 SR1 install stops at phase 34

    Hi
    Installing a Solution Manager 4.0 SR1 ABAP+Java central system and have used the new patch 75 kernel 700 DVD from SR2 shipment. O/S version is V5R4.
    The server also has another SM 4.0 installed system that is defined as the SLD (system landscape directory), and an ECC 6.0 SR2 DEV system (both also ABAP+Java central systems).  JDBC driver is the Toolbox driver.
    It stops at phase 34, and a retry does not succeed; also tried cancel, then shutdown of TMKSVR00 subsystem, deleted TMKSVR00 library, reload TMKSVR, restart sapinst.exe and continue install. This also fails at the same step.
    Here is the error.  Waiting the SAP response still - they think it is to do with the following :
    " The Scheduler consists of two parts: one is the Ejb and the other is a
    Library.
    The Ejb is the component 'tc/webadministrator/scheduler/ejb' on which
    your deployment fails and the Library is in the component
    'tc/webadministrator/solmandiag' where the Scheduler class is stored.
    The error you currently get would mean that the installer tries to
    deploy the Ejb before the Library breaking the deployment dependency"
    The log file has:
    ERROR
    CJS-30156 SDM deployment failed for at least one of the components to
    deploy.<br> SOLUTION:
    Check 'X:\usr\sap/SAPinst/SOLMAN/SYSTEM/DB4/CENTRAL/AS/callSdmViaSapinst.log' for more information.
    ERROR
    FCO-00011 The step enableUsageTypes with step key
    |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|enableUsageTypes was executed with status ERROR
    The log file has:
    Jan 30, 2007 11:19:52... Info: End of log messages of the target system.
    Jan 30, 2007 11:19:52... Info: ***** End of SAP J2EE Engine Deployment
    (J2EE Application) *****
    Jan 30, 2007 11:19:52... Error: Aborted: development
    component 'tc/webadministrator/scheduler/ejb'/'sap.com'/'SAP
    AG'/'7.0008.20060624010338.0000', grouped by software component 'LM-
    SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.8.0.20060702013900':
    Caught exception during application deployment from SAP J2EE Engine's
    deploy service:
    java.rmi.RemoteException: Cannot deploy application
    sap.com/tcwebadministratorscheduler~ejb..
    Reason: Exception during generation of components of application
    sap.com/tcwebadministratorscheduler~ejb in container EJBContainer.;
    nested exception is:
    com.sap.engine.services.deploy.exceptions.ServerDeploymentException:
    Exception during generation of components of application
    sap.com/tcwebadministratorscheduler~ejb in container EJBContainer.
    regards
    Michael.

    - Had to restart SMP system as the sapinst script would not do this on restart, then wait till the SERVER0 was Running - i.e. could login to http://<server>:50300 for instance 03 (Java/ABAP).  Then it went through phase 34 and completed successfully.

  • Issue on Solution Manager 4.0 SR3 installation

    Dear all,
    During the Oracle Client installation phase of a SAP Solution Manager 4.0
    system installation with sapinst, I get the following error
    ERROR 2008-01-21 16:04:06.776 iaxxejsbas.cpp:178
    EJS_ErrorReporter
    FJS-00003 TypeError: linkTarget has no properties (in script
    NW_Onehost|ind|ind|ind|ind, line 3431: ???)
    ERROR 2008-01-21 16:04:07.399 iaxxgenimp.cpp:731
    showDialog()
    FCO-00011 The step createOcl10Links with step key
    |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_C
    reateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|in
    d|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraClient|ind|ind|ind|ind|3|0|createOcl10Links was executed with status ERROR .
    TRACE 2008-01-21 16:04:07.443 iaxxgenimp.cpp:719
    showDialog()
    Any ideas?
    Many thanks
    Andreas

    On Solaris 10 platform...
    We found that we could correct the problem by extracting the SAR file OCL10264.SAR from the client DVD into the client directory /oracle/client/10x_64 (which we had to create) and execute "ln -s instantclient_10202 instantclient" to create the symbolic link for the instantclient directory. Then the installation continued successfully. 
    Credit to Rama Ekambaram for figuring this out...
    Tim Pittman

  • Error at "CAF" phase of Solution Manager 4.0 SR3 installation

    Hello,
    When we install Solution Manager SR3 at phase 57 of 59, we get an error when sapinst configures "use type as java" CAF configuration parameters.
    Line: -
    ERROR
    CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile java.log: 'JSE '.
    Line: -
    1. sapinst.log :
    ConfigMainExt state500
    TYPE=A
    STATE=500
    INFO_SHORT=Error connecting to  --http://yanbalsm:50000/ctc/ -- ConfigServlet?param=com.sap.ctc.util.OfflineConfig;PROPSHEETVALUE;CONFIGURATION=
    apps/sap.com/caf~runtime~ear/appcfg/application.global.properties,KEY=WAS_MACHIN
    E_ADDRESS,VALUE=yanbalsm. The provided user data might be incorrect or user migh
    t be locked.
    CONFIGURATION=
    ERROR 2008-02-23 18:30:52.811
    CJS-30059 Java EE Engine configuration error. DIAGNOSIS: See output of logfile
    java.log: 'JSE '.
    ERROR 2008-02-23 18:30:52.812
    FCO-00011 The step configCAFPropSheet with step key |NW_Onehost|ind|ind|ind|ind
    |0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Conf
    iguration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_CAF|ind|ind|ind|ind|1|0|configCAFProp
    Sheet was executed with status ERROR .
    Line: -
    the usser JSE means for J2ee_admin or other? . i looged into abap stack 001 with sap* and validate that that user is not blocked.
    Line: -
    2. java.log
    TYPE=A
    STATE=500
    INFO_SHORT=Error connecting to --http://yanbalsm:50000/ctc/
    -- ConfigServlet?param=com.sap.ctc.util.OfflineConfig;PROPSHEETVALUE;CONFIGURATION=
    apps/sap.com/cafruntimeear/appcfg/application.global.properties,KEY=WAS_MACHIN
    E_ADDRESS,VALUE=yanbalsm. The provided user data might be incorrect or user migh
    t be locked.
    CONFIGURATION=
    Line: -
    I look into http:// hostanme:port/nwa and users are ok and come from abap stack.
    but when try to uses config tool or VA with de sidadm user none load , i got a error message "JAVA_HOME" not set.
    i look into .j2eeenv file and is set with setenv.
    Line: -
    3. sapinst_dev.log .-
    TRACE      2008-02-24 00:02:56.72 [iaxxejsexp.cpp:199]
               EJS_Installer::writeTraceToLogBook()
    NWException thrown: nw.configError:
    Java EE Engine configuration error. DIAGNOSIS: See output of logfile java.log: '
    JSE '.
    ERROR      2008-02-24 00:02:56.72
               CJSlibModule::writeError_impl()
    CJS-30059  Java EE Engine configuration error. DIAGNOSIS: See output of logfile
    java.log: 'JSE '.
    Line: -
    could any one please tell me what can i check to solve this and finish my installation process.
    Thank,
    Daniel

    Hi
    We have the same problem but in AIX/Oracle
    Any suggestions?

  • Solution Manager 3.2 SR1 Install Problem

    Hello everybody,
    I'm having a hard time trying to install SAP SolMan 3.2 SR1 on Windows Server 2003 x86_64 with Oracle 10.2.
    I have installed the OS and Oracle 10.2.
    When I start the installation of CI of SolMan after couple of screens it gives me the error:
    CJS-00030  Assertion failed: No db client software version available in tORA_ClientVersion for client type AMD64
    I have searched for days google and other forums and couldn't find an answer.
    Any help would be very much appreciated.
    Thanks in advance.

    Hi Stanislav,
    The current Oracle 10.2.0.2 is at level patch-14 ( http://service.sap.com/swcenter-3pmain). So, that patch (10202_Patch14_MSWINX86-64.zip ) should be fine,
    Also there you will have Oracle Install client  OCL10264.SAR.
    But, I'm now thinking of the point Markus mentioned earlier about compatibity in 6.40 kernel and Oracle 10g. You might have a look at note 949116.
    In that case it might be you will have to go for SolMan 4.0 (based on WAS 7.00). If you are only using ABAP stack (no Solution Manager Diagnostics), they must be almost same.
    Cheers !!
    Satya.

  • Solution mangaer 4.0 SR3 Installation error at configure UME

    Dear All,
    I am trying to do installation of SOlution manager 4.0 SR3 on windows 2003 server, MS SQL Server 2005 as database.
    My Java version 1.4.2_16"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
    Java HotSpot(TM) Client VM (build 1.4.2_16-b05, mixed mode)
    My installation stuck at configure UME stage below is error message.
    Jun 20, 2008 6:21:06 PM  Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "setup"
    Jun 20, 2008 6:21:07 PM  Info: Using SID "SMN" for secure storage
    Jun 20, 2008 6:21:07 PM  Info: Created group entry in secure storage: Group "SAP_J2EE_ADMIN", roles "Administrator"
    Jun 20, 2008 6:21:08 PM  Info: Created group entry in secure storage: Group "SAP_J2EE_GUEST", roles ""
    Jun 20, 2008 6:21:08 PM  Info: Created user entry in secure storage: User "J2EE_ADMIN", password set, parent groups "SAP_J2EE_ADMIN", locked "false", roles ""
    Jun 20, 2008 6:21:08 PM  Error: main()
    [EXCEPTION]
    com.sap.security.core.server.secstorefs.FileIOException: I/O error on file "
    testpip/sapmnt/SMN/SYS/global/security/data/SecStore.properties".
         at com.sap.security.core.server.secstorefs.StorageHandler.flush(StorageHandler.java:769)
         at com.sap.security.core.server.secstorefs.SecStoreFS.insertPair(SecStoreFS.java:2258)
         at com.sap.security.tools.UMConfigModel.addUserInSecStore(UMConfigModel.java:725)
         at com.sap.security.tools.UMConfiguratorLoad.doSetup(UMConfiguratorLoad.java:575)
         at com.sap.security.tools.UMConfiguratorLoad.main(UMConfiguratorLoad.java:212)
         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:324)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: java.io.FileNotFoundException:
    testpip\sapmnt\SMN\SYS\global\security\data\SecStore.properties (The requested operation cannot be performed on a file with a user-mapped section open)
         at java.io.FileOutputStream.open(Native Method)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
         at com.sap.security.core.server.secstorefs.StorageHandler.flush(StorageHandler.java:765)
         ... 9 more
    Jun 20, 2008 6:21:08 PM  Info: Leaving with return code 99

    Ok. I double checked - you´re right. The new CD/DVD set with Solman 7.0 doesn´t support 32bit any more. I HIGHLY suggest to install SolMan on 64bit, you may not be able to use all functionality.
    Now back to your problem:
    Can you open the file? Is it there? There seems to be a permission problem...
    Markus

  • Solution Manager 4.0 Linux installation remains in step 20

    Hi,
    I have two questions:
    1.- We want to install NW04s with EP and WAS JAVA scenario, but first we have to install Solution Manager 4.0 with AS JAVA + AS ABAP instances, cause this is a necessary step for obtain the solution mananager key and for install NW04s. That's true?
    2.- In Solution Manager 4.0 installation for Linux, the installation program remains in "step 20 - Import ABAP" for a long time (I leave it running for more than a 12 hours...), and show no errors, but still running and no goes to the next step. Any idea?
    Information:
    Server: Linux_x86_64.
    Operating system: Suse Linux Enterprise Edition 9.2
    kernel: 2.6.5.7-7.267-smp
    java version: J2RE 1.4.2 IBM J9 2.2 Linux amd64-64
    I had a lot of problems to find jdk 1.4.xx for Linux on 64 bits that works with sapinst. For this reason, I had to install this IBM jdk.
    Message was edited by: Soporte OSS Soporte OSS

    Hi,
    I'm me again. xD
    Now I pass the step 20 but in the "Object_checker.log" shows that some objects can not be imported.
    Now it stops in step 23 with this error on logs: "JDBCDriverException: Can not connect to DB"
    Anyone knows what should I do?
    TIA,
    Arnau
    Message was edited by: Soporte OSS Soporte OSS

  • Solution Manager 7.1 Post-installation upgrade SPS04

    Hi
    I just installed Solution Manager 7.1, on Windows server 2008 R2 / 64 bits with Oracle database.
    In post installation steps I have to update my installation.
    According to note 1577909, I have downloaded the Stack DVD : " SAP Solution Manager 7.1 SPS04" from SAP marketplace and copied the java files in usr\sap\trans\EPS\in and unpacked the ABAP files in the same directory.
    Then I have downloaded the Stack Kernel files & copied in usr\sap\trans\EPS\in.
    Now I'm a little bit confused : I'm supposed to call transaction SAINT and use maintenance xml in the EPS inbox & JSPM and use maintenance XML in the EPS inbox => witch XML files should I use : the one in the support package stack or the one generated in the service marketplace in "link to SP Stack application" ?
    Is that all to update my solution manager? what about maintenance optimizer? ( in which I have errors ).
    Would the SPS 04 be installed? as well as the stack files?
    Is there a guide or a more detailed implementation procedure for this purpose?
    Should I make a backup before upgrading?
    Thanks for your input.
    Guillaume Blanchard

    Thanks a lot for your inputs.
    1 ) In SP Stack Application, my start SP Stack is "SAP SOLUTION MANAGER 7.1 - ISS Initial Shipment Stack"
    and my target one is SAP SOLUTION MANAGER 7.1 - SPS 04 (12/2011 )
    I'm in 64 bit so i have selected  SAP KERNET 7.20 32-BIT and Alternativest => SAP KERNEL 7.20 EXT 64-BIT  but in the next step i have to pick the software component versions : in note 1577909 it's say to only select kernel file, but
    I'm gettting warning on the next screen : 9 messages :
    - Step 2 : WILY Introscope workstation 8 and Alternative SCV : We recommend selecting at least one alternative
    - Step 2 : SAP KERNEL 7.20 32-BIT UNITOCDE and Alternative SCV : We recommend selecting at least one alternative
    - Step 2 : SAP IGS 7.20 and Alternative SCV : We recommend selecting at least one alternative
    - Step 2 : SAP IGS 7.20 and Alternative SCV : We recommend selecting at least one alternative
    - Step 2 : SAP HOST AGENT 7.20 : We recomment selecting at least one alternative
    - Step 2 : BMC APPSIGHT BLACKBOX 6.0.2 : We recomment selecting at least one instantiation
    - Step 2 : SAP GUI FOR WINDOWS 7.20 CORE  : We recomment selecting at least one instantiation
    - Step 2 : NWBC NW BUSINESS CLIENT 3.0 : We recomment selecting at least one instantiation
    - Step 2 : SAP BUSINESS BLUEPRT TOOL 101  : We recomment selecting at least one instantiation
    Is it right to keep up without considering those warnings?
    About the ABAP file from the SPS04 dvd there is many files without label : am i supposed to extract all of the SAR files ?
    Should i do the same for the sar files downloaded from SP Stack application ?
    Should i download the last SPAM/SAINT update from sap marketplace ( 730 ) ? how to install it ?
    Is there a guide about this procedure ?
    Still Really thanks for the inputs

  • Solution Manager on Linux x86_64 installation problem

    I try to install Solution Manager 4.0 on Linux X86_64 platform. Unfortunately i receive error "the JDK installed in directory /usr/lib/java does not support the 64 bit data model". And there is no J2SDK for Suse linux x86_64 (or at least i can't find it. Please help!!!

    OK. I solved the problem by using IBM Java. Also there is an SUSE version of SUN Java 1.4.2 for 64 bit systems.

  • Solution Manager can't generate  installation key  for Netweaver 2004s

    I am trying to generate installation key for a new installation of
    Netweaver 2004s or 7.0 and the Solution Manager only display SAP ECC
    5.0 or 6.0 in the field production version, when i am trying do create
    a new system landscape. My Solution Manager is 4.0 release and support
    package 10. The keys generated by ECC 5.0 or 6.0 doesn't work.

    That is because SAP has not released an ECC 7.0
    NW2004s is also refered to as 7.0.  It appears that you are confusing this with ECC 5.0 and ECC 6.0
    A NW2004s installation can contain an ECC5.0 or ECC 6.0, just like it can contain a CRM 5.0 or SRM, or EP, et cetera
    The generated keys probably do not work because you have wrong hostname or instance number entered.

  • Preparing Solution Manager for SMD Agents Installation

    Hello everyone
    I have to configure the Solution Manager of QAS to receive new SMD Agents, I looking at the transaction SOLMAN_SETUP.
    Does anybdoy know what do I have to do to prepare the environment for the installation of SMD agents?
    Thank

    Hi Marcelo,
    Check note 1365123 - Installation of Diagnostics Agents, this note shows the agent installation strategy. You must install one SMD agent per host (physical or virtual) . The SMD agent should be installed in all host you want to monitor.
    In order to connect the SMD agent into your Solution check the following WIKI:
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents#DiagnosticsAgents-Connectionoptions
    Also, you can managed the SMD agent in the "Agent Administration", it can be found at:
    - SOLMAN_WORKCENTER
    - Tab Root Cause Analysis
    - "Agent Administration"
    I recommend you to use the "Direct connection to solution manager" for your agents. It is easier than the SLD registration.
    Regards,
    Allam

  • Recieved error during Solution Manager EHP1 Java Components installation.

    I successfully installed EHP1 ABAP components but I'm have a problem with the Java components. I recieved the following error. Import aborted during ADSSAP02_0-20002778.SCA
    Feb 20, 2009 3:17:59 PM  Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
    Reason: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.; nested exception is:
            com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Feb 20, 2009 3:17:59 PM  Info: Starting to save the repository
    Feb 20, 2009 3:18:01 PM  Info: Finished saving the repository
    Feb 20, 2009 3:18:01 PM  Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
    Feb 20, 2009 3:18:01 PM  Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
    Failed deployment of SDAs:
    development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
    Please, look at error logs above for more information!
    Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.200712
    13024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
    Reason: Cannot load one of the bean interfaces or the bean class of bean LicenseEJBBean.; nested exception is:
            com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: Cannot load one of the bean interfaces or the bean cla
    ss of bean LicenseEJBBean.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Feb 20, 2009 11:25:59... Info: Starting to save the repository
    Feb 20, 2009 11:26:01... Info: Finished saving the repository
    Feb 20, 2009 11:26:01... Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634'
    '/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
    Feb 20, 2009 11:26:01... Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
    Failed deployment of SDAs:
    development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
    Edited by: Darrell Kirklen on Feb 23, 2009 5:03 PM

    Just resolved problem. While reviewing the sdmlog20090310.log I found
    error "java.lang.UnsupportedClassVersionError?" when I goggled this
    error "How do I resolve a java.lang.UnsupportedClassVersionError? I
    found the following solution:
    http://support.codegear.com/article/35846 : This exception can occur
    when the source is built targeting a JDK that is not supported by the
    JDK attempting to run it. In the above example, if the servlet was
    built targeting only JDK 1.5, but the web server runs JDK 1.4, the
    above exception will occur. Check, Project Properties | Build | Java |
    Target VM, and verify that the Target VM indicates a JDK compatibility
    that is appropriate for the JDK that is running it. It is recommended
    to set this field to 'All Java SDKs' for the most compatibility. The
    only reason you would want to specify a particular version is if your
    code uses language features that only appear in a particular version of
    the JDK, and you want to ensure that users use only a compatible JDK.
    Also check, Project Properties | Build | Java | Language Features, and
    verify that the Language Features are applicable with JDK that is
    running it
    A this point I checked the java -version at the os level and it showed
    1.5.0_17 we are aware the supported version of java should be 1.4.2_16
    our Unix team (Solaris) recently installed new patches and didnu2019t
    remember to leave the java version at 1.4.2_16 after their were done.
    Once the java version was set back to 1.4.2_16 I was able to complete
    the java portion of EHP1 using the JSPM successfully.
    Edited by: Darrell Kirklen on Mar 13, 2009 4:37 PM

  • NW 7.01 SR1 installation error

    hi all,
    we installing NW 7.01 EHP1 SR1 on solaris 10 woth oracle 10g , but we start installtion irt generate errors
    root@newdev # ./SAPINST
    [==============================] / extracting...  done!
    iauxsysex.c:271: exec(/tmp/sapinst_exe.2316.1272350145/SAPINST) error: No such f ile or directory
    iauxsysex.c:318: child /tmp/sapinst_exe.2316.1272350145/SAPINST (pid 2317) has c rashed. Executable directory is /tmp/sapinst_exe.2316.1272350145. Contact Suppor t.
    iaextract.c:895: child has signaled an exec error. Keeping directory /tmp/sapins t_exe.2316.1272350145
    while we have set all variable
    like
    root@newdev # JAVA_HOME=/opt/java1.4.2.24
    root@newdev # export JAVA_HOME
    root@newdev # SAPINST_JRE_HOME=/opt/java1.4.2.24/jre
    root@newdev # export SAPINST_JRE_HOME
    plz guide
    Imran

    hi master,
    we have rename it as "sapinst"
    now it open gui and generate error
    Caught a known exception during service selection. Errortext: ESAPinstException: error text undefined  Message stack: Opened sylib701_1.so exe dir is /tmp/sapinst_exe.3164.1272434610 unknown message ID (syslib.process.currentProcessEnv.cwdSuccessful) with parameter(s): /tmp/sapinst_exe.3164.1272434610 Opened /tmp/sapinst_exe.3164.1272434610/iaguieng701_1.so unknown message ID (syslib.process.currentProcessEnv.cwdSuccessful) with parameter(s): /dumps/51036888_15/InstMst_7.01_SR1__NW_ERP_CRM_SRM_SCM/IM_SOLARIS_X86_64 getspnam() returned NULL. checking existence of account user="root" uid="0" succeeded with true. inserted account (root, 0, USER) into the accountcache. receiving and sending on port 21200 Environment variable SAPINST_JRE_HOME set to value '/tmp/sapinst_exe.3164.1272434610/jre'. doStartGuiServer() is now running... java is: /tmp/sapinst_exe.3164.1272434610/jre/bin/java A child process has been started. Pid = 3169 unknown message ID (syslib.account.isExistingOnOsSucceededTrue) with parameter(s): sapinst checking existence of account group="sapinst" gid="103" succeeded with true. inserted account (sapinst, 103, GROUP) into the accountcache. unknown message ID (syslib.process.currentProcessEnv.groupSetSuccessfully) with parameter(s): 103 account user="root" uid="0" exists with parameter gid="0" checking existence of account group="root" gid="0" succeeded with true. inserted account (root, 0, GROUP) into the accountcache. account user="root" uid="0" exists with parameter gid="0" checking existence of account group="adm" gid="4" succeeded with true. inserted account (adm, 4, GROUP) into the accountcache. checking existence of account group="bin" gid="2" succeeded with true. inserted account (bin, 2, GROUP) into the accountcache. checking existence of account group="daemon" gid="12" succeeded with true. inserted account (daemon, 12, GROUP) into the accountcache. checking existence of account group="lp" gid="8" succeeded with true. inserted account (lp, 8, GROUP) into the accountcache. checking existence of account group="mail" gid="6" succeeded with true. inserted account (mail, 6, GROUP) into the accountcache. checking existence of account group="nuucp" gid="9" succeeded with true. inserted account (nuucp, 9, GROUP) into the accountcache. checking existence of account group="other" gid="1" succeeded with true. inserted account (other, 1, GROUP) into the accountcache. checking existence of account group="sys" gid="3" succeeded with true. inserted account (sys, 3, GROUP) into the accountcache. checking existence of account group="tty" gid="7" succeeded with true. inserted account (tty, 7, GROUP) into the accountcache. checking existence of account group="uucp" gid="5" succeeded with true. inserted account (uucp, 5, GROUP) into the accountcache. account user="root" uid="0" exists with parameter groups="other,bin,sys,adm,uucp,mail,tty,lp,nuucp,daemon,sapinst,root" User is already member of group sapinst. Nothing to do. exe dir is /tmp/sapinst_exe.3164.1272434610 unknown message ID (syslib.filesystem.creatingFile) with parameter(s): /tmp/sapinst_instdir/x unknown message ID (syslib.filesystem.removingFile) with parameter(s): /tmp/sapinst_instdir/x retrieving account information for group sapinst... unknown message ID (syslib.account.isExistingOnOsSucceededTrue) with parameter(s): sapinst getting ACL of /tmp/sapinst_instdir succeeded. inserted account (Everyone, -17, GROUP) into the accountcache. Editing rights (rwx): (103, GROUP, =rwx) Setting rights of sapinst to rwx Editing rights (rwx): (0, USER, =rwx) Setting rights of root to rwx Editing rights (rwx): (-17, GROUP, =rwx) Setting rights of Everyone to rwx unknown message ID (syslib.filesystem.aclSetSucceeded) with parameter(s): /tmp/sapinst_instdir retrieving account information done. unknown message ID (syslib.process.currentProcessEnv.cwdSuccessful) with parameter(s): /tmp/sapinst_exe.3164.1272434610 Opened /tmp/sapinst_exe.3164.1272434610/iakdblib701_1.so unknown message ID (syslib.process.currentProcessEnv.cwdSuccessful) with parameter(s): /dumps/51036888_15/InstMst_7.01_SR1__NW_ERP_CRM_SRM_SCM/IM_SOLARIS_X86_64  This is SAPinst, version 701_1, make variant 701_REL, build 1015597 compiled on Oct 2 2008, 22:44:50  unknown message ID (controller.xmlParseErrors) with parameter(s): /dumps/51036888_15/InstMst_7.01_SR1__NW_ERP_CRM_SRM_SCM/IM_SOLARIS_X86_64/product.catalog line 3, 24: error unable to retrieve external entity 'catalog.dtd'   Please inform the installation development, execution will be terminated now.

  • Solution Manager 4.0 - MSCS Installation

    Hi All,
    We are planning for Solman 4.0 Installation in Cluster environment with Windows 2003 server and MS SQL Server 2005.
    I have some queries related to this task.
    1. Is it possible to install Central Instance in first MSCS node and Database Instance in Additional MSCS node, activate failover in both points. Like if CI system goes down first MSCS node should failover to addtional node and if DI goes down additioonal MSCS node should failover to first MSCS node. Since in cluster installation document of solman, this type of failovers is not mentioned.
    2. Enqueue Replication Server Installation: Our solman has both ABAP+Java stack. For this case how we can install ERS. In document it has mentioned we have install 4 times means
    ERS1(ABAP), ERS2(Java) - First MSCS Node
    ERS3(ABAP), ERS4(Java) - Additional MSCS Node
    3. Is it mandatory to install in Dialog Instance in the cluster installation. Since in installation document it is mentioned like atleast one dialog instance should be installed.
    Pls give me some inputs for this queries
    Thanks in Advance
    Regards
    KT

    Got Solution...Its not Mandatory to install ERS

Maybe you are looking for

  • I cannot delete ANY apps after upgrading to ios 5-

    After updated my software to ios 5 (iPhone 4, Verizon), I cannot delete any of the apps; it's like every single app is now a "native," acting just like all of the built in apps like phone, message, safari, etc. When I hold down on any one of them, th

  • Where can I get an old PPC Leopard install disc?

    I've got a Mac Mini G4 1.42ghz PPC 512mb ram. I need a leopard install disc but can't find one anywhere

  • RCA - Read Permission

    Hi, I'm trying to assign the necessary Root Cause Analysis roles for read access to a user. But without success: I assigned the following roles to the user: - SAP_RCA_DISP - SAP_RCA_EXE - SAP_SMWORK_BASIC - SAP_SMWORK_DIAG - SAP_BI_E2E But the user c

  • Re: Satellite Pro A200 - Screen goes black after BIOS screen

    Hi, I'm new to the forum and have quite a big problem. So any help is welcome and appreciated. My Satellite Pro A200 goes black after the BIOS screen and a black screen with a blinking cursor. Also just before the screen goes black a bleep can be hea

  • Random 401 errors - Kerberos + Reporting Server

    We have a portal with Reporting Server in SharePoint mode and deployed our reports to SharePoint. Reports run in integrated security mode, we configured Kerberos. (Reporting server configured as RSNegotiate, added SPN's, etc.) Everything seems to be