Plug-in status not performed in Managed system configuration

Dear Experts,
I had configured Managed system configuration in SolMan 7.1 SP10. I could  find plug-in status " not performed" (grey) in solman_setup screen . Below screenshot for your reference. I had highlighted the plug-in status in blue for easy recognition. Please provide your valuable inputs.
Thanks,
Phani.    

Hi Phani,
It is an open issue, pls see below; you might have to hang on till SP12 is available.
1954303 - The Plug-in Status (ST-A/PI) Grey for Managed System In Solution Manager SP10 and SP11.
A fix for this issue is planned for SP12, please note that this is subject to change
Regards,
Vivek

Similar Messages

  • 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

  • SolMan 7.1 SP10: Managed Systems Configuration: client 000 OK, client 100 error

    Hello,
    after installing SolMan 7.1 SP10 successfully I also completed the steps "System Preparation" and "Basic Configuration".
    Now I'm connecting the managed ABAP systems to the Solution Manager by performing step "Managed Systems Configuration".
    After several other ABAP systems I'm now connecting our productive CRM 7.0 EHP1 system "CM3" (SAP_BASIS 702).
    I also connected the CRM development and CRM quality assurance system without a problem.
    For client 000 everything worked fine, the RFC destinations were created and a green light is shown.
    Now the problem is to connect the productive client 100:
    The log for Activity RFC Connection says:
    The corresponding dev_rfc tracefile says:
    **** Trace file opened at 20140326 164911 W. Europe Standard Time, by disp+work
    **** Versions SAP-REL 720,0,523 RFC-VER U 3 1468763 MT-SL
    ======> Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)
    ABAP Programm: SAPLSM_SETUP_API (Transaction: )
    Called function module: FUNCTION_EXISTS
    User: SOLMAN_ADMIN (Client: 001)
    Destination: 0050568713C71ED3AD9FC4F78AC9D9EB (Handle: 16, DtConId: 27FEB4E356BCF14F99EB0050568713C7, DtConCnt: 1, ConvId: 64734943,{27FEB4E3-56BC-F14F-99EB-0050568713C7})
    EPP RootContextId: 0050568713C71ED3AD9FB7AD4C4859EB, ConnectionId: 0050568713C71ED3AD9FB784232C59EB, ConnectionCnt: 1
    EPP TransactionId: BDFDB4E3626AF14899EB0050568713C7
    But both users taken to execute this step (SAP Solution Manager Administrator "SOLMAN_ADMIN" and Managed System Configuration User "SM_ADMIN_SM3") exist and have the correct provided password.
    Does anyone have a clue?
    Kind regards
    Rüdiger Höckel

    Hello Ranjith,
    thanks for your quick response.
    The ST-A/PI software component is the same on all systems: 01Q_700 #2.
    SolMan system: SM3
    CRM systems: CM0 (ok), CM1 (ok), CM3 (problem with client 100, client 000 OK).
    I also tried the recommendation found in the SAP Community Network
    (http://scn.sap.com/thread/3483642) but this didn't help either:
    1.Delete system from LMDB.
    2.Delete system from SLD of solman.
    3.Re- register the system to SLD of solman(rz70 for AS ABAP)
    [the LMDB synchronizes with the SLD every 10 minutes, system CM3 is visible again in the LMDB]
    4.Now follow the steps in managed system configuration.
    The wizard worked fine for client 000 but throws this error for client 100.
    I use all the latest installation and configuration guides.
    For this step I'm using the guide "Managed System Configuration" that is available in the SOLMAN_SETUP wiki.
    https://websmp206.sap-ag.de/~sapidb/011000358700001120342013E.pdf
    Kind regards
    Rüdiger
    P.S. In total I have already connected eight systems (SAP_BASIS 700 to 731) but this is the first system that gives an error.

  • I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

    I can not make a "Byte Code Adapter Installation"
    When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
    Please help to resolve a number of questions that might help me complete the setup :
    1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
    I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
    2 . Why Server Node is empty detail settings ?
    JDK Location: 
    Enterprise Manager Host: 
    Enterprise Manager Port: 
    Introscope Agent Name: 
    Introscope Agent Profile: 
    Autoprobe Directives: 
    Wily Version: 
    Introscope Agent Version: 
    Introscope Agent Log Location:
    3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
    And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
    Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
    there is such an item:
    2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
    However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

    The problem was resolved a small manipulation - on stage Basic Configuration,
    point 3 "Configure CA Introscope"
    I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
    Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
    Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

  • DSM service is not deployed in managed system

    Hi pros,
    in our system landscape, we installed DSM&BRFplus instance and multiple SAP ECC systems. The purpose is to use DSM to deploy BRFplus services to managed systems. However,
    When deploying BFFplus functionsto a managed system via DSM. Although in DSM it says the function has been deployed successfully. But when checking in the managed system (via program "FDT_GENERATION_TOOL"), no functions were generated.
    As a result, in the managed system I can not use API to invoke any BRFplus service. Can anyone help on this? I have checked RFC destination setup and added managed systems.
    thanks

    Hi Nisha/Vikram,
    Thanks for your reply. I have executed above command as per the note 1907909.But again I am able to find the agent when I am executing step4 of managed system configuration (assign diag agant). I checked the error log in agent admin and I could find below error.
    CIM_ERR_FAILED: User credentials are invalid or user is denied access <WBEMHttpRequestSender.java:398:newCommunicationException()>
    For this I found that "slddsuser" is getting locked time and again.I am not aware as why this user id is getting locked repetitively.
    Incorrect client ID. The stub is not connected yet.
    Nested exception
    is:
    com.sap.engine.services.rmi_p4.P4IOException: Cannot make connection.
    <P4ObjectBrokerClientImpl.java:726:getException()>
    Unexpected exception.
    Nested exception is:
    com.sap.engine.services.rmi_p4.P4IOException: InterruptedException while
    waiting fot the message.
    <P4ObjectBrokerClientImpl.java:739:getException()>
    Diagnostics agent is not connected to solution manager server,
    connection status: DISCONNECTED
    <SMDJNDILookupAgentSideImplementation.java:120:_lookup()>
    Object not found in lookup of SMD_DataEnrichment_Registrator.
    <ServerContextImpl.java:652:lookup()>
    No
    connection with the server. <ClientContext.java:2835:close()>
    Please Suggest
    Thanks
    Aditya Roushan

  • Software Prerequisites in managed system configuration are not fulfilled

    Hello dear Forum,
    I'm facing a problem when I configure a PI system in managed system configuration. I register the  Netweaver PI AS ABAP technical system to solman's SLD directly(run RZ70), and collect the information of the Netweaver PI AS JAVA from the PI's sld. I don't know whether it matters.
    The following error occurs when I Check Prerequisites:
                   J2EE-FRMW does not fulfill the prerequisites (installed: 7.11 SP0, expected: 7.11 SP001)
    But I don't know how to find J2EE-FRMW 7.11 SP001 and do some update, please give me some advice.
    Best regards and thanks for your help,
    Pany

    Hi Pany,
    Steps to follow
    - Rename the J2EEFRMW01_5-20002637.zip file to J2EEFRMW01_5-20002637.SCA.
    -telnet localhost 5$$08
    -logon with the user administrator
    - deploy /software/j2eefrmwpatch/J2EEFRMW01_5-20002637.SCA version_rule=all
    - Once it is done , then trigger the data to the SLD
    - Checked the software component in SLD
    - Resync the LMDB with SLD
    - Then performed the activity of manage system Configuration.
    With Regards
    Ashutosh Chaturvedi

  • Solman_setup - Managed System Configuration - ST-PI plugin not up-to-date

    Hi,
    I have a problem with configuring managed systems in Solution manager using txn solman_setup. When I select the managed system, enter all the data for the READ destination, TMW destination and Back destination and click "Maintain Connection" the system comes back with message:
    ST-PI Plugin not up-to-date for managed system IVE, see note 1274287
    When I check the OSS note and my managed system I see that my managed system is already on the right required level for SAP Solution Tools Plug-In which is: ST-PI 2008_1_700.
    I did check also for service packs but these do not yet exist.
    Can someone help me with this issue?
    Next list shows current version of the managed systems:
    SAP ECC 6.0
    SAP ABA 700 Sp 13
    SAP Basis 700 SP13
    St-PI 2008_1_700 SP 0
    PI-Basis 2005_1_700 SP 13
    SAP BW 700 SP 15
    SAP AP 700 SP9
    ST-A/PI 01l_ECC600 SP 0

    I did finally resolve my problem with input from OS which is listed below.
    You're using the latest version of ST-PI. There's no patch levels
    available to download in this moment. To solve this issue I ask you to
    first apply the latest version of this note below. Please, read
    carefully step by step this note below and follow all the procedures.
    Number 1172948
    Short text SAP Solution Manager - Basic functions
    After you applied the central note, I ask you to apply these notes belowWhen you had all these notes applied, this issue will be solved.
    Number 1274287
    Short text End-to-End Diagnostics SP18
    Number 1244225
    Short text Solution Manager 7.0 EhP 1: recommended
    corrections
    Please, apply the latest patch level for lmservice too.

  • System service not activate in managed system

    Hello,
    I am implementing SAP Solution Manager Diagnostics.
    1. I am working in Phase 3 - Managed System Configuration
    2. Connect Managed system.
    When I start this step, I get this error :
    Please import the actual support package for SAP_BASIS or activate the service 'SYSTEM' manually.
    I am configuring XDS system which runs with SP13.
    The "SYSTEM" services is already activated in the managed system (XDS).
    Thanks for your help.
    Best regards
    P. Cuennet

    Thanks Ruediger !
    I have already implemented OSS Note 1172948.
    I will apply correction of OSS Note 1309047.
    Another question regarding the Extractor Framework (SMD - Extractor Framework Administration) :
    1. Can you create your own Extractor ?
    2. Does the Extractor depends on the SAP product ?
        Example :  Do I have specific extractor for BI systems and other for PI systems ?
    Thanks in advance for your feedback
    Best regards
    P. Cuennet

  • Managed System Configuration ! The table does not contain any data !

    Hi,
    In Sol Man Setup , Managed System Configuration, in phase 6 - Create Logical Componets -
    There is no Product Version and Product Instance Available.
    The message is :  " The table does not contain any data "
    How can correct this problem ?
    Thanks

    Hi,
    while creating new Logical Component via SMSY , you need to specify Product first.
    e.g. if you managed system is ERP 6.0 , select Product as SAP ERP
    once you select Product , it automatically fetches information for product Version and Main Instance depending upon Product field input.
    Please check and let us know if issue still persits.
    Thanks,
    Rupali

  • Managed System Configuration - Software version and OS is not accepting

    Dear
    When i try to setup the PI system in solman 7.1 - Managed system configuration, below the error msg.
    Please help to sort it the problem
    Regards
    Jay

    Hi Pany,
    Steps to follow
    - Rename the J2EEFRMW01_5-20002637.zip file to J2EEFRMW01_5-20002637.SCA.
    -telnet localhost 5$$08
    -logon with the user administrator
    - deploy /software/j2eefrmwpatch/J2EEFRMW01_5-20002637.SCA version_rule=all
    - Once it is done , then trigger the data to the SLD
    - Checked the software component in SLD
    - Resync the LMDB with SLD
    - Then performed the activity of manage system Configuration.
    With Regards
    Ashutosh Chaturvedi

  • Technical Systems Not appearing  in Managed Sytem Configuration

    Hi Experts,
    I am doing Solman_setup after upgrade.I am in Managed system configuration step.I have synchronized Abap and java systems through RZ70 and NWA respectively to Solamn Local SLD and hence they are also appearing in LMDB (technical system tab).However when I am opening Managed System Configuration page  no technical system (Abap or Java) is   found (except solman Abap and solman Java) technical system tab page (find the screen shot for ur convenience ).Can any one help me out to find the solution.
    Thanks
    Aditya Roushan

    Hi
    Please check the Synchronization job  between SLD and LMDB is running fine.
    Did you finish all the steps(SLD Setup) System Preparation?
    If the issue still exist please de actviate the SLD and recreate again
    Run the SLD and LMDB Sync job again after the recreation Step: SLD Setup
    Kind Regards,
    Phaneendra Kakani

  • Managed system Configuration : The JMX metrics of this Host / Byte Code Adapter are missing

    Hi Friends
    While Configuring EP system with SOLMAN 7.1 SP12 it is giving below message in self Diagnosis Phase.
    1. Solman system is already having ISAGENT version 8 and 9 installed (but Managed system is having 8)
    2. I have followed the automatic Process as below
    ==========================================
    Automated Installation of the Introscope Agent via SMD
    The Solution Manager provides an application that performs the setup of the Introscope
    byte code agent for Java automatically. This section explains the steps to run the setup.
    Before you can run the Introscope agent setup, the setup wizard for the managed system
    must have been executed.
    1.
    2.
    3.
    4. Launch the Introscope Setup application: SAP Solution Manager Configuration 
    Managed Systems Configuration  Step 7 Configure Automatically  Automatic
    Activity “Byte Code Adapter Installation”  “Open Java URL” (only available in edit
    mode). Your screen will look similar to the image below:
    5. Check the Enterprise Manager Settings at the top of the screen. These are the
    connection parameters that will be used by the agent to connect to the Enterprise
    Manager.
    6. In the pane Introscope Agent Setttings, select the system that you want to instrument
    with the agent. Check “select all” and click “Retrieve Current Settings”. This will display
    the current status of the agent setup.
    7. To initially setup or update the agents, click Setup Introscope Agent …. This will open
    the setup dialog as shown below. Select the desired agent version (by default only one
    available) and choose the profile. Next, check the desired instrumentation areas, and,
    in the case of AIX, review the AIX settings to match your environment (J9 or classic
    mode).
    8. Finally, hit Apply to perform the necessary changes in the agent configuration. Agent
    config files will be adapted and the Java VM parameters will be set as required for the
    managed system.
    ================================================================
    3. Restarted SAP but error still present.
    Please help to resolve the issue.
    Thanks

    Found the solution :
    1819577 - Workload Analysis data missing for Java systems when using ISAGENT 8.2.4.0
    Cause
    l This issue has been identified as product defect and documented in note 1273028
    Resolution
    l As mentioned in note 1273028, update to ISAGENT 8.2.4 Patch 1 timestamp: 2012-06-26, please proceed as described below)
    1. Enable the Maintenance Mode in the Agent Administration UI (http://solmanserver:port/smd/AgentAdmin)
    2. Deploy the file to the Solution Manager JAVA stack using the Software Deployment Manager (SDM)
    3. Disable the Maintenance Mode in the Agent Administration
    4. Execute again the activity 'Byte Code Adapter Installation' of the step 'Configure Automatically' in the 'Managed System Configuration' for the
    affected systems. This activity will deploy the new version of the
    Introscope JAVA agent in the managed system servers and reconfigure the JVM parameters to use the new version of Introscope JAVA
    Agent;
    5. Check from Introscope Agent Admin if "IS Agent State" contains value "Running but needs restart"
    6. Restart the affected managed system(s)
    Finally Solution is update your SOLMAN system patch ISAGENT 8.2.4.0 from patch 0 to 1 via SDM.
    Thanks
    Mukesh

  • Warnings in Managed System Configuration

    Dear all,
    We are in the process of connecting a satellite system to Solman 7.1 and to monitor its datas.
    So in Managed system configuration for system, we are facing some warnings in step 8 and step 11.
    In step 8(Configure Automatically),Generate System level metrics ended with a warning i.e "The Diagnostic Agent for Introscope Enterprise manager could not be found"
    In step 11,(Configuration),Configuration check ended with warnings.
    i.e Errors found during the last 20 run for extractor
    Kindly suggest on how to proceed further.
    Thanks,
    Regards,
    Hasan

    Hello Diego,
    Sorry for the late reply..
    Yea the Enterprise Manager is running.
    When i tried the URL which you had given, it is displaying as 404 not found.
    Also when i start the Diagnostic agent in the SOLMAN, it is getting started and it is showing green LED in MMC, but when I try to connect the Diagnostic Agent to Solman in Basic configuration step, it is turning yellow and displays as,
    ""Access denied by the Managing System
    Check username/password
    Managing System details:
    host hllsap12
    port 8103
    Last operational status 272"
    After this the Diagnostic agent turns to yellow in MMC also..
    Kindly advice,
    Thank You,
    Regards,
    Hasan

  • Managed system configuration, step:Check Prerequisites

    hi firends,
    We've updated our SLM system up to SP13 and import finished success.
    When we starts managed system conf from menu SOLMAN_SETUP - Managed System Configuration - Configure System - Check Prerequisites, execution return error that system prerequisites are not fullfilled.
    But from menu Status all SP's are correct
    Additionally screenshot added to attachment
    please help me to resolve this problem.
    P.S. all other steps in Managed system conf wizard finished Success.
    Thanks in advance
    Shahin

    Hi Matthias,
    Please review SAP Note 1571442 as it might be helpful in resolving this error message.

  • Managed System Configuration Error for MDM 7.1 SP09

    Greetings, Needed your expert advise. We are getting an error while configuring our MDM Servers (Version 7.1.08.196) in Solution Manager. As suggested in SAP Note  1798643 , I have manually filled the required details and transferred through sldreg.exe to SLD. Now when i try to perform Managed System Configuration, it is throwing the below error. The definition of Technical System '~MDM' is not correct: '~MDM': No Path found in Installed Technical System 'SID~MDM~'. I'm not sure how to manually update the Install Path for our MDM Servers. Since, the data to LMDB is automatically supplied, I might not be able to manually edit anything. Could you please advise if there is any step to solve this issue. Thanks, Haseeb Ahmed.

    Dear ,
    Haseeb,
    I had the exact same problem with MDM managed system setup . I was on MDM 7.1 SP10.
    1940337 - RCA template for Solution Manager 7.10 SP10
    This note should resolve your problem. This note has the updated template for MDM.
    It did for mine
    Thanks
    Amit

Maybe you are looking for