Access Central SLD Error

Hi Experts,
We are using the SLD SOLMAN and we and the ideia is to use it as Central SLD. In order to allowed PI indentifed the Central SLD we must appllied few oss notes like; 939592, 768148 and 720717, but much as we try it to import we got few errors as describe below:
"Unable to read software component versions from System Landscape Directory "ASPTSSM01:50000"
Another error occurs when trying to access the SLD by the runtime workbench:
"Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)"
Anybody help-me.
Regards,
HMattos.

Hi HMattos,
I hope you have created the PI service users in SOLMAN and assigned the same password as the PI service user password.
Open /rep on your PI and click SLD. Check if it opens the SOLMAN page.
Check in VA if SLD data supplier test works fine.
Check SLDCHECK transaction.
If you get errors in any of these, the you will get a hint as to where is the issue. If you unable to resolve, then post the results of the above.
Cheers....,
Raghu.

Similar Messages

  • Error while Running ESS - TypeBroker failed to access SLD: Error while obta

    Hi all,
    We try to run a WebDypro Application of ESS on 6.40 with mySAP ERP 2004:
    All the necessary JCO connections
    - SAP_R3_HumanResources
    - SAP_RE_HumanResources_MetaData
    are maintained and pinged and tested positive.
    Still, we get following error message. (see complete stack below):
    ...TypeBroker failed to access SLD: Error while obtaining JCO connection.
    Could anybody help, please?
    ERROR STACK
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4011.00.0000.20050217164947.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:49:12[UTC], changelist=329752, host=PWDFM026)
    Web Dynpro code generators of DC sap.com/essarbank:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/pcui_gp~xssutils:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/ess~per:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/pcui_gp~xssfpm:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    Web Dynpro code generators of DC sap.com/ess~xx:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    J2EE Engine:
    No information available
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_08-b03, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:362)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:199)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:171)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:349)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:599)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
         ... 40 more

    Hi
    The type broker error indicates, issue with regard to your SLD. Check whether the SLD is configured properly. You need to do a initial level of SLD between your message server (SAp/back end) and your server. Check whether landscape has been created for the SAP server.
    landscape must be proper with your server configuration/installation number, SID and instance number...etc...
    After you have your SLD, recheck on your JCO for the model data and meta data connections..
    If you have any specific issues do let us know
    thanks
    sathya

  • Central SLD

    I try to import SW Component Version into Repository from Central SLD, System gives me the messagebelow:
    <b>Unable to read software component versions from System Landscape Directory "brckxiprd.internal.borusan.com:50000"</b>
    What must I do to fix this problem?
    thanks.

    hello cemil,
    Check out these note :
    Note 720198 - Integration Repository cannot access SLD
    Note 836093 - IFR: Updating the application components => error
    It may help you out....
    regards
    Prasad

  • How to link XI-Development to the central SLD on XI-Production?

    Hi,
    we have a two systems landscape with XI-DEV and XI-PROD.
    So far, we have used the SLD on XI-DEV.
    Now we want to use one central SLD that is running on XI-PROD for all developments on XI-DEV.
    What is necessary to to that (any documentation available?
    1. First we have done an export/import to copy all technical and business systems to the central SLD.
    2. Then we have set the following parameters in the exchange profile (Section Connections) of XI-DEV:
       com.sap.aii.connect.cr.name: Host of XI-PROD
       com.sap.aii.connect.cr.httpport: Port of XI-PROD
       com.sap.aii.connect.landscape.name: Host XI-PROD
       com.sap.aii.connect.landscape.httpport: Port XI-PROD SLD
    3. Now we have done an SLD data cache cleanup.
    4. TEST: I have created a new business system in the SDL (XI-PROD) to check, if this business system is available in the integration builder on XI-DEV. If i try to assign a new business system, I got the error message:<b>Access to object list of type "BusinessSystem" using the InternalEOAService BusinessSystemAccessor failed</b>.
    Also i get the error: <b>"No connection to SLD"</b> if i try to compare the adapter-specific entries of a business system with the SLD.
    What is the reason? What steps are missing?
    Do i need to maintain transactions like LCRSERVADDR (server address of landscape directory?) and SLDAPICUST or anything else??
    Thanks for any help!

    Chris,
    Follow the OSS Notes
    720717: Reduce the number of System Landscape Direcotries (SLD) &
    768148: Using a separate SLD for XI
    This should solve your problem.
    regards
    Shravan

  • Not Updating in Central SLD

    Hello,
    Upon performing our daily system checks, one of the item is to monitor the sending of SLD data of the installed systems in the System Landscape to the Central SLD which in our case is the XI box. Four of our systems having Java stack did not update. With that, i performed the necessary steps to trigger it so that it'll update in both Web AS ABAP and Web AS Java. With regards to ABAP, i triggered and activated the system to collect and send SLD data via RZ70. As for the Java Systems, i triggered and activated it in the SLD Data Supplier in the visual admin. I performed the CIMOM test and it was a success. Furthermore, i've triggered the send SLD data. In order to check whether it worked or not, i've checked the respective local SLDs of the systems and viewed that it is updated there for both ABAP and JAVA. Furthermore, i've checked the system landscape and viewed the systems are updated for both ABAP and JAVA except for our APO system, both ABAP and JAVA as well. As another step, i reconfigured the Data supplier in the administration of the SLD of APO in order to make sure that the password of xisuper is correct or something. However, until now, it has yet to be updated.
    Hope you could help me.
    Thanks so much!

    Have you checked the Log on the receiving and sending SLDs to see of there is an error?

  • SLD Error

    Hello All,
    I am trying to deploy a webdynpro app .The backend connection fails .
    I am able to test the Jco Connection on SLD and the test is sucessfull.
    Please help
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'BERLIN_METADATA' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:500)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:229)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:214)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:111)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:147)
    ... 45 more
    Stack Trace:
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:com.sap.netweaver.mobile.emp.types.GetEmployeeTimeModel:com.sap.netweaver.mobile.emp.types.Bapicats2 could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:229)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:345)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:40)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
    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)
    Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
    at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
    at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
    at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
    at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
    at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
    at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
    ... 32 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:149)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:175)
    at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
    ... 42 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'BERLIN_METADATA' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:500)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:229)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:214)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:111)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:147)
    ... 45 more
    Thanks

    Hi silpa,
    The exception came as your JCO connection is not defined in SLD; Login to the J2EE server as Administrator and configure the connection BERLIN_METADATA.
    Follow the steps
    Login as Administrator
    Select Button "maintain JCo Destinations"
    Find the Source
    Configure the MODEL_DATA as application data at the Datatype and RFC_METADATA_DEST as Dictionary meta data  .
    After configuring this test it and run the application.
    Regards
      - Vinod
    Rewards if found helpful.

  • XI installation with central SLD

    Hello,
    I have installed solution manger to generate key for XI installation. But, when i in stall solution manager, it installed MaxDB and local SLD and also i think WEBAS ABAP. After that i generated the key.
    And, I am installing XI on the same host. There is no configuration as such i did.I tried to use the same solution manger DB, but i t failed. So i started with New DB creation. And central SLD........
    Is there any configurations that i need to do to install XI with our any errors.
    When i used existing SLD, is there any configuration i have to do.
    More important, i have to install solution manager and XI on same host
    Can anybody any issues here.
    Please advice,
    Srini

    This should be straight forward.
    If the SLD is set up for Sol Man, you enter these details on the in the installation wizard.
    You will need seperate SIDs and you will need to assign the Virtual host names for each installation.
    You will need to check the SLD config after install.  the two sm59 conenctions - LCRSAPRFC & SAPSLDAPI, the sldapicust, the JCo Connections in Visual Admin and the SLD Data Supplier in Visual ADmin.

  • Central SLD - Manipulations

    We want to prepare a central SLD by merging many instances of current local SLDs.
    We found note about merging and grouping instances... it is ok.
    My question deals with next steps because we want to keep local SLD in Production instances (PI, BW instances)...
    We will need to export data of central SLD when built, into local production SLD... but some of local production SLD already have data. Do we need to purge them before import ? If yes how ? Is there a risk to create duplicates entries, associations ?
    Thanks a lot

    Hi,
    Since even bringing up the useradmin web page is slow, it cannot be the SLD.
    Bad response time is caused by cpu, memory and/or network.  Is the SLD server on the same network subnet as XI or your PC?
    You can also logon to the SLD server and examine the cpu and memory utilization.
    Examine the J2EE log to see if there are any errors.  This can also cause response time problem.
    Regards,
    Bill

  • Pointing to central SLD inplace of local SLD

    Hi ,
    I want to change point local SLD to central sld link in  http://hostname:50000/rep/start/index.jsp.
    Please advise me.
    Regards,
    Kirthi S

    Hi ,
    Thanks for replying.
    As per the note am trying to change the Aii parameters to central SLD in xchange profile but xiprofile is throwing a error
    http://10.232.255.56:50000/webdynpro/resources/sap.com/com.sap.xi.exprofui/XIProfileApp
    dbconnect.prop: failed to load properties file 
    Please help me on this.
    thanks
    Kirthi

  • Central SLD setup

    Hi
    We have a freshly installed landscape comprising of Solutiona Manager 4.0,EP 7.0,ECC 6.0,BI 7.0.(I am new to netweaver)
    We need to setup a central SLD on the solution manager system.Also there is a requirement to monitor all system form the solution manager
    NWA.
    Currently when I log onto NWA the follwing error messages are shown
    system Landscape Directory is not accessible!
    Only Local system can be administered!
    Could someone tell me the steps to setup the SLD(ie connect different systes),setup central NWA and some basic concepts.
    As far as I understand SLD data supplier is used for communication between the j2ee engines.
    so for eg: for a pure Java stack like EP is it enough to give the logon details of Solution manager in SLD Data supplier of Ep's Visual administrator..?
    Please help.
    thanks
    rocky
    P.S: will reward points for helpful answers.

    Hai,
          It is better to mention the central SLD server details during the installation process in the phase,Registration in System Landscape Directory(central SLD,local SLD,no SLD)
    We need to setup a central SLD on the solution manager system.Also there is a requirement to monitor all system form the solution manager
    NWA.----
    > Maintain the Central SLD as Solutionmanager system.Login into the other system and go to Visual Administrator(c:\usr\sap\SID\DVEBMGS<instno>\j2ee\admin\go.bat)->Server->Services->SLD Data Supplier-> In the tabRuntime, HTTP Settings->Give the host name of the Central SLD system(Solman),Port number, SLDDSUSER,and password and save the settings and then in the
    CIM Client Generation Settings->Give the hostname of the Central SLD system,port number,SLDDSUSER and Password,save the settings and click on the CIMClient Test to check the CIM Test.
    Once the CIMTest is successful,
    Click on the button(Assign application roles to user groups) and also on the button (trigger datatransfer to System Landscape Directory(SLD)),this transfer the settings to the Central SLD system.
    Thanks and Regards,

  • Central SLD is too slow.

    Hello all,
        We have central SLD which is contectecd to XI sandbox, dev, NWDI and Portal. This SLD is extremely slow even when trying from the server. Even when I go useradmin web page, it takes about 2 minutes to display page. This server has 4 Gigs fo RAM.
    Any suggestions?
    Regards,
    N.S

    Hi,
    Since even bringing up the useradmin web page is slow, it cannot be the SLD.
    Bad response time is caused by cpu, memory and/or network.  Is the SLD server on the same network subnet as XI or your PC?
    You can also logon to the SLD server and examine the cpu and memory utilization.
    Examine the J2EE log to see if there are any errors.  This can also cause response time problem.
    Regards,
    Bill

  • SRM SWCV not geting synched up in CMS from Central SLD

    Hi,
    We set up SRM SWCV in Central SLD and using that in Dev system.
    We want to transport this SWCV from Dev to QA using CMS.When we are trying to do this transport we are getting error and the reason is there is no entry of SRM stuff in CMS.
    Our CMS is pointing to Central SLD and when we are trying to Update CMS it is pulling all other SWCV s from Central SLD except SRM stuff..So we couldn't add SRM SWCV in CMS...
    So,please let us know what we are doing wrong...or Should we approach differently to load SRM content in QA systems..
    Thanks in advance
    Venu

    Yes Venu,
    You need to import SRM Content into QA syste.
    DO NOT TRANSPORT CONTENTS....!
    Thanks

  • Central sld problems ?

    Hi Guys,
    The scenario is like this.
    1. Central SLD installed on solution manager
    2. We are trying to connect an XI BOX to this central SLD.
    Steps did in XI BOX:
    1. SLDAPICUST - points to SLD host.
    2. Exchange Profile - values set for Connections like cr.name and landscape.name.
    3. SLD Data supplier - in visadm - points to Central SLD - due to this, The Java stack of XIBOX is listed as a technical system in central SLD and data collection works correctly.
    3. JcoRfc Destination - LCRSAPRFC_XIBOX - program id registerd in visadm with gateway host and service as XIBOX gateway service itself.
    Steps did in Central SLD:
    1. Jco Rfc Destination - SAPSLDAPI_XIBOX - program id registered in visadm with gateway host and service as that of the XIBOX.
    2. SLD Data Supplier - points to sld itself and when data collection is done - sld itself is added as a technical system in SLD.
    Problems:
    1. IR and ID are not regsitered in SLD under Technical Systems of type Exchange Infrastructure
    2. when trying to import the SWCV from the sld getting the message as "unable to read the data from the centralsldhostname:50000"
    3. when i do the cache notifications in ID, i am getting the error as unable to determine the central adapter engine.
    4. Adapters not listed under adapter monitoring
    5 when i go the administration cache overview, i am not seeing the adapter meta data like af.server
    checked the settings according to 720717, 768148, 939592.
    any help would be really appreciated
    Thanks,
    Srini

    Hi Agasthuri,
    I dont have any issues with the SLDCHECK and it works fine. I have already done the reimporting of the basis component.
    Thanks,
    Srini
    Edited by: srinivas kapu on Jan 29, 2008 2:32 PM

  • Not able to access Central admin or any other site

    My machine name has been changed from abc-xyz to DT-012
    After changing my machine name am not able to access Central admin or any other site in sharepoint. which says '
    Server Error in '/' Application.'
    Please tell me after changing machine name what else i have to change so i can access my SharePoint back.

    Hi Niraj, 
    Thanks for posting your issue, Just wanted to know have you changed server name  using below mentioned command?
    stsadm -o renameserver -oldservername oldservername -newservername newservername
    I hope, you have not changed your SQL Server name/instance. If changed SQL too. Kindly re-run the configuration Wizard of SQL server to set up Alias.
    Also, Browse below mentioned URLs to know more about the fixes of this issue
    http://www.ericjochens.com/2013/03/change-sharepoint-server-hostname-and.html
    http://www.bluesphereinc.com/blog/renaming-a-sharepoint-20102013-server/
    I hope this is helpful to you, mark it as Helpful.
    If this works, Please mark it as Answered.
    Regards,
    Dharmendra Singh (MCPD-EA | MCTS)
    Blog : http://sharepoint-community.net/profile/DharmendraSingh

  • Difference Between Central SLD & Local SLD

    Hi All,
    Q1) What is the Difference Between Central SLD & Local SLD.
    Q2) Maintaining Individual SLD For DEV, QTY, PRD Servers is the Best One Or Maitaining the Single SLD is the Best One ????
    Please Ans These Two Q's
    Regards
    Vamsi

    > 2. Maintaining individual SLD for DEV, QTY  & PRD
    > will be better approach. We follow this approach.
    SAP recommends a Single SLD.
    Having a separate SLD for every environment beats the concept of SLD itself. SLD is a place where you can look and understand what components/ system run in your landscape. If you are going to hve one for every Environment, it is against the concept of SLD itself. More maintenance is another issue.
    Single SLD as recommended by SLD has the problem that you do not want to provide access to a component that can be used in production to developing teams and so on .What Barry has pointed is something that is a more practical approach.
    There are no hard and fast rules. A client present across Geographies, havinng multiple vendors and IT teams handling different geographies would prefer to have multiple SLD's one for each Geography and then maybe a master SLD that is going to conain all info of the other Sld's and so on., There is no direct answer to this question other than it purely depends on individual clients.
    Regards
    Bhavesh

