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.

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

SLD error after LDAP integration

Hello All,
I integrated Corporate LDAP with EP 7.0 ,after that I have SLD error when I click on the ESS tab which says:
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics' in the SLD. No such JCO destination is defined in the SLD.
When I go to content Admin->Webdynpro ,the SLD service is stopped and the 'Maintain Jco's' tab is greyed out.
This keeps on happening regularly.
When I go to the SLD log it says 'Server certificate rejected by ChainVerfier' ,I wonder if we need to implement SSL when we have the turned LDAP on.
Any help would be really appreciated
Thanks

Hi Subhash,
I think u didnt configure your SLD properly.
open this link
Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak
which gives the porcedure to configure SLD
for JCO destinations
http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm
Administration manual->server administration->Administration/Configuration of Web Dynpro Runtime Environment ->Web Dynpro Content Administrator
rgds
srinivas

SLD Error : No host name defined in Exchange profile sld.SID.host

Hi,
I am trying to do the configuration for the pre built examples (Airlines, Agency ) using XI after installation.
But when I installed XI and did the post install configuration, I had mentioned 000 as Integration server and configured the same using the SLD (URL) in business system configuration.
But when I was doing the configuration for the example, I wanted to configure the client 100 as integration server on SLD (under business systems) , so I deleted the old business system pointing to client 000 (as it is defined as integration server) and now I am trying to add a new business system (client 100) on SLD and it is giving me an error saying that the integration server already defined.
On the SLD error log it also shows tat No Host name defined in Exchange profile for sld.SID.host...
Are the above two errors related and how do I add the client 100 as a business system on SLD and have it as my Integration server.....
Please help..
Thanks,
Madhu

Moorthy,
Thanks for the reply...but all the checks were successful when I did the configuration in 000 and before I deleted the business system for client 000 in SLD...(See my post and problem above..)....I messed with my SLD and removed the business system for client 000 (which is configured as the integration server) and now when I try to add a new business system for client 100 (as integration server>..) I am not able to do as it gives me a error saying integration server already exists even though I deleted it from SLD Business system..
Thanks,
Madhu

Config SLD error on SAPNWCE71Trial_JavaEEServer

Hi all:
[step-1]After I successfully installed SAPNWCE71Trial_JavaEEServer(downloaded from SDN) on my laptop,
[step-2]goto: http://localhost:50000/sld
error reported: System Landscape Directory(SLD)is not installed on this AS Java system
Question: How to reinstall SLD from SAPNWCE71Trial_JavaEEServer?
Thanks for any help and suggestion

Hello ,
As per my understanding you can not install SLD as single component .
SLD should be install at the time of Installation .
Hope I answer your Question !
Regards ,
Santosh

SLD error - Please see my problem letter by letter.

HI Masters,
before see this error , first of all read my doubt line by line. then only You can understand.
I have three doubts.
first one is :
when i am login to http://hostname:portno/sld browser , it showing error message in red color. Please check it .
1) You do not have permission to view to SLD. Min required : UME role with permission com.sap.lcr.lcruser and j2ee role lcruser.see the sld post-installtion guide for details.
2) SLD not configured. Configure SLD in Adminsitration First.
It showing these above two error messages.
in go.bat file after click on cim client test , i click on trigger sld data transfer, it showing error message.
OPERATION FAILED ! FAILED TO COLLECT DATA . THERE IS NO PROCESS TO READ DATA WRITTEN TO A PIPE..
perform standard user group to role assignment also failed.
Second one is :
I log in to go.bat file and gave correct host name , port no, userid- SLDDSUSER and password in area of cim client test and http settings tab:
after then when i click on CIM CLIENT test . The test conection is failed.
But with j2ee_admin user id in http setting tab and cim client test tab , then click on cim client test.
the test is succeed.
my doubt is generally by using user id - slddsuser in cimclient test and http settings tabs , even then also cim client test will succeed. but in my case with only j2ee_admin user id, only then cim client test is succeed.
why it's happend with only j2ee_admin user only cim client test is succeed. why this one not succeed with SLDDSUSER.
, i click on trigger sld data transfer, it showing error message.
OPERATION FAILED ! FAILED TO COLLECT DATA . THERE IS NO PROCESS TO READ DATA WRITTEN TO A PIPE..
perform standard user group to role assignment also failed.
THIRD DOUBT IS :
I am not finding the roles and users related to SLD and NWDI.
Please give reply . reply will highly appreciated .
Edited by: sujana mullapudi on Nov 4, 2009 1:21 PM

Hi
Please check documentation at System Landscape Directory (SLD) in particular the SLD Post Installation Guide
chapter "Configuring SLD Security Roles"
The SLD users may not be delivered with default authorizations - customers have to select the appropriate or as required roles
Best regards
Stuart

