Installation Solution Manager: R3load testconnct:ERROR

Just about to install Solution Manager 7.0 on a Linux SUSE with MaxDB.
Step IMPORT ABAP gives an error (in R3load.exe.log)
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20100401095047
/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
/usr/sap/SOL/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 21:39:36
/usr/sap/SOL/SYS/exe/run/R3load -testconnect
(DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20
(DB) ERROR: DbSlErrorMsg rc = 20
/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20100401095047
No idea what DBSL_CMD_IMP_FUNS_SET rc=20 could mean???
Any idea?

Hello Henrik,
This sounds like you are trying to install the license and getting this issue.
Please review SAP Note 359944
Please run 'saplicense -show' again under user <sid>adm, and make sure the version of saplicense, it is Release 640 or Release 4.5B
check db-library version run command 'disp+work -v', then you will see the kernel version and dbsl patch level
update if necessary:
If releases of SAPLICENSE and dbsl are different, eg. SAPLICENSE is 640, but your kernel is 4.5B, please goto Service Marketplace and update the executables.
Thanks,
Mark

Similar Messages

  • Error in Phase during installation Solution Manager 7.1

    Dear all,
    when I want to install the Solution Manager 7.1 it comes an error during a installation phase.
    The log of the error (JAVA) is:
    ConfigMainExt state200
    TYPE=A<BR>STATE=<BR>INFO_SHORT=com.sap.security.core.server.destinations.api.DestinationException: com.sap.security.core.server.destinations.api.DestinationException: [destination_0000] No such destination of type WebService exists.
         at com.sap.security.core.server.destinations.service.DestinationServiceImpl.getDestinationNames(DestinationServiceImpl.java:278)
         at com.sap.ctc.util.DestinationConfig.maintainDestination(DestinationConfig.java:122)
         at com.sap.ctc.util.DestinationConfig.maintainWebServiceDestination(DestinationConfig.java:93)
         at com.sap.ctc.util.DestinationConfig.performFunction(DestinationConfig.java:50)
         at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:74)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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)
    //   => Maintaining Destination Service: sap.com/tcwdpdfobject/com.sap.tc.webdynpro.adsproxy.AdsProxy/ConfigPort_Document
    ERROR: Destination Service not available! // No such destination of type WebService exists.
    <BR>CONFIGURATION=
    Can anyone tell me what it is?

    Hello,
    What phase of the installation does this error occur?
    Is it failing to start the Java Engine?
    The reason I ask is the JVM will fail until you have set the java parameters, and you can't do that until the j2ee/configtools directory is created and you can run configtools, and that doesn't happen untilt eh start of the JVM phase, and then it always fails because the MAXHEAP is set too low by default and other parameters need setting. Then when the Install is re-started it can start the JVM and continue.
    This is not mentioned in the install guide. However if you are failing in another step, you would need to mention what step.
    You need to name the log you are showing the error, because it may or may not be the right log to look at, or it may be an error, but is not the cause. So if my guess is not right, please specify the phase name it fails and the log you reference, because there may be other logs that have better information as to why it failed. One you should check is dev_server0, in work.
    Regards,
    Paul

  • Installation Solution Manager error in the step Import Abap

    We are installing Solution Manager but in the step import abap, appear
    the error:
    /usr/sap/SML/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
    Compiled Feb 24 2009 21:54:08
    /usr/sap/SML/SYS/exe/run/R3load -testconnect
    (DB) ERROR: DbSlControl(DBSL_CMD_IMP_FUNS_SET) rc = 20
    (DB) ERROR: DbSlErrorMsg rc = 20
    /usr/sap/SML/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/SML/SYS/exe/run/R3load: END OF LOG: 20091202234420</message>
    I appreciate your help for this problem
    Regards.
    Ricardo Rivas

    Hi,
    Check SAP note 898181.
    Thanks
    Sunny

  • Solution manager 4.0 error

    Hi
    I am installing solution manager 4.0 on windows 2003 with oracle 10g.
    I am getting the error stage "RUN ABAP REPORT".
    The error massage is
    ERROR 2006-12-01 08:07:26
    FRF-00007  Unable to open RFC connection.
    ERROR 2006-12-01 08:07:26
    MUT-03025  Caught ERfcExcept in Modulecall: Password logon no longer possible - too many failed attempts.
    ERROR 2006-12-01 08:07:26
    FCO-00011  The step runRSWBOINS 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_ABAP_Reports|ind|ind|ind|ind|1|0|runRSWBOINS was executed with status ERROR .
    INFO 2006-12-01 08:19:58
    An error occured and the user decide to stop.\n Current step "|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_ABAP_Reports|ind|ind|ind|ind|1|0|runRSWBOINS".
    I can log on to the system though SAPGUI every thinh fine.
    What is the solution for that.Pls help me.
    Roshantha

    Hi I am getting another error at the stage 33 "Create java users"
    ERROR 2006-12-01 11:37:13
    CJS-30196  User not authorized. Session terminated
    ERROR 2006-12-01 11:37:13
    FCO-00011  The step createJ2EEAdmin 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_Doublestack|ind|ind|ind|ind|2|0|createJ2EEAdmin was executed with status ERROR
    Pls give me the solution for that.
    I manage to resolve previous issue.
    Roshantha

  • IDES ERP 2004 installation / Solution manager

    I am about to install IDES ERP 2004 on a test desktop system and I would like to know if I also need to install solution manager, any suggestions?
    Thanks
    Frank

    Hi Frank,
    Welcome to SDN!
    You can find the guide for ERP 2004 installation at
    http://service.sap.com/instguides -> ERP 2004. Its
    the same as a DB instance isntallation. You just have to
    provide the IDES DVDs. No need to install the solution manager.
    Regards
    Srikishan

  • Installation Solution Manager on Oracle 10g / AIX 6.1 - Oracle Patches

    Hi guys,
    I have a question.
    I'm on a project to install ERP 6.0 and I will start installing Solution Manager 7.0 EHP1, through no fault, the project is long overdue and urgently need the Solution Manager for the team project starts.
    The SAP platform is AIX 6.1 / Oracle 10.2.0.4. When I'm installing the central instance of Solution Manager, where the process to install Oracle Database Software Installation, then Current Patch Set (10.2.0.4) and lastly Required Interim Patches, which would be the point 4.7.4 of the Installation Guide SAP Solution Manager 7.0 including SAP Enhancement Package 1 on AIX - Oracle, can jump this last step (Required Interim Patches) and install these patches later ????? O is mandatory to install the Interim Patches to continue installing of SM.
    Thanks a lot.
    Desiré

    Hello Desirée
    If you take a look at the note, Oracle/SAP have change the patches policy.
    Currently there is only ONE "patch" to be installed.
    It is called a SAP patch Bundle (or something like that)
    It contains the latest PSU, and all required SAP individual patches.
    It must be installed with Mopatch.
    it has been released the 10th of this month.
    This can facilitate the task of installing patches (only one to "take care off"

  • Sap solution manager optimizer configuration error

    Dear Receipient
    I have installed solution manager 4.0, patch is updated upto the level of optimizer configuration. I have configured sap router on the same solution manager machine.
    now i am in solution manager optimizer configuration in that i am doing it with an user of having sap_all rights
    in t code  sm59 -> sap-oss  connection test is good
    now through t code solution_manager i have created an new active solution of sandbox land scape and through t code smsy i have created an logical component of sap ecc and i have added the user basis which iam using for soman optimizer configuration thru t code aisuser
    but now if i go to t code solution_manager if i click on sandbox landscape -> change management -> support packs -> then click on maintenance optimizer it shows as no system
    and also in product version also no available its showing
    i dont know where i went wrong in my solman optimizer configuration
    pls help me
    regards
    senthil

    Hi,
    Please follow the SAP Tutor to setup maintenance optimizer:
    http://service.sap.com/solman-mopz
    -> "SAP Tutor on Maintenance Optimizer " under the section
       "Additional information on Maintenance Optimizer"
    Best regards,
    Warren

  • Installation Solution Manager

    HI All,
    We have installed Solution Manager 4.0 in the following configuration
    DB        SQL-2005 ,OS        Windows-2003 .I would like to know the procedure for installing Solution Manager 4.0 in the following configuration
    DB&#12288;&#12288;&#12288;ORACLE&#12288;9.2&#12288;64-BIT
    OS&#12288;&#12288;&#12288;HPUX&#12288;&#12288;11.23/IA64 64BIT
    Regards,
    L Srikanthan.

    Hello ,
    Please download the relevent document from the below url :
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000075728&
    Regards,
    Santosh

  • ERROR ON SOLUTION MANAGER

    Hi !!!
    I have Some problems with the load and instalation of the Solution Manager. When I try to start the solution manager shows an error message:
    Loading of 'SAPSSEXC' import package: ERROR
    Import Monitor jobs: running 2, waiting 14, completed 1, failed 1, total 18.
    Import Monitor jobs: running 3, waiting 13, completed 1, failed 1, total 18.
    Loading of 'SAPAPPL1' import package: ERROR
    Someone can help me?
    Thanks & Regards

    Hi Luis,
    1.First check whether TNSListener is running. If is running Login as <SID>adm and check whether database is up and running.
    How to check?
    goto run and type sqlplus "/as sysdba"
    If you get Ideal Instance as a result use STARTUP command to start database.
    If database is already up and running follw the step2.
    2. Goto init<SID>.ora file at OS level. (
    oracle\ora92\database\init<SID>.ora)
    take a back up of file and change the following parameters values as i specified.
    a. shared_pool_size = 20M and
    b. db_cache_size = 20M
    then restart Installation.
    This will solve your problem.
    Regards,
    Suraj

  • Install Solution Manager 4.0 Support Release 4 ,JDK ERROR

    I'm install Solution Manager 4.0 Support Release 4  on Windows 2003 Enterprise x64 Edition with Oracle10g
    and JSDK 1_4_2_18,when confirm JDK DIRECTORY,Its shown error below.
    ERROR 2008-07-15 09:00:21.328
    FCO-00011  The step verifyPolicy with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_getJavaHome|ind|ind|ind|ind|1|0|verifyPolicy was executed with status ERROR .
    SAPinst has found a valid JDK directory.The installed JDK has version 1.4.2_18,confirm that you want to use this JDK DIRECTORY.
    Please help me

    Oh, Sory so much
    my step installer
    1. pre-OS configuration parameter (solaris recomment on Master Install)
    2. Installer solution manager
    3. master install disk , select install solution manager 4.0, select OS(solaris) , select DB(oracle)
    4.start install ,
    5. error step ??? 27 "start instance server" fail ????
    error detail.
    error 2008-01-20
    CJS-30149 ABAP Processes of Instance <SID> /Overbmgsoo (ABAP:Msncytrlinnign) class did not start after 50:00 Min Givising up
    error 2008-01-20 17.52
    FCD-00011 th step start with key NW_Onehost|ind|..... Nw_Onehost_system|ind|..... Nw_CI Instance |ind|.... Nw_CI instance start |ind|... start was executed with start erroe
    Thank you.

  • Wily Introscope is not running in Solution Manager 7.1

    Hello Experts,
    wily Introscope is not running in solution manager system,
    below error getting in log, solution manager is running on windows server and how to start wily in windows.
    8/23/14 11:58:50.088 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager Release 9.1.0.0 (Build 581006)
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Introscope installation at: D:\usr\sap\CCMS\apmintroscope\.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] CA Introscope(R) Version 9.1
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Copyright (c) 2011 CA. All Rights Reserved.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope(R) is a registered trademark of CA.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting Introscope Enterprise Manager...
    8/23/14 11:58:50.090 AM IST [INFO] [WrapperSimpleAppMain] [Manager]
    ****** CA Wily Introscope License ******
      type = em-sap
      rev = 30
      cid = sap-ags
      organization = SAP Active Global Support
      reg-id = sap-end-user
      email = none
      sum = 27618b562bc2239e3cf71d9542c76df4
    8/23/14 11:58:50.091 AM IST [INFO] [WrapperSimpleAppMain] [Manager] The Introscope Enterprise Manager is set to run in StandAlone mode.
    8/23/14 11:58:50.113 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting server...
    8/23/14 11:58:52.343 AM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections are enabled
    8/23/14 11:58:52.343 AM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"
    8/23/14 11:58:52.412 AM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private
    8/23/14 11:58:52.628 AM IST [ERROR] [WrapperSimpleAppMain] [Manager] The EM failed to start. Local Users and Groups realm is misconfigured. Error using new settings for Realm: Non existent user "analyst" referenced in "CEM Analyst" group.
    8/23/14 11:58:52.645 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Shutting down the Isengard server
    8/23/14 11:58:52.655 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Orderly shutdown complete.
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager Release 9.1.0.0 (Build 581006)
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Introscope installation at: D:\usr\sap\CCMS\apmintroscope\.
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] CA Introscope(R) Version 9.1
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Copyright (c) 2011 CA. All Rights Reserved.
    8/23/14 12:02:31.585 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope(R) is a registered trademark of CA.
    8/23/14 12:02:31.585 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting Introscope Enterprise Manager...
    8/23/14 12:02:31.585 PM IST [INFO] [WrapperSimpleAppMain] [Manager]
    ****** CA Wily Introscope License ******
      type = em-sap
      rev = 30
      cid = sap-ags
      organization = SAP Active Global Support
      reg-id = sap-end-user
      email = none
      sum = 27618b562bc2239e3cf71d9542c76df4
    8/23/14 12:02:31.586 PM IST [INFO] [WrapperSimpleAppMain] [Manager] The Introscope Enterprise Manager is set to run in StandAlone mode.
    8/23/14 12:02:31.602 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting server...
    8/23/14 12:02:31.958 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections are enabled
    8/23/14 12:02:31.959 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"
    8/23/14 12:02:32.030 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private
    8/23/14 12:02:32.287 PM IST [ERROR] [WrapperSimpleAppMain] [Manager] The EM failed to start. Local Users and Groups realm is misconfigured. Error using new settings for Realm: Non existent user "analyst" referenced in "CEM Analyst" group.
    8/23/14 12:02:32.306 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Shutting down the Isengard server
    8/23/14 12:02:32.321 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Orderly shutdown complete.
    8/23/14 12:37:05.225 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager Release 9.1.0.0 (Build 581006)
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Introscope installation at: D:\usr\sap\CCMS\apmintroscope\.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] CA Introscope(R) Version 9.1
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Copyright (c) 2011 CA. All Rights Reserved.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope(R) is a registered trademark of CA.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting Introscope Enterprise Manager...
    8/23/14 12:37:05.227 PM IST [INFO] [WrapperSimpleAppMain] [Manager]
    ****** CA Wily Introscope License ******
      type = em-sap
      rev = 30
      cid = sap-ags
      organization = SAP Active Global Support
      reg-id = sap-end-user
      email = none
      sum = 27618b562bc2239e3cf71d9542c76df4
    8/23/14 12:37:05.228 PM IST [INFO] [WrapperSimpleAppMain] [Manager] The Introscope Enterprise Manager is set to run in StandAlone mode.
    8/23/14 12:37:05.249 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting server...
    8/23/14 12:37:05.644 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections are enabled
    8/23/14 12:37:05.644 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"
    8/23/14 12:37:05.728 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private
    8/23/14 12:37:05.994 PM IST [ERROR] [WrapperSimpleAppMain] [Manager] The EM failed to start. Local Users and Groups realm is misconfigured. Error using new settings for Realm: Non existent user "analyst" referenced in "CEM Analyst" group.
    8/23/14 12:37:06.014 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Shutting down the Isengard server
    8/23/14 12:37:06.028 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Orderly shutdown complete.
    Please assist me on this
    Best Regards
    Hanuman

    Hello Srivastav,
    i am getting below problem in wily introscope log
    9/01/14 11:22:02.675 AM IST [ERROR] [WrapperSimpleAppMain] [Manager.Acceptor] Failed to bind to server socket
    java.net.BindException: Address already in use: bind
      at sun.nio.ch.Net.bind(Native Method)
      at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
      at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
      at com.wily.isengard.postofficehub.link.server.Acceptor.<init>(Acceptor.java:72)
      at com.wily.isengard.postofficehub.link.server.ConnectionListenerFactory.create(ConnectionListenerFactory.java:31)
      at com.wily.isengard.postoffice.server.PostOfficeHubServer.startIncomingConnectionListener(PostOfficeHubServer.java:261)
      at com.wily.isengard.postoffice.server.PostOfficeHubServer.startAllIncomingConnectionListeners(PostOfficeHubServer.java:235)
      at com.wily.isengard.postoffice.server.PostOfficeHubServer.acceptIncomingHubConnections(PostOfficeHubServer.java:103)
      at com.wily.isengard.api.server.IsengardControllerServer.acceptIncomingConnections(IsengardControllerServer.java:207)
      at com.wily.isengard.api.samplemain.SampleMain.acceptIncomingConnections(SampleMain.java:117)
      at com.wily.introscope.server.enterprise.EnterpriseServer.initialize(EnterpriseServer.java:708)
      at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:358)
      at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
      at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:301)
      at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:280)
      at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1444)
      at com.wily.introscope.em.internal.Activator.startEM(Activator.java:116)
      at com.wily.introscope.em.internal.Application.start(Application.java:27)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      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 org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
      at org.eclipse.core.launcher.Main.main(Main.java:30)
      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 org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:244)
      at java.lang.Thread.run(Thread.java:662)
    9/01/14 11:22:02.679 AM IST [INFO] [WrapperSimpleAppMain] [Manager.PostOfficeHub] Server listening for incoming default socket connections on port 6001
    9/01/14 11:22:02.682 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Connection Initiator listening...
    9/01/14 11:22:02.684 AM IST [INFO] [WrapperSimpleAppMain] [Manager.MMHotDeployEntity] Will monitor D:\usr\sap\CCMS\apmintroscope\deploy for new files every 60 seconds
    9/01/14 11:22:02.685 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager started with management module warnings.
    9/01/14 11:22:42.883 AM IST [INFO] [PO:main Mailman 1] [Manager.LoadBalancer] Loaded loadbalancing.xml
    9/01/14 11:23:31.817 AM IST [INFO] [btpool0-1] [Manager] User "Admin" logged in successfully from host "localhost"
    9/01/14 11:23:31.825 AM IST [INFO] [btpool0-1] [Manager] request.getContextPath() /webview
    9/01/14 11:23:31.826 AM IST [INFO] [btpool0-1] [Manager] Login event Admin 1667ryb11leum 10.1.0.133 true
    9/01/14 11:51:30.061 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409164200000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.063 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409077800000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.064 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409423400000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.066 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409337000000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.067 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409250600000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.088 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1406831400000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.089 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1408991400000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.090 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1408905000000.data seems to be OK - not sure what to do with append inputs
    Please help me to sort this issue,
    Best Regards,
    Hanuman Chinthalwar

  • Install solution manager 4.0 fail (solaris & oracle 10g)

    Install solution manager 4.0 be congested "start instance serveice" step fail.
    Edited by: Kraikanchit Duangdee on Jan 21, 2008 5:00 PM

    Oh, Sory so much
    my step installer
    1. pre-OS configuration parameter (solaris recomment on Master Install)
    2. Installer solution manager
    3. master install disk , select install solution manager 4.0, select OS(solaris) , select DB(oracle)
    4.start install ,
    5. error step ??? 27 "start instance server" fail ????
    error detail.
    error 2008-01-20
    CJS-30149 ABAP Processes of Instance <SID> /Overbmgsoo (ABAP:Msncytrlinnign) class did not start after 50:00 Min Givising up
    error 2008-01-20 17.52
    FCD-00011 th step start with key NW_Onehost|ind|..... Nw_Onehost_system|ind|..... Nw_CI Instance |ind|.... Nw_CI instance start |ind|... start was executed with start erroe
    Thank you.

  • Early watch alert from Solution manager

    Hi ,
    I have been receiving the earlywatch alerts from Solution manager to my mailbox.
    But this week I didn't receive early watch report . I am getting all other alerts through solution manager to my mailbox.
    I checked in the receipients list and my emailID is there and when I checked in SOST in solution manager I can't see that the report in any status there.
    What will be the probelm?
    Please do reply to this query.
    Thanks
    Gayathri.

    Subhash,
    Thanks for the reply, I checked that already.
    I checked and found that in Early watch report is with status data available , but not send .
    Its showing that the job SM:EXEC SERVICES has to run.
    This job has failed in Solution manager with the error as follows.
    ABAP/4 processor: EXPORT_TABLE_UPDATE_CONFLICT
    Job cancelled
    Thanks
    Gayathri

  • Error in Phase Import ABAP by Installation of Solution Manager 4.0

    Hello,
    i have started Installation of Solution Manager 4.0 (Win,MaxDb).An Error occurred during phase Abap Import. From 18 Jobs only 13 was completed, 5 failed. After retry next 3 jobs was completed, but the last 2 will not completed (i have tried 3 times).
    Messages from logs:
    import_monitor.log
    TRACE: 2007-06-09 15:40:49 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is started.
    TRACE: 2007-06-09 15:40:49 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAPAPPL0' import package into database:
    D:\usr\sap\SM2\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -nolog -c 0
    ERROR: 2007-06-09 19:04:59 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is interrupted with R3load error.
    Process 'D:\usr\sap\SM2\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -nolog -c 0' 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
    SAPAPPL0.log
    (IMP) INFO: import of LISCOMDES completed (0 rows) #20070608172145
    (RDI) ERROR: missing attribute description for table "LISDOMAIN" in DB independent control file "E:\install_dvd\export\EXP3\DATA\SAPAPPL0.STR"
    (DB) ERROR: DDL statement failed
    (ALTER TABLE "LISDOMAIN" ALTER PRIMARY KEY ( "DOMNAM", "STATE" ) )
    DbSlExecute: rc = 103
      (SQL error -942)
      error message returned by DbSl:
    (IMP) ERROR: LOCK TABLE failed for table LISDOMAIN
    (RDI) ERROR: missing attribute description for table "LISDOMAIN" in DB independent control file "E:\install_dvd\export\EXP3\DATA\SAPAPPL0.STR"
    Have anybody any ideas or sugestions?
    Regards
    Bogdan Rokosa

    Hello,
    problem solved. After installation stop and system restart, phase ran without errors.
    Regards
    Bogdan Rokosa

  • Solution Manager 7.0 Installation Error on Import ABAP  -Test DB connection

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

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

Maybe you are looking for