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

Similar Messages

  • No hosts found in SMD Managed Sytem Setup Wizard

    Dear Experts,
    I connected a Portal system to SMD server. I manaualy defined the system in SMSY instead of SLD.
    When I went to the SMD Managed System Setup Wizard, it reported"No instances or
    servers are defined for this system. Please check its definition in SMSY before proceeding to setup".
    I've carefully checked all system definition in SMSY. I wonder if others have come across the similiar
    problem, sincerely hoping for your advice.
    Best Regards,
    Karl

    Hi, David,
    I just can't find my installed agents in SLD view. But under Agent administration Agent Tab I can see them with status green. I installed agent without registration to SLD, but user directly P4 connection.
    I tried go SMD view, I can see my agents there , and it has a column SLD settings, push SLD settings,
    I clicked to push SLD settings, but an error occured:(Failed to send SLD settings to remote agent: sapeppap01 (detail: Failed to save new SLD settings; nested exception is: java.lang.StringIndexOutOfBoundsException: String index out of range: -1).
    Best Regards,
    Karl

  • 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-

  • 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

  • Diagnostics System: Managed System Setup Wizard

    Hi there!
    I have installed the Host Agent and Diagnostic Agent on a test-system successfully. Now I have tried to start the Setup Wizard for managed systems (http://<hostname>:port/smd). The system collection was no problem, but the Setup Parameters. If I choose the directories of the "System Install Path",  the "Instance Path" and also the "Instance Number" the following Message appears: "No Diagnostics Agent available at this time Please install or start an SMD Agent for <hostname>".
    I don't know the reason, because the Diagnostic Agent is running and I think my parameters will be okay:
    System Install Path: usr/sap/DAA/
    Instance Path: usr/sap/DAA/SMDA97/
    Instance Numer: 97
    Is there a failure?
    I look forward to your reply!
    Best reagrds,
    Andreas

    Hi there!
    I have found an interesting warning:
    Managing System '<hostname>' is  registered in the SLD but the CIM declaration is not valid, the agents cannot be attached correctly. check SLD Managing system declaration. (detail: CIM_ERR_FAILED: Cannot find SAP_BCCentralServiceInstance of SAP_J2EEEngineCluster SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="<hostname>" in SLD LR)
    I think it is the reason for my problems .. Can anybody help me?
    Best regards,
    Andreas

  • 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

  • Cisco Ironport ESA System setup wizard

    Hi all,
    i'm installing a Cisco ESA. I configured IP of Data1 and Management and Hostname with temporary data to enable feature keys.
    Now i have to migrate those parameter to final configuration except management. IF i run again the system setup wizard does it blow up
    the features installed and activated? 
    Thanks
    smaikol

    If you re-run systemsetup again from the CLI - it will reset the IP and listeners you have configured, along with the network information associated.  You are presented the warning message from the CLI:  
    WARNING: The system setup wizard will completely delete any existing 'listeners' and all associated settings including the 'Host Access Table'
    - mail operations may be interrupted.
    </warning>
    The features themselves are still present and licensed, and should not change.  During the setup wizard prompts - you are asked if you want to use and enable the features - such as Anti-Spam, Anti-Virus:
    Do you want to use Anti-Spam scanning in the default Incoming Mail policy? [Y]> 
    Would you like to enable the Spam Quarantine? [Y]> 
    1. IronPort Anti-Spam
    2. Intelligent Multi-Scan
    3. Cloudmark Service Provider Edition
    Enter the number of the Anti-Spam engine you would like to use on the default Incoming Mail policy.
    []> 1
    IronPort selected for DEFAULT policy
    Do you want to use Anti-Virus scanning in the default Incoming and Outgoing Mail policies? [Y]> 
    1. McAfee Anti-Virus
    2. Sophos Anti-Virus
    Enter the number of the Anti-Virus engine you would like to use on the default Incoming and Outgoing Mail policies.
    []> 2
    Sophos selected for DEFAULT policy
    Do you want to use Anti-Malware scanning in the default Incoming Mail policies? [Y]> 
    Advanced Malware Protection selected for DEFAULT policy
    Do you want to enable Outbreak Filters? [Y]> 
    Outbreak Filters enabled.
    Allow the sharing of limited data with SenderBase? [Y]> 
    You have successfully configured Outbreak Filters and SenderBase.
    </setup>
    Usually, it is just simpler if you are re-IPing the ESA from a temporary IP to permanent IP to just change the information associated via ifconfig and modify the interface as needed, or on the GUI use Network > IP Interfaces.  
    -Robert

  • 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

  • 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

  • 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

  • Failed to push XML template when setup SMD Managed system

    Hi,
    when I setup a managed system in SMD, I receive the warning:
    XML Templates pushed : 0 successful, 1 failed
    Failed to push XML template to sv50761/TP4/10 (sv50761.RUV.DE) : com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad Attribute value(:main:, row:10, col:79)(cause=com.sap.engine.lib.xml.pars
    er.ParserException XMLParser: Bad Attribute value (:main:, row:10, col:79))
    (Data Collect may fail due to missing templates)
    Do you still want to proceed ? (Setup operations may fail due to warnings above)
    when I check the xml-templates, at the mentioned row, there's the database-information: it shows "9.00.3068#" (a binary value, instead of #)
    when I check the database in SMSY there's "9.00.3068#" in version as well, I can't change it there manually, because datasource is TMS/RFC.
    In SLD the Version vor the database is displayed correct: 9.00.3068 (without #).
    Where does the # occur & how to delete it? How can we setup managed systems without the warning?
    kr, achim

    Just came across this issue and this snote fixed it.
    Note 1156714 - Failure to push XML templates during Diagnostics Setup

  • Error while running the diagnositc system setup wizard

    Hello All,
    When I am running the diagnstics setup wizard,I am getting the following warning for SSO.SMD is the SID for my solution manager system and it is ABAP+JAVA system:
    SSO Setup : both Java and Abap stacks are using a ticket certificate with identical DN : 'CN=SMD'
    SSO will not work with such add-in configurations. Please refer to Details below for manual actions to be taken, and run this setup step again.
    Step SSO Details
    Either the Java ticket certificate or the Abap ticket certificate of the managing system (ABAP Host=localhost sys=01 client=200) must be deleted and re-created, using a Subject DN other than 'CN=SMD'
    For ABAP stack : please use transaction STRUSTSSO2 to delete the system PSE, and recreate the PSE Own Certificate with a different name (NB : this will destroy any existing SSO Setup on ABAP side)Or, for Java stack : please refer to SAP Note 701205, section 'J2EE', third bullet and note attachments (ReplacingPublicKey.pdf) for doing it on Java stack
    Also I am getting an error:
    The upgrader doesnt run,it says the SMD upgrader will be run
    What does this mean
    Please help
    Rohit

    Thanks Jagan
    I have run upgrader as u mentioned here
    Just needed to confirm
    Well I will correct the SSO as u mentioned,Thanks
    Also I am getting an error for wily interscopy while I run the setup for managed system
    I will post that in a diferent post
    Thanks
    Rohit

  • 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.

  • How to install EASY DMS (Document Management System) setup in windows 7

    Dear Experts,
    Recently we have started a project to establish document management system in SAP. So, i have downloaded easydms7.1sp04 from the servicemarketplace service.sap.com/swdc and setup is successfully installed in windows Xp and unable to install successfully in windows 7.
    The SAP is upgraded in our company to release ERP6 EHP6.
    In windows Xp the DMS is accessing to all the systems in the landscape( DEV, QAS, PRD).
    But, In windows 7 it is only accessing the production system and if creating manually the systems prompting the error about RFC and hosts in windows 7.

    Hi Sir,
    As mentioned earlier it is prompting me the error
    Logon Failed (RFC_ERROR_LOGON_FAILURE)
    Name or Password is incorrect (repeat logon)
    But it is accessing only the production system in windows 7 but not all the 3 systems which are in landscape. I dont know how can it proceed to logon to the production system only with out other systems .
    Thanks in advance
    Regards,
    Easwar

  • Managed System Setup: SAP Router

    Hello!
    We are trying to execute managed system configuration for some sattelite system that we access over SAP Router.
    Which ports (inbound/outound) do we need to open in order to install Diagnostic Agent and connect it to Solution Manager?
    Thank you!

    Hello Alex,
    Please check this conversation External diagnostic agent   and note 1886060 - System Monitoring Setup for SAP Router.
    BR,

Maybe you are looking for