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.

Similar Messages

  • 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

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

  • 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

  • Error in Managed system configuration.

    Hi Folks,
    In Solman 7.1 i am configuring my Java system in managed system configuration on the last phase of configuration which is "Check Configuration" i got the below error...
    Can any one guide me on this....
    I installed the Diagnostic agent as well as willy inter scope.
    Regards,
    Anil.

    check the note which describes your problem
    1776959 - Solution Manager 7.1 Manged System configuration. Error: Timezone from managed system could not be retrieved: Timezone of J2EE Engine (GMT+01:00) does not match the timezone of the diagnostics agent (Europe/Berlin)
    Resolution
    Open the instance.properties file of the J2EE Engine on the managed system
    Locate the parameter "-Duser.timezone=" and its value
    If the -Duser.timezone is not set the JVM uses GMT
    Set the -Duser.timezone parameter in the JVM of the SMD Agent. If there was no "-Duser.timezone in the J2EE's instance.properties file use the timezone that was indicated in the error message e.g. GMT+01:00 (from the above error message, this might differ on your environment) To do this:
    Locate the smd.properties file (for newer agents the files is called: smdagent.properties)
    The path is: .../usr/sap/<DiagnosticAgentSID>/SMDA<SYSNumber>/SMDAgent/smdagent.properties
    The -Duser.timezone= parameter of the Diagnostics Agent and the SAP J2EE engine need to be set to the same timezone. That means the string needs to be the same for both parameters
    e.g.
    If the -Duser.timezone= parameter of the J2EE engine is set to -Duser.timezone="GMT+01:00"
    set the Diagnostics Agent parameter to:
    smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m -Duser.timezone="GMT+01:00"
    Restart the Agent
    Re-run the "Configuration Check" in the "Managed System Configuration"
    Please make sure that the time zone configuration is correct according to the SAP recommendations: http://wiki.sdn.sap.com/wiki/display/Basis/Timezone+changes+best+practices

  • Syntax error in program CL_AC_METRIC_REPOSITORY=======CP When going to managed system configuration in solman 7.1

    Dear SAP Gurus,
    Good Morning.
    I'm getting error in managed system configuration in solman 7.1. Error is like
    The system preparation and Basic configuration in working fine, but when we are going to click the managed system configuration Error getting like this.
    Solution Manager  Version : 7.1
    SP Level  : SP5
    Thanks in Advance.
    Regrads,
    Kumar BN

    Hello Kumar,
    I would suggest moving this discussion to this space in SCN: http://scn.sap.com/community/it-management/alm/solution-manager
    That will help get you a quicker response.
    Thank you,
    Kristen

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

  • Managed System Configuration - PI7.1 system solman_setup

    HI all,
    In trying to execute the step "Managed System Configuration" for a PI7.1 system in Solution Manager SOLMAN_SETUP, in the first step to "maintain the connection", its failing immediately with:
    Error when opening an RFC connection
    Establish connection to System <hostname>(01) - <SID>_001
    Any ideas?
    Thanks, Neeta

    Hello Neeta,
    i face the same problem.
    Establish connection to System <hostname>(01) - <SID>_001
    / CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=726 Gateway ist not connected to the l...
    i check the following and they are all fine.
    - ping to PI from solman
    - PI IP address in SMSY
    Could you tell me which part you configured in SMSY?
    regards

  • SOLMAN_SETUP - Managed System Configuration - DBA_COCKPIT

    Dear SAP Colleagues,
    I am currently implementing SMD in my Solution Manager system. I use the guided procedure SOLMAN_SETUP. The first 2 phases - Initial and Basic Configuration are completed.
    I have starting the 3rd one - Managed System Configuration - Manual Configuration.
    I have started the "Configure DBA Cockpit".
    I have no problem with most of my managed systems (ERP, BI, EP)..
    But when I want to configure the DBA cockpit for my PI systems, I get error.
    Even if I personnaly there is nothing to do with the SAP Product, I get an error when I want to configure my all 3 PI system in DBA Cockpit.
    1. I select the Managed System in my list
    . The DB Host Name is automatically filled out.
    . The DB Name is automatically filled out.
    . The Schema Name (Optional) is also automatically filled out.
    2. Then I click on Next button and I get this error :
    The DB connection is no successfully tested.
    Please make sure the parameters below are correct and hit ....
    Database Name : XDS
    Datbase host : xdsci
    TNS Name : ???
    User Name : SAPXDS
    Password : ???
    Question :
    1. From where (SLD or SMSY) these information (Database Name, Database Host, TNS Name ...)
        related to managed system XDS are uploaded ?
        In other terms, where are these technical information pre-configured ? In SLD ? In SMSY ?
    2. How may I fix this issue ? I did not configure the other managed system and it perfectly works.
    Thanks in advance for your help
    Best regards
    CP

    Hi,
    I found this OSS Note : 1265070
    You can also connect directly to this link :
    https://websmp207.sap-ag.de/~sapidb/011000358700000074392009E
    Best regards
    CP

  • SQL Error 0 during DBACockpit setup in Managed System Configuration

    Hi All,
    I'm getting SQL Error 0 during DBA Cockpit setup in Managed system configuration. I'm trying to connect MsSQL 2005 from Linux system(Solution Manager 7.1 SP10). I have installed necessary ODBC and microsoft drivers. Any suggestions will be appreciated.
    Regards,
    Pragadees

    If I've understood you correctly, you are trying to setup a remote database connection from an SAP Solution Manager system running on Linux with a database which is NOT MSSQL to a database which is MSSQL running on Windows.
    In that case have you checked these SAP notes ?
    1265134 - DBA Cockpit: Connecting a remote database
    1388700 - SolMan 7.0 EHP1 Database Warehouse for MSSQL
    Regards
    RB

  • Managed system configuration error

    Dear Expert,
    While doing managed system configuration step-"Check Configuration"  for my solman (7.1)system itself, I am  getting attached error.
    Please Advice .
    Thanks
    Chander

    Dear Oliver ,
    I have downloaded the Patch 183 (SAPHOSTAGENT183_183-20005735.SAR).
    Refering below link for upgrade http://help.sap.com/saphelp_nw73ehp1/helpdata/en/39/a1f623bae74a2784f88282c8652070/content.htm
    But after uncaring of Patch 183 ,I am not getting below files in new patch level .
    sapstartsrv.exe
    saposcol.exe
    saphostctrl.exe
    saphostexec.exe
    According to link the last file will be used in upgrade
    saphostexec.exe -upgrade
    but this is not present in new patch level 183.
    Thanks
    Chander

  • MAnaged system configuration error in solution manager

    Hi,
    While doing managed system configuration getting the error, below versions are using.
    MDM 7.1 SP10  Import server  and Solution manager 7.1 SP10.
    Can anyone help me?.
    Regards
    Chandra

    Two cases you have
    1) Satellite system
    Re-install The DIA agent and give correct (port numbers )SLD details
    Once you re-install the DIA agent, run Rz70 from satellite system
    data will pull from satellite system to central SLD.
    2)Run SLD check from Solman system , check its successful or not
    Go to LMDB and check satellite system
    After re-Synchronize technical system from SLD 
    Thanks ,
    Rahul yedapally

  • 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

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

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

Maybe you are looking for