Error during Managed system setup "Wilyhost Agent" type

Hello All,
Managed system setup finished with one error. Iam using this for selfmonitoring (solman itself as managed system)
Error msg as follows.
0 Wilyhost Agent(s) from host inbbssun02 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (TDCTBI.india.tcs.com:6001) no Wilyhost Agent was detected from host inbbssun02. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
I checked jvm_SMDAgent.out. and log as follows.
/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.4.2_20-rev" from S
un Microsystems Inc.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.ag
entProfile"
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sa
p.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.ag
ent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval i
s set to 1800
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to
500
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is
set to 3000
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to
locate the extensions directory.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/SMD/J98/SMDAgent/applications.config/
com.sap.smd.agent.application.wilyhost/ext was successfully located
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Pro
perty "com.wily.introscope.agent.agentName".
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
1/06/10 02:55:30 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
[p4://inbbssun02:50004] Agent ready.
1/06/10 02:55:34 PM IST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise
Manager at TDCTBI.india.tcs.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "inbbssun02", Proce
ss = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
Is there any seperate setting for wilyhost agent connection to EM ?
Regards,
Shyam

I have restarted the agent at OS level and it appears in the Agent Admin page.
I then re-ran the Managed System Config for this system and receive the same error.
I have looked at the jvm_smdagent.out file on the wilyhost and found the following errors
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/19/10 12:34:08 PM CET [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly.  Keeping the connection alive.
The agent on the solution manager box is version 7.0 and the version od the agent on the PI box is 7.11
Regards
Stephen

Similar Messages

  • Solman_admin password changes results in errors during managed system setup

    Hello all,
    I am trying to get Solman 4.0 EHP 1 to work, but get numberous problems.
    Currently I have 6 messages at SAP, but no solution yet.
    Situation:
    Solman 4.0
    SAP_BASIS     701     0003
    SAP_ABA     701     0003
    ST-PI     2008_1_700     0000
    PI_BASIS     701     0003
    SAP_BW     701     0003
    CRMUIF     500     0001
    SAP_AP     700     0014
    BBPCRM     500     0013
    CPRXRPM     400     0014
    BI_CONT     704     0002
    ST     400     0019
    ST-A/PI     01L_CRM570     0000
    ST-ICO     150_700     0016
    ST-SER     701_2008_2     0002
    So, it is uptodate.
    The problem:
    Changing the solman_admin password results in errors during connecting a managed system.
    In the inital setup the solman_admin is created with a pasword.
    After the basic setup I setup some managed systems.
    In the meantime I had to change the password of solman_admin
    I am logged in with solman_admin and do solman_setup to setup the managed system.
    During the setup a process tries to logon back to the solman using solman_admin and the incorrect password.
    This is the logging:
    Step SSO Details
    Found SID for SSO ACL entry : MSD
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (823 bytes)
    A failure occured while connecting to ABAP stack on localhost sys=70 client=300 user=SOLMAN_ADMIN
    !! Exception : Password logon no longer possible - too many failed attempts
    A failure occured while importing ABAP SSO ticket certificate in ABAP stack
    !! Exception : java.lang.NullPointerException
    Java SSO ticket certificate of MSD was imported in ABAP PSE of kswv024.mob.local (client 300)
    The Java SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=MSD LoginTicketClient=000)
    Anyone else has this problem?
    gr
    Sander

    Just for clarification it's Solman 7.0 EHP1 correct?
    Also you may want to unlock the following user:
    localhost sys=70 client=300 user=SOLMAN_ADMIN
    Then if you navigate (in solution manager) to TCode solman_workcenter -> "Root Cause Analysis" tab ->"Agent Administration" menu item on the left -> "Applications Configuration" tab -> under the Agent Applications - Configuration menu on the left select "com.sap.smd.agent.application.global.configuration" -> Change the "Scope" drop down in the frame to the right to the SMD agent that you are using for "localhost sys=70 client=300" -> Click the "edit" button to the right of the Scope drop down box -> now find the entry below that lists "SOLMAN_ADMIN" as the user and find the corresponding password entry and update it with the new password that you changed it to -> click save and try the managed setup again.
    Hope this helps, please let me know and we can go from there.

  • No P4 connection could be established to SID during managed systems setup

    Hi,
    I get the following error when executing managed systems setup Create Users request.
    No P4 connection could be established to BJR
    No configuration found for key (BJR/sapj2ee/msgserver/host). DETECTED Self-managing scenario. You need to first adapt the connectivity of Diagnostics Agent used for the Managed system BJR, before you could proceed with this setup. Therefore change the Agent connection type for the BJR relevant Diagnostics Agent to P4 Dispatcher, before you run again this setup. This connection update has to be performed in the Agent Administration under Agent Connectivity. You could access the Agent Administration from the Root Cause Analysis Work Center when logged as Solution Manager Administrator.
    I have deleted and manually recreated SM_ADMIN_SOL, SAPSUPPORT and SM_COLL_SOL users, but still get the same issue.
    Message server ports etc are correct. Screenshot below.
    I have reviewed OSS note 1678469 but not resolved the issue.
    Any ideas will be appreciated.
    Regards
    Tariq

    Hi,
    As stated please review how do you register dia agent in solution manager, you can check in step 4 assign diagnostic agent in solman_setup.
    further review the below doc for dia agent registration via P4 port  Diagnostics Agents - SAP Solution Manager Setup - SCN Wiki
    Thanks
    Jansi

  • Link SAP PI 7.3 to SolMan 7.1 - error during managed system configuration

    All,
    I installed my diagnostics agent twice with different options:
    - Direct P4 connection via Java EE Dispatcher Node with port 5xx04
    - P4 connection via SCS message server with port 81xx
    In both cases I get an error during the managed system configuration of SAP PI 7.3: Remote error : Connection to P4 port of managed system failed.
    I'm a bit confused with the step Enter System Parameters. In the Java parameters section, I can only enter port 39xx. if not, I get an error.
    Also, I marked and unmarked the option concerning the ABAP user store, but the error persists.
    Please advice.
    Thanks a lot.

    Hi Allam,
    I checked the KBA and I think now, I have the correct HTTP port.
    The error I now get is S:CL_DIAGSTP_MESSAGE:483
    When I take the next step, Configure Automatically, I get this error during the Byte Code Adapter Installation phase when I open the Java URL stated in the navigation column:
    DIAG_WILY_MSG:157:S - com.sap.smdagent.vmmanager.VMManagerP4Exception: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid: check the connection credentials.More details about the error in agent 'sappi' log file (SMDAgentApplication.X.log).; nested exception is:
    com.sap.engine.services.security.exceptions.BaseLoginException: Error during authentication. For more information see the remote server traces.
    Any idea?
    Thanks.

  • Solution Manage Diagnostics - error in the system setup

    Hello,
    I have installed SMD and I installed one system with the Setup Wizard of the SMD. According to the result of the setup, it was successful.
    However, when I do a self check in SMD, I get the five following errors in the Monitored Setup node :
    5 error(s) found:
    No DB agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No JVM startup parameters setting status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No Roles assignment status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No SSO Setup status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    No Telnet agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
    Can anybody help me ?
    Thank you

    If you goto http://server:port/smd >>> Diagnostic Setup >>> Diagnostic System >>> Setup Wizard, do you have a message similar to:
    Last Diagnostics setup wizard execution on Tue Oct 09 13:34:44 2007 :
    - 0 setup steps disabled by user
    - 13 setup steps succesfully executed
    - 0 setup steps executed with warnings
    - 0 setup steps in error
    If you do, your Diagnostic server is correctly setup.
    For Managed system, same thing, http://server:port/smd >>> Diagnostic Setup >>> Managed Systems >>> Setup Wizard, or check setup results to make sure it's completed.

  • Managed System Setup Wizard Status " ? " SPS 15

    Dear All,
    I have a problem with my SMD.
    I have already upgrade the Solution Manager 4.0 from SPS 13 to SPS 15.
    I want to setup E2E Root Cause Analysis for CRM system.
    So I configured SMSY since I didn't configure SLD yet.
    I've already installed SMD Agent in managed system successfully also.
    When I run the Diagnostics Setup -> Managed System -> Setup WIzard,
    in the Setup Parameter Step , it said that " No SMD Agent is currently available (ie not assigned). Please install an agent for jktgrhxsapc1 or unassign an existing agent in Agent Administration  Why is that so ?
    In the Agent Administration ( DIagnostics Administration -> Managed SYstem -> Agent Administration) found that the agent is online.
    Second, In managed system setup wizard - System Selection Step, there's an unknown system with SID '???' and  the status said that 'Some SMD Agent Runnning on host not belonging any successfully published solution' . Where can we find the log if we have an error when publishing solution ?
    Thanks in advance,
    Adhi

    Hi Labinot,
    I have checked the agent log looks like no error,
    id loaded TTL refType
    applications:com.sap.smd.agent.application.global.configuration true 0 strong
    applications:com.sap.smd.agent.application.tracing true 0 strong
    applications:com.sap.smd.agent.application.wilyhost true 0 strong
    applications:com.sap.smd.agent.application.flightrecorderdumpscan true 0 strong
    applications:com.sap.smd.agent.application.telnet true 0 strong
    applications:com.sap.smd.agent.application.filesystem true 0 strong
    applications:com.sap.smd.agent.application.logviewer true 0 strong
    applications:com.sap.smd.agent.application.remotesetup true 0 strong
    applications:com.sap.smd.agent.application.database true 0 strong
    applications:com.sap.smd.agent.application.datacollector true 0 strong
    applications:com.sap.smd.agent.application.runtime true 0 strong
    applications:com.sap.smd.agent.application.connectors true 0 strong
    applications:com.sap.smd.agent.application.wily true 0 strong
    Apr 10, 2008 7:13:07 PM [Thread[SMDAgent connection thread,5,main]] Info       [p4://jktgrhxsapl1:50604] Registration done.
    Apr 10, 2008 7:13:07 PM [Thread[SMDAgent connection thread,5,main]] Info       [p4://jktgrhxsapl1:50604] Agent ready.
    Apr 10, 2008 7:27:25 PM [Thread[Thread-37,5,main]] Info       Returned service object :com.sap.smd.core.runtime.agent.LogService@14cee41f
    Apr 10, 2008 7:27:26 PM [Thread[Thread-34,5,main]] Info       Returned service object :com.sap.smd.core.runtime.agent.LogService@14cee41f
    any other idea?
    -Adhi-

  • SMD - MANAGED SYSTEM SETUP WIZARD.

    Hi,
    I'm on Solman SPS 15, trying to setup EWA for portals.
    Ran the managed system setup, got the error.
    Step DataCollect Details
    Initial Data Collect ERROR for host XXXXXXX
    !! Exception : Tue Jun 24 11:03:08 EDT 2008 | storeComponentVersion(...):ComponentVersion ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1199734241239977, name=SAP J2EE ENGINE 7.00, internalVersion=7.00   PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 11:03:06 EDT 2008, status=[N], mod=[M], messageServer=XXXXX:3901, masterComponent=true]'! Please see log for next warning(s).
    com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: Tue Jun 24 11:03:08 EDT 2008 | storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1199734241239977, name=SAP J2EE ENGINE 7.00, internalVersion=7.00   PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 11:03:06 EDT 2008, status=[N], mod=[M], messageServer=XXXXXX:3901, masterComponent=true]'! Please see log for next warning(s).
    at com.sap.sup.admin.scheduler.task.remote.AbstractGatherRemoteTask.checkTaskResult(AbstractGatherRemoteTask.java:42)
    at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.parseXml(InitialConfigGatherTask.java:107)
    at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:68)
    at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)
    at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:305)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:263)
    at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:655)
    at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)
    at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:903)
    at java.lang.Thread.run(Thread.java:534).
    Plz advise.
    Thx in advance.

    #1.#00144F17012A00C700000018000066BD0004506CFD4B5C16#1214328943107#/Applications/AdminConsole/ConfigurationChangeReportingUpload#sap.com/tcwddispwda#com.sap.sup.admin.upload.configreport.xml.ConfigurationChangeHandler#J2EE_ADMIN#16932##XXXXX_SID_28888050#J2EE_ADMIN#0964c860421111dd94ec00144f17012a#Thread[Thread-83,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/Applications/AdminConsole/ConfigurationChangeReportingUpload#Plain###[7498] storeComponentVersion(...):ComponentVersion [SAP J2EE ENGINE 7.00][01200314690200004229][N/A][N/A]:Cannot insert/update/delete the component '[IComponent: key=1214257551084558, name=SAP J2EE ENGINE 7.00, internalVersion=7.00   PatchLevel 29172.450, ppmsId=01200314690200004229, date=Tue Jun 24 13:35:42 EDT 2008, status=[N], mod=[M], messageServer=XXXXX:3901, masterComponent=true].
    I found this in application log
    Edited by: Kobby bryant on Jun 24, 2008 7:39 PM

  • Managed System Setup / Configure Diagnostics for Solution Manager itself

    Hello,
    I'm trying to run the "Managed System Setup" for the Solution Manager itself and
    I got a problem in the step 4 (Diagnostics Configuration / Configure Diagnostics):
    In the new opened window is only the ABAP stack displayed and the Java stack
    is missing.
    Does somebody know how to make the java stack visible?
    From my point of view seems the configuration of the SMSY ok. The java stack is also
    as "relevant" set.
    The Solution Manger 7.0 EHP1 is on SP25.
    Thanks in advance for your help!
    Kind regards,
    Joern

    Hi Jorn,
    I dont think its happening just because of your CR Content.
    Still If you want to update it,then go to Administration Tab in SLD->>Import the latest CR Content from there.
    As the latest CR Content is :SAP CR Content Version (sld/active):     SAP_CR 7.6 (produced 11/17/2011)
    And Jorn if you are stucked in the Diagnostic Agent registration then Go to Agent Candidate Administration->>In connection
    Parameters Tab go to->>Custom SLD Connection Parameters->>Apply->>Mark the Diagnostic Agent you want to
    connect->>Attach->>Give the password of the SMD_ADMIN->>Apply->>This way you will connect to the available Diagnostic
    Agent.Hope this will help your problem.
    Thanks & Regards
    Ajitabh
    Edited by: jitu001 on Dec 23, 2011 5:47 PM

  • RCS Managed system setup

    Hi,
    Do we need to re run managed system setup wizard, each time system stack or EHP is updated ? or even when solman stack is updated ?
    Reason: We recently updated solman to SPS27 after which I dont see any data collection happening specially for User Load for ABAP systems
    and none for java
    BR,
    Shyam

    Hello,
    Run transaction solman_setup and check in the OVERVIEW what are the Open Activities listed in Basic and Initial Configuration.
    All activities there must be redone, grey, red or green.
    In these tasks there will be the Diagnostics Configuration. This step includes setting the Maintenance Mode ON and OFF, which will stop all agents and deploy the new software to them (the so-called agelets that are delivered centrally from Solman LM-SERVICE to the managed system's SMD Agent).
    This is all you must execute after a LM-SERVICE upgrade.
    Therefore there's no reason to rerun the whole setup wizard, as it may cause issues with wrong parameters in the setup wizard. If the managed system is working perfectly and this is only an upgrade, it is not recommended to do the setup wizard again.
    Best regards,
    Guilherme
    Edited by: Guilherme Balbinot on Jul 15, 2011 8:37 AM
    Edited by: Guilherme Balbinot on Jul 15, 2011 8:41 AM

  • Managed System Setup Wizard: which J2EE-Admin-User

    Hello,
    I'm running the managed system setup wizard in the diagnostic.
    In the setup of the parameters, I have to enter the J2EE-Admin-User. But which one?
    I tried:
    SMD_AGT_ADM (Dialog user with admin roles on both stacks)
    SMD_AGT_ADM (Communications user with admin roles on both stacks)
    The user was created by me before the setup. But regardless of the user settings, I get the following error:
    A logon failure occured on frces4139/SM7/00 (192.168.1.139).
    System Setup aborted, to prevent locking the User Account.
    Please check error details, specify a valid User/Password if necessary, and start Setup again
    Any ideas? Which user or user settings have to be maintained?
    Thanks,
    Jan

    Hello,
    I think the user you need to enter here is the j2ee_admin user or another user with SAP_J2EE_ADMIN role.
    Regards,
    Benjamin Rouger

  • Error in Managed System Configuration - Sol Man 7.1

    Dear Experts,
    Whle configuring using solman_setup, I am getting below mentioned error in Managed System Configuaration:
    Cannot retrieve CIM Instances from CIM Class 'SAP_DiagnosticsRelevantSoftwareFeature'!
    Cannot  retrieve all CIM Instances from CIM class name 'SAP_TechnicalScenario' via LMDB Mass Access API!
    Cannot retrieve all CIM Instances from CIM class name 'SAP_DatabaseSystem' via LMDB Mass Access API!
    Any suggestions??
    Regards
    Vivek

    Hi Paul ,
    Thanks for the note that you provided.
    I am reconfiguring the LMDB and conteny Sync... The refresh will take 15-16 hours.. I am just waiting for the
    sync to be finished. Let's see what is in the store for me
    Keeping my fingers crossed untill then.
    Regards
    Vivek

  • SMD Error in managed system type PI 7.1 EHP1 Step Logical Ports error

    Hi people,
    Solution Manager Ehp1 7.0 SPS24
    I am currently runnig the wizard setup for managed System, everything is fine but when I run for PI 7.1 I get the following error:
    Fri Sep 10 20:29:48 2010 Logical Ports A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
    Step Logical Ports Details
    A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
    !! Exception : PORT_NOT_CREATED
    Exceptions
    com.sap.mw.jco.JCO$AbapException: (126) PORT_NOT_CREATED: PORT_NOT_CREATED
    at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1511)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
    at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
    at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
    at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
    at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
    at java.lang.Thread.run(Thread.java:534)
    Any ideas?
    Thanks in advance

    Hi everyone,
    Thanks everyone.
    Guilherme, finally I understand what really happens.  "Refresh" is not working properly in the Setup Wizard.
    First I have done what I can:
    System    Type      Managed Products                    Product Instances
    DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP  (I could not select PI at the same time)
    DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
    But, when I refresh the browser Internet Explorer appears the following:
    System    Type      Managed Products                    Product Instances
    DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP + Process Integration
    DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
    And then I do not get the error anymore. (I have to repeat step 2 in the wizard "Check Prerequisites for Diagnostics)
    And If I run transaction SMSY, I can see how PI is mantained since the wizard refresh SMSY.
    Product Instance Selection tab:
    Application Server ABAP (Flag selected: relevant)
    Process Integration (Flag selected: Also Installed, Technical System[ DPI, Java])
    Application Server Java (Flag selected: relevant, Technical System[ DPI, Java])
    So, if I use this configuration in the SMSY, when I run "solman_setup",  configuring DPI (My PI7.1), when I run "Configure Diagnostics", the wizard shows ABAP + PI as expected.
    Thanks a lot Guilherme!!

  • Identity Management System Setup Error

    In Global Settings tab when I try to set up identity management system for lotus notes by providing proper host name, user name and password I get following error on oc4j log file
    07/03/28 14:22:05 org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.ibm.CORBA.iiop.ORB vmcid: 0x0 minor code: 0 completed: No
    07/03/28 14:22:05      at org.omg.CORBA.ORB.create_impl(ORB.java:297)
    07/03/28 14:22:05      at org.omg.CORBA.ORB.init(ORB.java:336)
    07/03/28 14:22:05      at lotus.domino.cso.Session.getORBObject(Session.java:746)
    07/03/28 14:22:05      at lotus.domino.cso.Session.OREFtoSession(Session.java:780)
    07/03/28 14:22:05      at lotus.domino.cso.Session.<init>(Session.java:73)
    07/03/28 14:22:05      at lotus.domino.cso.Session.createSession(Session.java:41)
    07/03/28 14:22:05      at lotus.domino.NotesFactory.createSession(NotesFactory.java:67)
    07/03/28 14:22:05      at oracle.search.plugin.security.identity.ln.LNIdentityPluginRepositoryAccess.login(LNIdentityPluginRepositoryAccess.java:119)
    07/03/28 14:22:05      at oracle.search.plugin.security.identity.ln.LNIdentityPluginManager.validateParams(LNIdentityPluginManager.java:367)
    07/03/28 14:22:05      at oracle.search.admin.system.ctrl.SystemCtrl.identityMgmtActivate(SystemCtrl.java:1069)
    07/03/28 14:22:05      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    07/03/28 14:22:05      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    07/03/28 14:22:05      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    07/03/28 14:22:05      at java.lang.reflect.Method.invoke(Method.java:324)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.MethodEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.BasePageFlowEngine.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.AbstractPageBroker.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.ui.BaseUIPageBroker.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Unknown Source)
    07/03/28 14:22:05      at control.idmgmt__activate._jspService(_idmgmt__activate.java:1618)
    07/03/28 14:22:05      at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
    07/03/28 14:22:05      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    07/03/28 14:22:05      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
    07/03/28 14:22:05      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    07/03/28 14:22:05      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    07/03/28 14:22:05      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    07/03/28 14:22:05      at java.lang.Thread.run(Thread.java:534)
    07/03/28 14:22:05 Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: com.ibm.CORBA.iiop.ORB
         Dependent class: org.omg.CORBA.ORB
         Loader: jre.bootstrap:1.4.2_08
         Code-Source: unknown
         Configuration: jre bootstrap
    This load was initiated at search_admin.web.admin:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    07/03/28 14:22:05      at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2078)
    07/03/28 14:22:05      at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1679)
    07/03/28 14:22:05      at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1635)
    07/03/28 14:22:05      at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1620)
    07/03/28 14:22:05      at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    07/03/28 14:22:05      at java.lang.Class.forName0(Native Method)
    07/03/28 14:22:05      at java.lang.Class.forName(Class.java:219)
    07/03/28 14:22:05      at org.omg.CORBA.ORB.create_impl(ORB.java:295)
    07/03/28 14:22:05      ... 36 more
    07/03/28 14:22:05 lotus.domino.NotesException
    07/03/28 14:22:05      at lotus.domino.cso.Session.OREFtoSession(Session.java:825)
    07/03/28 14:22:05      at lotus.domino.cso.Session.<init>(Session.java:73)
    07/03/28 14:22:05      at lotus.domino.cso.Session.createSession(Session.java:41)
    07/03/28 14:22:05      at lotus.domino.NotesFactory.createSession(NotesFactory.java:67)
    07/03/28 14:22:05      at oracle.search.plugin.security.identity.ln.LNIdentityPluginRepositoryAccess.login(LNIdentityPluginRepositoryAccess.java:119)
    07/03/28 14:22:05      at oracle.search.plugin.security.identity.ln.LNIdentityPluginManager.validateParams(LNIdentityPluginManager.java:367)
    07/03/28 14:22:05      at oracle.search.admin.system.ctrl.SystemCtrl.identityMgmtActivate(SystemCtrl.java:1069)
    07/03/28 14:22:05      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    07/03/28 14:22:05      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    07/03/28 14:22:05      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    07/03/28 14:22:05      at java.lang.reflect.Method.invoke(Method.java:324)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.MethodEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.BasePageFlowEngine.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.AbstractPageBroker.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.ui.BaseUIPageBroker.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Unknown Source)
    07/03/28 14:22:05      at control.idmgmt__activate._jspService(_idmgmt__activate.java:1618)
    07/03/28 14:22:05      at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
    07/03/28 14:22:05      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    07/03/28 14:22:05      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
    07/03/28 14:22:05      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    07/03/28 14:22:05      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    07/03/28 14:22:05      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    07/03/28 14:22:05      at java.lang.Thread.run(Thread.java:534)
    07/03/28 14:22:05 oracle.search.sdk.common.PluginException: Login failed for host name
    07/03/28 14:22:05      at oracle.search.plugin.security.identity.ln.LNIdentityPluginManager.validateParams(LNIdentityPluginManager.java:376)
    07/03/28 14:22:05      at oracle.search.admin.system.ctrl.SystemCtrl.identityMgmtActivate(SystemCtrl.java:1069)
    07/03/28 14:22:05      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    07/03/28 14:22:05      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    07/03/28 14:22:05      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    07/03/28 14:22:05      at java.lang.reflect.Method.invoke(Method.java:324)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.MethodEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.event.BasePageFlowEngine.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.AbstractPageBroker.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.ui.BaseUIPageBroker.handleRequest(Unknown Source)
    07/03/28 14:22:05      at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Unknown Source)
    07/03/28 14:22:05      at control.idmgmt__activate._jspService(_idmgmt__activate.java:1618)
    07/03/28 14:22:05      at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
    07/03/28 14:22:05      at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
    07/03/28 14:22:05      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    07/03/28 14:22:05      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
    07/03/28 14:22:05      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    07/03/28 14:22:05      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    07/03/28 14:22:05      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    07/03/28 14:22:05      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    07/03/28 14:22:05      at java.lang.Thread.run(Thread.java:534)
    Please help
    Thanks in advance,
    Shakti

    Did you evern get a solution to your problem? We are experiencing the same exception:
    <2008-06-30 17:38:41,936> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Creat
    ing new instance of Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
    08/06/30 17:38:41 java.lang.Exception: Failed to create "ejb/collaxa/system/ActivationAgentManagerBe
    an" bean; exception reported is: "javax.naming.NoInitialContextException: Cannot instantiate class:
    com.evermind.server.ApplicationInitialContextFactory [Root exception is oracle.classloader.util.Anno
    tatedClassNotFoundException:
              Missing class: com.evermind.server.ApplicationInitialContextFactory
            Dependent class: com.sun.naming.internal.VersionHelper12
                     Loader: jre.bootstrap:1.5.0_06
                Code-Source: unknown
              Configuration: jre bootstrap
    This load was initiated at JmsAdapter:0.0.0 using the Class.forName() method.
    The missing class is available from the following locations:
            1. Code-Source: /D:/product/10.1.3.1/OracleAS_1/j2ee/home/lib/oc4j-internal.jar (from <code-
    source> in META-INF/boot.xml in D:\product\10.1.3.1\OracleAS_1\j2ee\home\oc4j.jar)
               This code-source is available in loader oc4j:10.1.3.
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at com.oracle.bpel.client.util.BeanRegistry.lookupActivationAgentManagerBean(BeanRegistry.ja
    va:700)
    at com.oracle.bpel.client.ActivationAgentHandle.getActivationAgentManager(ActivationAgentHan
    dle.java:205)
    at com.oracle.bpel.client.ActivationAgentHandle.addStats(ActivationAgentHandle.java:235)
    at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.publishAdapterStopWatch(AdapterFramewo
    rkListenerBase.java:2227)
    at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.publishAdapterStopWatch(Messa
    geEndpointImpl.java:490)
    at oracle.tip.adapter.fw.sw.AdapterStopWatchManager.publishInboundAdapterStopWatch(AdapterSt
    opWatchManager.java:241)
    at oracle.tip.adapter.fw.sw.AdapterStopWatchManager.stopInboundAdapterStopWatch(AdapterStopW
    atchManager.java:211)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:373)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.onMessage(JMSMessageConsumer.java:475)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.Kernel.execute(Kernel.java:343)
    at weblogic.kernel.Kernel.execute(Kernel.java:367)
    at weblogic.kernel.Kernel.execute(Kernel.java:355)
    at weblogic.jms.client.JMSSession.pushMessage(JMSSession.java:2474)
    at weblogic.jms.client.JMSSession.invoke(JMSSession.java:3006)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:132)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchOneWay(DispatcherImpl.java:341)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: oracle.classloader.util.AnnotatedClassNotFoundException:
    Missing class: com.evermind.server.ApplicationInitialContextFactory
    Dependent class: com.sun.naming.internal.VersionHelper12
    Loader: jre.bootstrap:1.5.0_06
    Code-Source: unknown
    Configuration: jre bootstrap
    This load was initiated at JmsAdapter:0.0.0 using the Class.forName() method.
    1. Code-Source: /D:/product/10.1.3.1/OracleAS_1/j2ee/home/lib/oc4j-internal.jar (from <code-
    source> in META-INF/boot.xml in D:\product\10.1.3.1\OracleAS_1\j2ee\home\oc4j.jar)
    This code-source is available in loader oc4j:10.1.3.
    at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2078)
    at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1679)
    at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1635)
    at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1620)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:242)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
    ... 32 more
    ".

  • SOLMAN_SETUP Wizard - Error on Managed System Configuration

    Hi all,
    I've installed SAP Solution Manager 7.0 EHP1 (Stack 19) on linux-oracle.
    After I start the configuration with SOLMAN_SETUP tcode.
    The "Initial Configuration" and the "Basic Configuration" phases are termined with success.
    In the third phase "Managed System Configuration", I try to connect itself on client 001 but when I try to generate the RFC Connection I received an error message on wizard when the system create the "Back RFC Destination". If I check this RFC on SM59 tcode it works!!!! I don't understand why I received the error message during the wizard.
    Then on "Check Prerequisites" I execute the "Diagnostic Prerequisites" phase and I received 2 error messages:
    a) The Introscope Enterprise Manager configuration cannot be loaded. Details:
    java.sql.SQLException: All configured Enterprise Managers are offline - check configuration.     at com.sap.sup.admin.wily.jdbc.EMOverview.getQueryEMgrs(EMOverview.java:251)     at com.sap.sup.admin.wily.jdbc.EMOverview.populateAgentCache(EMOverview.java:415)     at com.sap.sup.admin.wily.jdbc.EMOverview.checkAgentCache(EMOverview.java:461)     at com.sap.sup.admin.wily.jdbc.EMOverview.getAllEMgrs(EMOverview.java:220)     at com.sap.sup.admin.selfcheck.checks.wily.em.EmJdbcCheck.process(EmJdbcCheck.java:32)     at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165)     at sun.reflect.GeneratedMethodAccessor342.invoke(Unknown Source)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)     at java.lang.reflect.Method.invoke(Method.java:391)     at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)     at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)     at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)     at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)     at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)     at java.lang.Thread.run(Thread.java:770)
    b) The RFC Read Destination is not available for connection to Satellite System (RC=2). Details:
    Please check SAP Note 1106900
    I find The RFC Read Destination on SM59 tcode and it works if I try to "Connection Test".
    Could you please help me to check the two errors??
    Thanks in advanced
    Moreno

    Some more info when I tried to run the setup wizard again.
    Step Wilyhost Agent Details
    Setup Exception: Empty or no Wily EM host retrieved from secured global config! Going on with "localhost".
    Setup Exception: No Wily EM port was passed by SetupWizard! Going on with port 6001 instead.
    Created destination XXX|hostname_xxx_01
    Created action xxx -XXX AbapSystem
    Created action xxx|hostname_xxx_01 - XXX|hostname_xxx_01 AbapInstance
    Created 2 action(s).
    Retrieving list of Enterprise Managers failed: All configured Enterprise Managers are offline - check configuration.
    Exceptions
    java.sql.SQLException: All configured Enterprise Managers are offline - check configuration.
    at com.sap.sup.admin.wily.jdbc.EMOverview.getQueryEMgrs(EMOverview.java:251)
    at com.sap.sup.admin.wily.jdbc.EMOverview.populateAgentCache(EMOverview.java:415)
    at com.sap.sup.admin.wily.jdbc.EMOverview.checkAgentCache(EMOverview.java:461)
    at com.sap.sup.admin.wily.jdbc.EMOverview.getAgentEMgrs(EMOverview.java:269)
    at com.sap.sup.admin.wily.hostagent.Setup.emCanBeAccessed(Setup.java:440)
    at com.sap.sup.admin.wily.hostagent.Setup.executeSetup(Setup.java:87)
    at com.sap.sup.admin.setup.AppCfgTasks.configureEPAgent(AppCfgTasks.java:110)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:416)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:328)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:545)
    at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1680)
    at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
    at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1950)
    at java.lang.Thread.run(Thread.java:571)
    hostname is the hostname of the system, i removed it.
    xxx is the solution manager sid.

  • Configuration Check Error in Managed System Configuration

    Hi dear experts,
    I come across a problem as the screenshot shows blew:
    I check some relevant information, but no issues found:
    1.
    DEWDFLSSC5062:/usr/sap/hostctrl/exe # ./saphostexec -status
    saphostexec running (pid = 7094)
    sapstartsrv running (pid = 7097)
    10:46:34 24.06.2014     LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
    saposcol running (pid = 7130)
    DEWDFLSSC5062:/usr/sap/hostctrl/exe # cat host_profile
    SAPSYSTEMNAME = SAP
    SAPSYSTEM = 99
    service/porttypes = SAPHostControl SAPOscol SAPCCMS
    DIR_LIBRARY = /usr/sap/hostctrl/exe
    DIR_EXECUTABLE = /usr/sap/hostctrl/exe
    DIR_PROFILE = /usr/sap/hostctrl/exe
    DIR_GLOBAL = /usr/sap/hostctrl/exe
    DIR_INSTANCE = /usr/sap/hostctrl/exe
    DIR_HOME = /usr/sap/hostctrl/work
    service/admin_users = daaadm
    service/logfile_000 = /tmp/s
    service/logfile_001 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace*.trc
    service/logfile_002 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.*.trc
    service/logfile_003 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.trc
    And the version of hostagent is up-to-date.
    2.The URL
    - http://<SMDhost>:1128/SAPOscol/?wsdl
    - http://<SMDhost>:1128/SAPHostControl/?wsdl
    can be accessed.
    3.The step 3 in managed systems configuration is executed successfully.
    4.I have even uninstalled and re-installed the SMD and hostagent, and change the alert_timeout parameter in T-code DMD, but the issue insisted.
    5.Only a few SMDs in my landscape, so I think the parameter MaxThreadCount, InitialThreadCount, MinThreadCount should be no problem.
    Now I have no idea how to proceed, please give me some advice, thank you in advance.
    Best Regards,
    Pany Pan

    Hi Pany
    Kindly check the below two sapnote
    1935653 - Error "A timeout occured during the execution of the OS Command Console" when performing a Managed System Configuration - Solution Manager 7.1
    1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution of the OS Command Console" "An unexpected error occured"
    Moreover , you need to check/verify/maintain the parameter in configtool
    ThreadManager -> MaxThreadCount
    Total number of Diagnostics Agents * 2 + 50
    1250
    ThreadManager -> InitialThreadCount
    Total number of Diagnostics Agents * 1.5
    900
    ThreadManager -> MinThreadCount
    Total number of Diagnostics Agents
    600
    ConnectionManipulator -> maxSoTimeOutConnections
    Total number of Diagnostics Agents * 1.35
    810
    ConnectionManipulator -> MaxParallelUsers
    Total number of Diagnostics Agents + 50
    650
    In Diagnostics Agent Troubleshooting - SAP Solution Manager Setup - SCN Wiki 
    guide check the section Required Solution Manager Java Stack Settings (Scalability)
    I face the same issue , which got resolved by maintaining the above parameters, maxthreadCount,
    minthreadcount , maxSoTimeOutConnections.
    With Regards
    Ashutosh Chaturvedi

Maybe you are looking for

  • AR down Payment invoice

    Hello Experts                        I did a sales order say for 500000. i selected the same in AR down payment invoice.By default in DPM it is 100%.i did not changed that.Through payment means i received 200000 .Now the balance due is 300000 down pa

  • Tomcat installation

    hi all well i'm facing problemin configuring tomcat please if anyone can help me out on this on i will be greatful well i have set all TOMCAT_HOME and JAVA_HOME variables plus the jdk path and classpath is correct i'm using jdk1.2.2 and tomcat 3.2.4

  • Connect to DB2 from oracle 11g on windows 2008 server

    Hi Folks, I want to conenct to DB2 from oracle 11g using DB link. DB2 : user : db2user pwd : db2pwd database : db2database (OSBLDEV) able to connect to db2 server (installed on machine M1) using db2 client with above details from machine M2 (where or

  • Cols in smartforms

    hai abapers,      i have a requirement in which i have to supress the whole column in the table. is it possible in smartforms. plz respond quickly. its urgent

  • Bridge Prerelease Program Openings

    Bridge Customers, We are looking for a few interested Adobe Bridge users to join our Prerelease Program. We need customers who use Bridge in their workflow regularly and want to provide constructive feedback to the Bridge team on monthly prerelease b