SLD Error exporting technical system

Hi,
While trying to transport our first XI scenario for go-live, we have a error while trying to export a third-party technical system.
The idea is to import the third party development technical/business system in the production SLD as well to setup a transport target for third party production technical/business system that was created directly in the production sld.
We I click export, I do get a page with a link but this link does nothing and there is line with a red exclamation mark.
The sld log shows
#14599166 09/12/2006 14:25:03.402 [SAPEngine_Application_Thread[impl:3]_56] 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:51)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:435)
This sounds like a sap problem
Any suggestion for a workaround ?
regards
Dirk

Hi ...
at first U create a technical system in the development system..and that technical system belongs to development system....
and after u tranport this stuff to the production system...the technical system differs...i.e.u should change the technical system according to ur production system....
Cheers,
Raghavesh

Portal "Start SLD" error

Dear Gurus,
System : NW 7.31 EHP1
I configured SLD in portal, as screen shot maintained below all neccesary RFC status is "Not Defined".
By the way sld is running and configured
When i "Check SLD Connection" Test connection is sucessfully, but seems port -1 and URL is strange(as screen shot) . i dont know it is true or not.
When i "Start SLD" i am taking error like this
What is wrong with that guys ?
Regards

The second screen shot you have attached should have the host name, URL.
To properly configure this service, the following must be done. Use the Destinations Service to:
1. Set up the registration by creating a destination called "SLD_DataSupplier" of type HTTP. Enter the following configuration settings. (Note: The specified user must have the user role "SAP_SLD_DATA_SUPPLIER" or higher on the target SLD Server.)
- Appropriate URL (http://<host>:<port>)
- Authentication should be set to BASIC
- Appropriate User Name and Password
2. Set up the AS Java access to the SLD by creating a destination called "SLD_Client" of type HTTP. Enter the same configuration settings as in the SLD_DataSupplier destination. (Note: The specified user must have user role "SAP_SLD_GUEST" or higher. Aditional write access permissions may be required by certain applications. Refer to the corresponding application documentation for SLD access requirements.)

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.

Sld error in IR when importing SWCV

Hi
I'm unable to import any Software Component Version from the SLD into the Integration Repository. I ran transaction SLDCHECK, and successfully launched the SLD without any errors.
However, when I try to importing any software components from the SLD, the following error message is returned: Unable to read software component versions from System Landscape Directory "host addrres:50000"
in detail button
unable to import any Software Component Version from the SLD "host:50000"(swc_import_process_exception)
like this same 4 msgs comming
under this
unable to open connection to host"
host:500000".
the ip address of host could not be resolved. maybe
the URL is misspelled or the host dies no longer exist.
thess details comming in deatils button
Can anyone help please? it arzzent pls can any one help me
Many thanks in advance.

Hi,
Chek ur role and also check ur id is locked.
to know the authorization role check this link.
http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
Regards,
Phani
Reward points if Helpful

Urgent --SLD ERROR --- While Importing software Compenent Version in Design

Hello,
While Importing software Compenent Version in Design I am getting below error
"Unable to read software component versions from System Landscape Directory "cscvznsdc033.consult.abc.com:50100"
Also when I run tx ---sldcheck I get below errror
"Exchange Infrastructure: Test LCR Connection
Properties of RFC destination SAPSLDAPI
RFC host:
%%RFCSERVER%%
program id:      SLDAPI_IXI
gateway host:
abcvznsdc033
gateway service: sapgw01
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name:   abcvznsdc033.consult.abc.com
port number: 50100
user       : XIAPPLUSER
Use transaction SLDAPICUST if you wish to maintain the SLD server access data
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code     4
=> Check whether the SLD is running!
Summary: Connection to SLD does not work
=> Check SLD function and configurations
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id:      lcrsaprfc_sm4
gateway host:
abcsdcsap9.consult.abc.com
gateway service: sapgw01
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
Error when opening an RFC connection"
Regards

Unable to read software component versions from System Landscape Directory
also check SLDAPICUST transcation and maintain the URL for SLD

Define system on portal J2ee server in SYSTEM CONFIG -- SLD error

Hi,
Can , any body tell me how to create a system on portal J2EE server in which bussiness package has implemented.
WAS properties for the system as
WAS host name:<j2ee name> : <port>
WAS Path:/ webdynpro/dispatcher/
wAS protocol :HTTP
I have tried to create system in System admin--> System configuration --.>SLD .But it is showing following error
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (XX.XX.XX.XX:50000)
5. The host name XX.XX.XX.XX was resolved successfully.
6. The Web AS ping service http://XX.XX.XX:50000/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.
7. An HTTP/S connection to http://xx.xx.xx:50000/webdynpro/dispatcher/ was not obtained successfully; this might be due to a closed port on the Firewall.
Why it is checking R/3 connection setup like sap/bc/ping and other connection . Iam creating WAS connection for java only.Even iam not define any related properties on this system.
Regards,
Eswar.

Hi,
in your ABAP system, open transaction SICF, F8, and go activating the required services :
Default Host > sap > bc > ping. Right click on it and choose "Activate".
This will normally solve your point 6 error.
For point 7 I might think of a port error, can you tell us if your system is load balanced ? if yes, your port defined in your system in the PCD in the connector category hase to be 3600. If not load balanced : 3200.
If implementing SSO, also check in the RZ10 transaction that your default profile contains those parameters :
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
icm/host_name_full = server_host_name.domain.com.
Fabien.

SLD Error in IE:Error while reading ID of own business system from the SLD

Dear Champs,
Scenario : JDBC to Proxy(APO system)
We are getting below error in MONI UAT Box. All other interface are working fine but we are facing issue for a particular Bussiness System also logical system are maintained properly.the same interface is working fine in other UAT box.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>R/3 Sys ID</SAP:P1>
<SAP:P2>"Client"</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading ID of own business system from the SLD for system "R/3 Sys ID"and client "Clnt no"</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards,
Manikandan

Hi Mani,
Solution 1:
Check if the techncal system has associated Business system. I think there is something wrong in your SLD configuration and try to correct it.
Solution 2:
Create a Business system in the ID, and create the communication channel do the respective changes in ID ( I.e Receiver agreement, Receiver determination & Interface).

SLD error after upgrade to SP13

Hi experts,
Our enterprise portal instance has a local sld running in the WAS.
Recently, we upgraded from SP09 to SP13. After this, we are not able to connect to sld from webdynpro administrator.
Given below is the log file content in SLD.
#10 12/23/2007 15:26:48.731 [SAPEngine_Application_Thread[impl:3]_20] FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Failed to initialize cluster notification. Please check your JNDI service and JMS provider for errors.
at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:154)
at com.sap.lcr.cimsrv.ClusterNotificationListener.start(ClusterNotificationListener.java:69)
at com.sap.lcr.cimsrv.CIMOMServlet.init(CIMOMServlet.java:107)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:339)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:354)
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: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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: javax.jms.JMSSecurityException: You do not have permissions: action consumer and instance SLDClusterNotificationTopic.
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2614)
at com.sap.jms.client.session.Session.createConsumer(Session.java:2173)
at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)
at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:142)
... 18 more
caused by:
javax.jms.JMSSecurityException: You do not have permissions: action consumer and instance SLDClusterNotificationTopic.
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2614)
at com.sap.jms.client.session.Session.createConsumer(Session.java:2173)
at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)
at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:142)
at com.sap.lcr.cimsrv.ClusterNotificationListener.start(ClusterNotificationListener.java:69)
at com.sap.lcr.cimsrv.CIMOMServlet.init(CIMOMServlet.java:107)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:339)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:354)
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: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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Why does this happen? I tried this with administrator login itself.
Can anyone help me out please?
Thanks alot
Shobin

