Early Morning Page (daily) for managed systems

Hello!
We are using the newest SAP Solution Manager 7.1 and would like to automatically generate
a Early Morning Page (daily report) for all the managed systems.
Of great interest is the following content in this Early Morning page:
- introduction/comment/own text
- growth of database/file systems and history of previous week
- Dialog response time and history of previous week
- amount of short dumps
Does SAP Solution Manager7.1 provide this service or there are some other tools that can fulfill our requirements?

Tailored SLR. This sounds good.
To my knowledge you can generate SLR monthly or weekly.
What I need:
an automatic short daily report with the status symbol and all the important KPI values like DB growth, response time, etc.
Thank you!

Similar Messages

  • Solution Manager - EarlyWatch Alert shows red flag for managed system.

    Hi Guys,
    I tried to fix EarlyWatch alert report for Managed systems of QA and Dev which showed red flag on SolMan in DSWP. While trying to generate BACK RFC Destination to SolMan for QA and Dev, it messed up the EarlyWatch alert reports of Prod which was successfully working upto this point. And now the red flag appears for Prod system on SolMan in DSWP instead of two bottle sign.
    As for why Dev and QA did not work, I found out it was NONE internal RFC popped whenever I tried to choose the RFC to connect to SolMan while Prod which was working fine before always showed BACK rfc. That's why I tried to fix BACK rfc for Dev and QA.
    Please help me to fix these EWA problems.
    Thanks,
    Modena

    Hi Modena,
    Please see the link below for this specific issue:
    http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=228262728

  • Error in code page mapping for Source system whil loading the data from ECC

    HI Gurus,
    I am working in a implementation project, Recently our BI sand box is up, when i am doing my load from 0comp_code_attr it is throwing an error "Error in code page mapping for source system"(This is my first load from ECC).
    In details tab it is showing as the data is sent from the source system but the data is not reaching to the PSA.
    Please let me know if there are any settings needs to be made.
    Many thanks in Advance
    Jagadeesh

    HI V,
    Thanks for your quick response. I did it but it didn't resolve the issue. since the system id which i am having is 3 digits(LEC) but there it is taking only 2 digits, so i clicked on the button called Propose system ids, it has praposed LE, but the issue is stil there.
    Do we need to do any settings in LBWE??
    Thanks and Regards
    Jagadeesh

  • Error in code page mapping for Source System

    Hi All,
    We are Loading data into BI system from MDM System.
    It was loading fine but Yesterday we got an error " Error in code page mapping for Source System"
    Message Class: RSDS_ACCESS 13.
    We alreday tried to Search any IDOCs with error/unprocessed , but there isn't any.
    Any pointers for this error will be Helpful.
    Regards,
    Mayank

    Our SP currently SAPKW70019 , the SAP note mentioned above required to apply SP for 13, which we already beyond that...unfortunately we still face the same problem .. almost every day ..
    any advice.. ?
    Edited by: Edi Erwan  Abu Talib on Jun 22, 2009 8:22 AM

  • MAI for managed systems residing in separate network

    Hello!
    We are considering to implement the new Monitoring and Alerting Infrastructure (MAI) with Diagnostics Agents for our SAP systems. 
    The most of our SAP managed systems reside in separate network (differ from SOLMAN network).
    In order to retrieve CCMS-data from these systems we must use RFC connections within SAP router string.
    Has someone already successfully set up MAI for managed systems that reside in separate network?
    Of great interest are the information about
    1) Integration of these systems into DBACOCKPIT of SOLMAN
    2) Installation of Diagnostic Agent on remote host
    Many thanks for your information.

    Hello SAP-SDN,
    as for your initial question:
    Has someone already successfully set up MAI for managed systems that reside in separate network?
    Of great interest are the information about
    1) Integration of these systems into DBACOCKPIT of SOLMAN
    2) Installation of Diagnostic Agent on remote host
    1.- actually on process, but still don0t found any problem to do on remote network trought sapruter.
    2.- actually working and running, the unique limitation is the connection between willy hostagent and wily EM.
    as for your next question:
    1a) database related data in your Alerting (e.g. tablespaces)
    1b) database related data in your IT Performance Reporting/Interactive Reporting (e.g. growth of database)
    1c) DBACOCKPIT connection for the remote SAP system
    1a) for ewa ABAP you can get that information from a remote netwaork managed system without any problem
    1b) for ewa ABAP you can get that information from a remote netwaork managed system without any problem
    1c) still on process, but i think that can be possible as well is possible to connect the remote SMD diagnostic agent trought one or more saprouters.

  • Quick help - Is SAPHOSTAGENT Mandatory for managing system (solman) ?

    Hi All,
    Quick question, Is SAPHOSTAGENT Mandatory for managing system (solman) ?
    No data in infocube OSMD_PE2D (JAVA MEMORY USAGE) and i'm trying to narrow down the problem. Therefore, i want to know is SAPHOSTAGENT Mandatory for managing system (solman) ?
    Thanks,
    Nicholas Chang

    Hi All,
    I've figured out that DAA and SAPHOSTAGNET is needed for SOLMAN EHP1 SPS > 20 as the diagram depicted in AgentInstallation.pdf, from Note 1365123 - Installation of Diagnostics Agents.
    and i've resolved the problem where data is populated in OSMD_PE2D and JAVA MEMORY USAGE data and etc is appearing in WA and EWA.
    Step performed:
    1) before rerun diagnostic system setup, ensure RFC for SELF_DEST for BW source system is working fine and importantly, all field should be empty in technical settings, logon & security and etc. Perform RFC and authorization check.
    2) rerun diagnostic system setup and ensure all result returned green, and check CCMSBI_SETUP_E2E log. Ensure it completed successfully. ( you need to adjust WEBADMIN & SOLMANDIAG RFC by putting in the gateway host and port to avoid intermittent RFC error, also enlarge RFC resource in table E2E resources)
    3) go to TX rstco_admin and ensure status is activation successful.
    4) follow sapnote 1259109 and upload the latest xml according to your solman version.
    5) Install object accordingly by following note 1342231 & 1110013 (the note specify the bugs happen in SPs18, whilst my solman version is EHP1 SPs27 and i was reluctant to apply at the first place. But upon checking, most of the objects mentioning in the note that required installed are not installed!)
    6) Rerun managed system setup
    7) Check infocube OSMD_PE2D after 1 hour or 1 day?? unsure as i checked after one day.
    Cheers,
    Thanks,
    Nicholas Chang.

  • Understanding and using Logical Components for Managed System configuration

    Experts.....
    I am embarking on a fresh installation of SolMan 7 EhP1 SPS25 and after a few bugs along the way, I am finally nearing the end of including the first Managed System.  Somewhat related to {forum:id=10293771] I am hoping I can get some advice, but specifically with regards to Logical Components.
    General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component.  I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B.  This seems wrong to me?
    I am at the last step of the managed systems configuration wizard : "create logical components" and only want to ensure that I set things up to hopefully ensure that later usages (Maintenance Optimizer, etc) will handle things correctly!!!
    - Our SAP landscape is not very complex
    1. only ERP and EP (Dev/Test/Prod). 
    2. We are utilizing HR Self Service (XSS).
    3. The ERP ABAP systems are on Netweaver 7.01. 
    4. EhP4 has been installed, however we only activated the HCM business functions.  Therefore SAP_HR is on 604 whereas SAP_APPL is on 600.  I think this might be driving some of the confusion in SMSY
    For the DEV ABAP system I am trying to configure:
    1. The system is showing up in two products : "SAP ERP" and "SAP ERP Enhancement Package" with the header data for both showing "EHP4 FOR SAP ERP 6.0 / NW7.01" and "SAP ERP 6.0"
    2. Under "SAP ERP" the "product instance selection" shows only "SAP NW - Adobe Docu. Service" and "SAP ECC Server" as relevant
    3. Under ""SAP ERP Enhancement Package" the "product instance selection" shows only "Human Capital Mgmt" as relevant by default.  I manually flagged the development portal system as "relevant" for "SAP XSS (Self Services)"
    4. The RCA DBA Cockpit system is complaining "No data available for extractor activation. Please check product mapping and Software Components in SMSY"
    5. In the Managed System wizard, there is no logical component for any of the "EHP4 FOR SAP ERP 6.0 / NW7.01" selections
    From what I can tell, I think this is correct:
    1. Create a Z_EHP4 logical component and assign the DEV/QAS/PRD systems to them
    2. Also assign the DEV/QAS/PRD to the existing SAP logical component "SAP ERP ECC SERVER"???
    3. For the Solutions, my plan is to create
    a. Non-Production ERP : with the dev/test erp/ep systems, but test system as the leading system
    b. Production ERP with the prod erp/ep systems only
    Thanks for any advice/guidance to help me avoid future problems!!
    Edited by: Eric Poellinger on Jun 15, 2011 6:32 PM

    General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
    Client 100 could be assigned to any number of logical components, client 200 could be assigned to those same ones or none of them. A logical component is just a grouping of systems used to accomplish some task in SolMan.
    For example with ChaRM you could have 2 logical components.
    ZCHARM_DEV development (100) -> QA (200) -> prod (300)
    ZCHARM_SEC security (900) -> QA (200) -> prod(300)
    One is used to show the path for moving development changes to prod, the other for security changes. 200 belongs to both, but 100 only to one.
    Set them up in whatever way meets you needs. It looks like for you, you could just use the default one and assign your clients to the various system roles. Not all functionality in SolMan uses the logical components though.

  • Metrics of EWA for managed system are in gray

    Dear All,
    We have solman7.1, system configuration and basic configuration are all successfully, we have a managed system, the Managed system configuration are successfully, in system monitoring, we see all EWA metrics are in gray.
    but EWA report was generated successfully.
    Could you please advise what could be the cause and how can i fix this gray issue?  Thanks.

    Hi,
    Please bear in mind that EWA metrics are collected only once per week ususally on a Monday so you could check today and see if the metrics are being collected? If not you could check if the data provider delivers data or not using the E2E_DPC_GET_DATA_CHECK program.
    Kind regards,
    Roland

  • Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

    Hi Folks,
    While doing Managed System Configuration for Soman system i am getting error in SSO Setup
    Currently I am in
    8. Configure Automatically :Single Sign On Setup
    This is i am going for managed System (Solution Manager System Itself)
    Below is error log..
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    Screen shot attached.
    Found SID for SSO ACL entry : SMP
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
    The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Exception
    java.rmi.RemoteException: Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:331)
    at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
    at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
    ... 8 more
    Regards,
    San

    Hi Sandeep,
    It seems authorization issue. Please check the below SAP Note :
    1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
    Hope this helps.
    Thanks & Regards,
    Nisha

  • Not find EWA Session in the managed system

    Hi all,
    I am configuring SOL 7.1 for EWA.
    I have configured SDCCN both on Solution manager 7.1 and Managed System.
    In the solution manager, i can find EWA session for managed system.
    The question is : When i run "Refresh sessions" on the T-code: SDCCN of Managed system, it can not retrive EWA session where exist on the Solution manager.
    How do i do? Can someone help, please.
    BR
    Wu

    after reconfiguration in new client,
    Follow Note 727998 - Complete Replacement of Service Definitions for SDCC/SDCCN
    step 1 :
    in the solution manager:
    1.1 run report  BDL_DELETE_ALL_TABLES in SE38
    1.2 SDCCN-> Goto -> Settings -> Task specific -> RFC destinations.
           Ensure that connection 'NONE' and SDCC_OSS is maintained, and that the 'master'
    1.3 Execute a "service definition refresh" in SDCCN
    1.4 Delete any task 'Maintenance Package' in the 'To do' tab in SDCCN.
    1.5 Create a new periodic task 'Maintenance Package' in SDCCN
    1.6 Call function module /BDL/_GENERATE_LOGFUNCINCLUDES in SE37
            Assign the value 'ALL' to the import parameter 'OPTION' (keep the default values for all other parameters) and execute the module.
    1.7 Execute "refresh session" in SDCCN
    step 2:
    in the managed system:
    1.1 run report  BDL_DELETE_ALL_TABLES in SE38
    1.2 SDCCN-> Goto -> Settings -> Task specific -> RFC destinations.
           Ensure that only connection SM_<SOL>_BACK' (delete SDCC_OSS )is maintained, and that the 'master'
    1.3 Execute a "service definition refresh" in SDCCN
    1.4 Delete any task 'Maintenance Package' in the 'To do' tab in SDCCN.
    1.5 Create a new periodic task 'Maintenance Package' in SDCCN
    1.6 Call function module /BDL/_GENERATE_LOGFUNCINCLUDES in SE37
            Assign the value 'ALL' to the import parameter 'OPTION' (keep the default values for all other parameters) and execute the module.
    1.7 Execute "refresh session" in SDCCN
    Best Regards,
    Wu

  • Error in codepage mapping for source system. Error text:

    guyz,
    im facing the below issue in prod.
    Error in codepage mapping for source system. Error text:
    Message no. RSDS_ACCESS013
    Collection in source system ended
    Error message during processing in BI
    Diagnosis
    An error occurred in BI while processing the data. The error is documented in an error message.
    System Response
    A caller 01, 02 or equal to or greater than 20 contains an error meesage.
    Further analysis:
    The error message(s) was (were) sent by:
    Inbound Processing
    Procedure
    Check the error message (pushbutton below the text).
    Select the message in the message dialog box, and look at the long text for further information.
    Follow the instructions in the message.
    need your guidance,
    cheerz,
    raps.
    Edited by: raps on Mar 1, 2012 9:39 AM

    Hi ,
    Kindly go throught the following threads for your issue resolution::
    Error in code page mapping for Source System
    Erroe in source system
    Regards,
    Arpit

  • 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

    Dear Team,
    While doing managed system configuration for AS JAVA system (only used for BI JAVA) we are getting error as "Solman System prerequisite are not met" ST-A/PI 01P_700 is not installed.
    When Checked in Solman system ; However the ST-A/PI is higher version than what is asked for. It has version of ST-A/PI 01R_700.
    Our solman is at 7.1 SPS 08
    Please suggest how to go ahead.
    Regards,
    King Arthur

    Dear Divyanshu,
    I have done managed system configuration for ABAP only stack on  NW 7.01 ECC and it went successful.
    However at that time my ST-A/PI was on lower version than ST-A/PI 01R_700 (i.e. somewhere on P or Q version)
    Now I am trying to do for Managed system which is Only JAVA stack....and is based on NW 7.41.

  • 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

  • Configuration of EWA reports for java systems.

    Hello,
    I am facing a problem with configuration of EWA reports for SAP NW Portal.
    I have already configured EWA for abap systems, and those are running good on weekly basis. but i have problem with configuration of reports for java systems.
    So far, i have installed an SMD agent and CA on my EP-satellite system. I have also configured and SMD server on my Sollution Manager and registered the SMD agent on SMD server and installed Willy Introscope on SMD server.
    I  am using a central SLD which is running on different host as Solution Manager. I did all the configuration (smsy_setup, configuration of sld_data_supplier etc... )
    I have also created the system in SMSY, matched the smsy with SLD and assigned Logical component to java system.
    So far, so good according to manuals but when i  want do define data collection in the SMD for Gargage Collection  (task in scheduler) i cannot see host of my portal system.
    I can see only the hosts (scheduler tasks ) of all abap system for which the EWA reports have already been  generated.
    Am i missing something?
    Some configuration in SMD?
    My solution manager is running on Sap NW 7.0, SPS16,
    Sattelite system  NW 7.0 EP, SPS 6 (planning to SPS 19)
    Thank you for your advices!!!

    Hi Suveer,
    I did the configuration before. I forgot to mention it.
    I found this errors in Diagnostic Setup, maybe this could be the cause of the issue.
    Step BI Details
    Cannot invoke CCMSBISETUP on host localhost
    !! Exception : An exception occured during the execution of this function 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC'.(cause=com.sap.sup.admin.abap.rfc.exception.RfcExecutionException The function named 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC' doesn't exist!)
    Exceptions
    com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: An exception occured during the execution of this function 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC'.
    at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:92)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.setupBIConfiguration_ccmsBiSetup(AbapSysRfcAdapter.java:743)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.setupBIConfiguration_ccmsBiSetup(AbapSysRfcAdapter.java:727)
    at com.sap.sup.admin.setup.ManagingServices.startCcmsBiSetup(ManagingServices.java:2686)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:334)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.setupSMDServer(ConfirmationView.java:378)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.onActionSetupServer(ConfirmationView.java:211)
    at com.sap.sup.admin.setup.wizard.monitoring.wdp.InternalConfirmationView.wdInvokeEventHandler(InternalConfirmationView.java:278)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: The function named 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC' doesn't exist!
    at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:62)
    ... 37 more
    And also this one>>
    Step RFC Details
    Failed to create TCP/IP RFC on ABAP side (SM59)
    !! Exception :      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE
    Exceptions
    com.sap.aii.proxy.framework.core.BaseProxyException:      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE
    at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
    at com.sap.sup.admin.setup.abapproxy.tcpiprfc.TcpIpRfcProxy_PortType.inst_Create_Tcpip_Rfcdest(TcpIpRfcProxy_PortType.java:16)
    at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:663)
    at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:637)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:300)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.setupSMDServer(ConfirmationView.java:378)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.onActionSetupServer(ConfirmationView.java:211)
    at com.sap.sup.admin.setup.wizard.monitoring.wdp.InternalConfirmationView.wdInvokeEventHandler(InternalConfirmationView.java:278)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    And in the troubleshooting setup for managed systems, i can see that no initial upload was found form the SMD agent which is running on Java System.
    Thanks a lot for your remarks

Maybe you are looking for