Maybe you are looking for

  • IDoc Package to File using Multi Mapping urjent

    Hi Experts, I have a scenario where PI 7.1 need to receive IDocs in a package and should send three files to target system. I am using multi mapping concept here, where i have created one message mapping, one operation mapping with three interfaces s

  • Windows XP setup errors on KT3-ARU

    I have a KT3-ARU & am having problems installing Windows XP on my pc. An error message comes after or installing the devices. Current  hardware(s) AMD Athlon XP 1800+(locked, non-overclocked) Samsung 256MB PC2700 RAM Maxtor UDMA100 20GB HDD(Conected

  • Two versions of Front Row?

    I just noticed using System Profiler that there are two versions of Front Row on my iMac. Version 1.0 is located in /Applications Version 2.1.6 is located in /System/Library/CoreServices/ Double-clicking either one brings up versions 2.1.6. Does all

  • How to make my website logo show as the new Yosemite favourites icon?

    I've been searching high and low for the answer to this question so I hope someone maybe able to help me. When you click in the address bar in safari using Yosemite you get the icons from the websites that you have as a favourite. Some, like Facebook

  • Distortion using USB port for audio output

    I did some research in the Mac Mini community regarding the problem I'm experiencing but most of the posts were several years old so I thought I would start a new thread. I am using one of the USB ports on my 2011 Mac Mini (2.3GHz, i5) to feed a High