hi,
i have reinstalled my environment and use the local CIM with version 1.5.24. the problem came after i tried a new model version with import in http://<host>:<port>/sld.
the settings in visual administrator cluster> Security Provider > Runtime(tab) > service.jms.default.authorization>security roles (view, tab) are administrators and clients. adminstrators have security roles administrators and clients have guests. group is SAP_J2EE_ADMIN . they are all Role Reference, is marked. I go to edit mode and when i change the role type to security role comes a popup with message the selected role reference will be replaced by a new role in order to perform the mapping.
After Reinstall my environment, i dont touch this area in visual administrator.
Note: with jspm variant "single support packages" not sp-stack! i'am on sp level 14 with almost all of deployed components. No problems to CAF SP 14, thtas composite application framework, i became an error.
regards,
christoph
Edited by: Christoph Kautz on Jan 31, 2008 11:19 AM

SLD Error - Urgent

Hi All,
Whenever I create a Technical system in SLD, I get the following errors:
CIM_ERR_FAILED: Unable to execute createInstance() request, exclusive write mode is enabled
Since, I am not able to define a Technical system in SLD, I am not able to create JCo connection, Please help me to resolve this.
Regards / Guru

Hello,
Check whether all roles are assigned to SLD user in visual admin and check whether SLD user is locked in the backend system

SLD Error

Similar Messages

Maybe you are looking for