SLD - Error in creation of technical system

hi experts,
when we go to create a new technical system type WEB AS ABAP, the system said 'system already exists'
it exist other technical system for this system of type third party,
don't is it possible have together?
very thanks,

Hi,
The problem is due to whatever technical system your are trying to create those details are  already contain another technical system name in SLD.  We can't create more then one technical system with same parameters.  Better to use existing technical system or delete existing one create new one.

Similar Messages

  • SLD configuration for DXI / PXI technical systems

    Hello,
    we have a problem when transporting XI configuration objects from XI dev to XI prod. The transport objects arrive in XI prod, but the name of the business system (for the SAP backend system) is not converted from dev business system (T01CLNT010) to prod business system (P01CLNT01) although the transport target for T01CLNT010 business system was set correctly (we are using business system groups Dev and Prod). And the "related integration server" for T01CLNT010 was also set correctly to DXICLNT010.
    But then I noticed that the technical system for the DXI (XI Dev) is configured as follows:
    TMS Domain ("DOMAIN_PXI") and TMS Transport Group Name GROUP_PXI ("GROUP_PXI") have the same values as PXI. Is that correct ?? We are using file transport, not CMS.
    Another strange effect is that when I set the group in business system DXICLNT010 to Dev, that is also applied to business system PXICLNT010 ! Which is of course not what I want.
    I assume I have to associate DXICLNT010 to Dev and PXICLNT010 to Prod, same as for T01CLNT010 / P01CLNT010. Correct ? Or does the group in the XI business systems not matter ?
    Can anyone post an example of a working SLD configuration with two XI system dev and prod ? What values do I have to use in the XI technical and business systems, so that the transport will work ?
    CSY

    There's obviously something wrong in the SLD configuration for the exchange infrastructure systems. The error you're describing (one system pointing to another) usually occurs when one system is generated through homogeneous system copy of another system (was that your case?). I've seen that behaviour once and they corrected it by manually deleting the exchange infrastructure systems from SLD and creating them again from scratch.
    Anyway, I highly recommend you to get an expert NW Basis consultant to realize a check in it before you proceed any further.
    Aside of that, you're correct in your assumptions.
    Your config in SLD should be like:
    DEV_GROUP:
    - DXI
    - T01
    PRD_GROUP:
    - PXI
    - P01
    It's always 1 XI BS per group.
    Also, if you use separate SLDs for XI Dev and XI Prd, you have to make sure that this configuration is reflected in both SLDs. So, if you make it one SLD instance, you must generate a delta export zip file from the SLD where you did the configuration and import this zip file in the other SLD instance.
    If you use a central SLD, then it's not necessary.
    Regards,
    Henrique.

  • Error in creation of source system

    Hi Experts,
    We are facing a problem while creation of source system. We are getting an error "You have no authorization for basic types (activity 03)" Kindly help me to resolve this issue.
    Regards,
    Jitendra

    Hi there,
    if you get the error again, please go tcode su53 directly and see for which object the authorization is missing. I understand you have SAP_ALL access but for any authorization issue we normally go to SU53 tcode and verfiy.
    So once you get the object name then go to SU01 and open your id. Go to authorization tab and find for that object and see if '03' activity is assigned to you or not.
    If this step is absolutely fine then we can think of alternative solution.
    Regards,
    Anup

  • Autmated creation of Technical system

    Hi Experts,
                      I am experiencing a strange phenomenon. In my PI dev server, I hav manually integrated BI dev server and R/3 server. There is no other server apart from these in the landscape.
        But everyday morning I get to see that the Technical system for teh BI production server along with all its clients being created sometime in the 3 am in the morning. I really don understand why is this happening. There is no RFC connection with the BI prod server,, no kind of connnection done taht i can remember.
        I am concerned as only 2 of us hav access to SLD , I wonder how is this Technical System getting created..
    Regards,
    Arnab.

    Hi,
    either you have a common SLD for PI dev and prod systems, so your BI prod technical system is appearing in your SLD...........
    but if you have local SLDs for dev and prd systems, then i guess that may be you have made a SLD bridge between your dev and prd systems to automatically synch the SLDs of these systems.
    Regards,
    Rajeev Gupta

  • Creation of technical system and business system

    Hi Guys,
    Im just a beginner in SAP XI..I would like to know what will be the setup in my SLD .
    My data will be coming from MS SQL and will transfer it to SAP R/3.
    Is it true that I need to setup the Technical system , one for my Sender (data coming from sql ) and
    one for my Receiver (data will transfer to SAP R/3).
    about the Business system? do i need to create buss system for Sender and receiver?
    Please help.
    Thanks in advance.
    aVaDuDz

    Hi,
    you don't have to create technical system for R/3 you should better use tcode RZ70 for selfregistering:
    The specified item was not found.
    And for this technical system you should create also a business system.
    You should create a technical and business system for your MS SQL if it's inside of your system landscape.
    Here is a good explanation:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/43/01ea90ab24235de10000000a1553f7/frameset.htm
    Regards
    Patrick
    Edited by: Patrick Koehnen on Oct 2, 2008 10:26 AM

  • Database tab is not filled in SLD after I create a technical system abap

    Hi guys,
    why is it? what do I have to set up to have this tab filled with valid values?
    Thank you
    Olian

    Hi,
    For technical system of type WebAS ABAP, you do not create it manually in SLD......instead its process is to log into R/3 system and run transaction RZ70 and from this transaction technical details of R/3 system are published to SLD of XI..........this is a basis activity and so you can ask your basis guys to do it for you...........then when it is done, then your Web AS system will be created in technical system in SLD with all the data filled properly.
    Regards,
    Rajeev Gupta

  • Doubt regarding creation of technical system.

    Hi i am doing interface between R3 and JDBC(third party)
    1)I  have created one technical system(type as web as abap) for R3 and one technical system(type as third party) for JDBC.
    2)but we usually download one software component in IR and we create namespace under downloaded software component(swc). we do create all objects for this interface is under this namespace.
    3)when we create technical system it will ask us install product, let us say we assign a prodocut called xyzr3 for Tecnical syste(TS r3), under this we have assigned a software componet(swc) called  xyzr3sw.
    4) when we create technical system for third party it will ask us to installed product, should i create new product for this technical system or do i need to assign a product xyzr3 witch is already created for R3 TS(tecnical system)?
    5)bcz we are using only one namespace for this interface whitch is created under xyzr3sw(sc of r3 ts, type as webase abap)
    6) let us say , we have created new product and swc for third party TS, any way we are not importing this sw component in IR, bcz we have imported xyzr3sw(sc of product, ts of r3), so do i need to assign same product xyzr3(witchi is creted for R3) , xyzrsw (swc created for R3) to ts (ts of type thired party)? bcz we are importing only one swc in IR to develop the interface(one name space)
    thanks,
    dhanush

    Hi Dhanush..
    4) when we create technical system for third party it will ask us to installed product, should i create new product for this technical system or do i need to assign a product xyzr3 witch is already created for R3 TS(tecnical system)?
    Yes. I think you should create new product here..
    6) let us say , we have created new product and swc for third party TS, any way we are not importing this sw component in IR, bcz we have imported xyzr3sw(sc of product, ts of r3), so do i need to assign same product xyzr3(witchi is creted for R3) , xyzrsw (swc created for R3) to ts (ts of type thired party)? bcz we are
    importing only one swc in IR to develop the interface(one name space)
    Yes. You do not need to import new software component version created for Third party.
    But I'll suggest here..since you want to use JDBC on the receiver side...you can just create Business Service ( where you do not have to specify technical details) and you can used as a receiving system. No need to create 3rd party here..
    Let me know if you need more details.
    Nilesh

  • What's different between busniess system and technical system in SLD?

    I can enter product(ect.ERP r/3) , components(ect.FI-CO module) to technical system , then enter technical system to busniess system  but ,who can explain  what's different between busniess system and technical system in SLD, exactly?
    THANKS!

    Technical Systems are of following types:
    Technical systems are application systems that are installed in your system landscape. An example of an application system is a Customer Relationship Management (CRM) server. In the SLD, there are five types of technical systems:
    1.)WEBas java,
    2.)Standalone JAVA
    3.)Third party
    4.)Web as ABAP
    1) Web AS Java
    Web AS Java systems consist of one or more instances and each instance is installed on a separate host. An instance itself consists of cluster nodes that can communicate with each other.
    2.)Standalone Java
    Standalone Java technical systems are standalone Java applications that are installed in a computer system from an administration perspective. They can also be installed as an operating system service or as a daemon
    Web AS java belongs to the NetWeaver Comes with both ABAP and Java, Standalone instread comes separate from the netWeaver.
    3) Third party technical sytem
    It can be any of the technical sytem. let us say if you want to send a file to R/3, here the file reside in your local system. for that you can define your local system as a third party technical system.
    All those machines that comes under non sap, belongs to the third party.
    4.) Web AS ABAP technical systems, ranging from any SAP system to an APO server or CRM server, are based on the same Basis Component (BC), which includes the ABAP interpreter, ABAP Dictionary, ABAP Workbench, and so on. A dedicated database, which stores most of the data of the BC and the application components, is associated with the system.
    Also refer : http://help.sap.com/saphelp_nw70/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
    Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems.
    Depending on the associated technical system, the following types of business systems are defined in the SLD:
    · Web AS ABAP
    A business system, which is associated with a Web AS ABAP.
    A business system, which is associated with a Web AS ABAP, can play the role either of an application system or an integration server. An integration server is the central component of XI, which provides a framework for the exchange of information among various internal and external entities of a company. The integration server facilitates the interaction between the different operating systems and applications across internal and external networks.
    · Web AS Java
    A business system, which is associated with a Web AS Java.
    · Standalone
    A business system, which is associated with a standalone Java application.
    · Third-party
    A business system, which is associated with a third-party technical system.
    http://help.sap.com/saphelp_nw70/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm

  • No ABAP technical systems in SMSY

    Hello,
    I've just set up a new Solution Manager Ehp1 and patched it to SPS23. In my SLD, I have two ABAP technical systems. However, I don't see them in SMSY. The associated product systems are present (one SAP ERP, the other SM itself).
    I've tried to schedule a fetch from the SLD in Setup System Landscape maintenance from the SMSY menu and it doesn't show any errors. In addition, per note 1468559, I've run SMSY_FETCH_SYSTEM_UPDATE for a single system. Returns success but no technical systems.
    If I try to create the technical systems manually in SMSY, there is no entry in the system type list for ABAP (I don't know if there should be or not, so even just confirming that it should exist would be helpful).
    Any ideas on what else I can check to solve this issue?
    Thanks.
    Rob

    Hi Rob,
    The technical system maintanence in SMSY is not relevant for ABAP systems.
    Technical system maintanence is required for non-ABAP systems like Java, TREX, MDM etc.
    Check the Landscape setup guide for more details:
    https://service.sap.com/~sapdownload/011000358700000074392009E/SP18_SolMan_Setup_Guide_V2.pdf
    Regards,
    Srikishan

  • Solman 7.1 LVSM Product system has no technical system assigned

    Hi All,
    As reference of blog #sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification  work in SOLMAN7.1SAPNetworkWeblogs%2528SAPNetworkWeblogs%2529
    I have created product instance from LSVM and now I have problem to add "product system" for Enterprise portal (using NW 7.3)  to the landscape, as its throw me an error "Product system has no technical system assigned".
    From the display help its mentioned:
    *Diagnosis*
    Product system is not assigned a technical system in the system landscape of the Solution Manager.
    *System Response*
    Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly assigned, many important functions are not available to you, or are only available on a restricted basis.
    *Procedure*
    Assign one or more technical systems to your product system . SAP recommends that you use the corresponding wizard of the Landscape Verification Tool. To start the wizard, choose the button Change Technical System Assignments next to the message. The user interface of the wizard contains detailed information about its usage.
    I'm not sure with sentence of Assign one or more technical systems to your product system and which wizard are this referring to ?
    I have also checked from the wiki:
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/MaintenanceofProductintheSystemLandscape#MaintenanceofProductintheSystemLandscape-EnterprisePortal
    And its only supported for NW 7.0 not 7.3.
    Is there anyone had this issues ?
    It's feels like I'm the only one stuck in this.
    Thanks in advanced.
    Raff

    Hi Sunny,
    Many thanks for your reply.
    I have followed the guide you mentioned, now I can see 2 EPD Error from LVSM.
    1. Product system EPD has no technical system assigned (new)
    2. Technical system EPD is not assigned to a product system
    For number 1. if I clicked on Change Technical System Assignments I can see EPD there, but when I want to add the EPD by clicking > I've got this error message " Newly linked technical system EPD has already been locked by user" I've tried to remove the lock from sm12 but nothing happen.
    For number 2. if I clicked on Change Product System Assignments, there is an error messages "Technical system EPD was updated in parallel session"
    I believe the number 1. coming because I create it from SMSY, but the number 2. is still there in the first place.
    Cheers,
    Raff

  • NW-Release of Technical System SID of managed system - is unidentifiable!

    Hi,
    Does anyone encountered this issue before when generating stack file?
    I am going to generate the stack file for SAP Enhancement Package 7 for SAP ERP 6.0 and SAP NetWeaver 7.4 
    but during phase 2.2 it pops up the error "NW-Release of Technical System <SID of managed system>- is unidentifiable!"
    I had read through note 1754904, but I could not found any SAP LiveCache under ERP system under SMSY.
    Thanks and regards,
    Shu Jie

    Hi Shu Jie,
    Please goto LMDB, then select technical system -> choose your system -> check the software field whether it has updated with the information of NW
    if not, please make sure you added the system in SLD and SLD sync with LMDB.
    please refer Landscape Management Database (LMDB) – FAQ and Troubleshooting for the LMDB - Managing System Landscape Information - SAP Library
    Thanks
    Jansi

  • Difference betweeen     Technical systems and Business systems

    Hi
    In a SLD we need to configure  technical systems and Business systems.. what is the exact difference between  Technical Systems and Business Systems..
    this question is asked an interview.. for this.. how can we explain..
    thanks
    babu

    Hi babu
    First I let u know with analogy and actual definition as below
    Any module of SAP like MM, SRM, FICO ets makes a logical system in combination according to business requirements is a business system which is actualy hosted on an  application server like ABAP AS or Java AS which is basically a technical system.
    Technical systems are application systems that are installed in system landscape (a CRM server, for example). Most systems (Web AS ABAP and Web AS Java systems) automatically report information to the SLD about the elements that they contain by using the SLD data supplier programs. You need to manually register the following types of system only:
    Standalone Java systems
    Third-party systems
    Business systems are logical senders or receivers that exchange messages by using SAP XI and that are entered in the System Landscape Directory.
    The business systems in the System Landscape Directory relate to a system landscape.
    The business systems of business partners are not entered in the System Landscape Directory. To be able to address such business partners logically, use services in the Integration Directory. A business system is a way of specifying a service in the Integration Directory more precisely (business system service).
    Reward point if it help u understand

  • Failed to retrieve technical system: QEM_NABP~JAVA

    Hi,
    I am configuring Solution manager Diag. with J2EE engine ( xEM system ). I executed tx.code solman_setup and then selected managed system configuration. Executed Diagnostic prerequisites and then received error Failed to retrieve technical system: QEM_NABP~JAVA
    Then I selected maintain technical system in related links but QEM system is maintained user Java system.
    Can you please let me know what would be the issue.
    Best Regards,
    Tushar.
    Edited by: TusharC Chavan on Nov 4, 2009 11:19 AM

    Hi,
    What worked for me:
    go to SMSY – Landscape Components – Product System (select system) – Product Instance Selection (tab) – (check) Technical System Assigment and fill in the “Technical system” and “System type” tab
    Best Regards,
    Catalin

  • Error while exporting the 3rd party technical system in SLD

    Dear all,
        We're currently using PI 7.0. When trying to export the technical system in SLD, after the exporting, the IE jumps to the download page automatically, but there's a exclamation mark with no text info. I've tried to create a new 3rd-party technical system and try to export, the same thing happened.
        It happened in both our develop and our production PI system.
        Also I've found following error info in SLD server log:
    Log Record Details
    #33 04/19/2007 10:07:38.573 [SAPEngine_Application_Thread[impl:3]_33]
    ERROR com.sap.sld.wd.technicalsystem.ExportView: null
    Thrown:
    java.lang.UnsupportedOperationException
    at java.util.AbstractCollection.add(AbstractCollection.java:216)
    at java.util.AbstractCollection.addAll(AbstractCollection.java:319)
    at
    com.sap.lcr.webui.admin.ImportExportControl.addAssociatorAndReferenceNames(ImportExportControl.java:1244)
    at com.sap.sld.wd.technicalsystem.ExportView.getBCSystemExportList
    (ExportView.java:285)
    at com.sap.sld.wd.technicalsystem.ExportView.getExport
    (ExportView.java:193)
    at com.sap.sld.wd.technicalsystem.wdp.InternalExportView.getExport
    (InternalExportView.java:137)
    at
    com.sap.sld.wd.technicalsystem.wdp.IPrivateExportView$IContextElement.wdGetObject(IPrivateExportView.java:208)
    at com.sap.tc.webdynpro.progmodel.context.AttributePointer.getObject
    (AttributePointer.java:158)
    at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat
    (DataContainer.java:1092)
    at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat
    (DataContainer.java:1064)
    at
    com.sap.tc.webdynpro.clientserver.uielib.standard.impl.FileDownload._getData(FileDownload.java:81)
    at
    com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.FileDownloadAdapter.getReference(FileDownloadAdapter.java:291)
    at com.sap.tc.ur.renderer.ie6.LinkRenderer.render(LinkRenderer.java:53)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutCellFragment(GridLayoutRenderer.java:826)
    at
    com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:424)
    at
    com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutFragment
    (GridLayoutRenderer.java:336)
    at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.render
    (GridLayoutRenderer.java:79)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at com.sap.tc.ur.renderer.ie6.GroupRenderer.renderGroupFragment
    (GroupRenderer.java:1184)
    at com.sap.tc.ur.renderer.ie6.GroupRenderer.render
    (GroupRenderer.java:74)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutItemFragment(FlowLayoutRenderer.java:254)
    at
    com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutFragment
    (FlowLayoutRenderer.java:210)
    at com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.render
    (FlowLayoutRenderer.java:49)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
    at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render
    (ScrollContainerRenderer.java:74)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
    at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render
    (ViewContainerRenderer.java:49)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutItemFragment(FlowLayoutRenderer.java:254)
    at
    com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutFragment
    (FlowLayoutRenderer.java:210)
    at com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.render
    (FlowLayoutRenderer.java:49)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
    at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render
    (ScrollContainerRenderer.java:74)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
    at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render
    (ViewContainerRenderer.java:49)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
    at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render
    (ViewContainerRenderer.java:49)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutCellFragment(GridLayoutRenderer.java:826)
    at
    com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:424)
    at
    com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutFragment
    (GridLayoutRenderer.java:336)
    at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.render
    (GridLayoutRenderer.java:79)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
    at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render
    (ScrollContainerRenderer.java:74)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.UiWindowRenderer.render(UiWindowRenderer.java:52)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
    at
    com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendHtml
    (HtmlClient.java:1039)
    at
    com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.fillDynamicTemplateContext(HtmlClient.java:455)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse
    (HtmlClient.java:1223)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse
    (HtmlClient.java:1179)
    at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse
    (HtmlClient.java:299)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.finishTasks
    (AbstractClient.java:173)
    at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
    at
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:753)
    at
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing
    (ClientSession.java:261)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
    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:387)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
    (RequestAnalizer.java:365)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle
    (RequestAnalizer.java:266)
    at com.sap.engine.services.httpserver.server.Client.handle
    (Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request
    (Processor.java:160)
    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:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run
    (SingleThread.java:170)
    Hope you can help us.
    Thanks and B'Rgds,
    YiNing

    not sure if it has relevance, but the SLD level transports will do nothing but create a CIM file which should be downloaded to your deskktop.
    1. Make sure that there are no Pop Up BLocker's acting on the XI server on your machine.
    2. Make sure that you have the download authorizations on your machine.
    Regards
    Bhavesh

  • Error while adding Poduct to Technical System in SLD

    Hallo all .
    I am trying to add a product to a technical system and i get the following error .
    CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_InstalledProduct.CollectionID="39e669ae-4752-5274-31d1-d7d085055ac",ProductIdentifyingNumber="0",ProductName="********",ProductVendor="********",ProductVersion="1.0",SystemID="SRQ.SystemNumber.**********.SystemHome.*********"
    I have deleted everything (Technical System, Business System, Product) and recreated them but the error persists .
    I also rebooted the j2ee server and cleared the SLD and the CPA cache .
    Every help will be appreciated.

    Thank you both but none of the above is the solution.
    (we had checked the note allready too)
    Currently I am following those instructions, but the problem is that although I delete the TS this is not shown as it should . Still I don't think that it is the TS that causes tha problem but the connection between the TS and the Product . ( My guess is that somewhere there should be a wrong database entry, connecting the TS with the Product. Of course I have no idea where to look for it)
    Cleaning Up Data
    Use
    The data supplier programs report data about the systems in your landscape to the SLD. If a system no longer exists in your landscape, the data about the system remains in the SLD. You have to clean up the data manually in the SLD.
    Procedure
    1. Choose Administration u2192 Automatically Updated Data.
    2. Enter a date and optionally a time before which you want to display the systems that reported data to the SLD.
    3. Choose Display.
    A list of systems is displayed along with the date on which they last reported data to the SLD.
    If a particular date is too far in the past (see Scheduling the Data Collection Programs [Page 66]), this is a good indication that the system no longer exists in the system landscape. The SLD has no way of knowing this, so you must manually remove the system from the SLD.
    4. Select the system(s) you want to remove from the SLD.
    Bear in mind that you remove not only the system but also all its associations to other systems, for example to business systems.
    5. If you want to remove the selected system(s) and all their instances, choose Remove.

Maybe you are looking for