cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SLD Error

Go to solution
Former Member

on ‎03-01-2008 4:51 PM

0 Kudos

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

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎03-03-2008 8:33 AM
0 Kudos

hai shilpa,

there can only be two reasons for the error your getting.

1.sld setting are not working properly

solution--->contact basis people and check if there is any problem with sld settings

2.Administrator password has expired.

solution-->contact basis people and check if admin passwd has expired and if so ask them to reset.

Thanks n Regards

Sharanya.R

Show replies
Show replies

Answers (3)

Answers (3)

Former Member
‎03-05-2008 1:01 AM
0 Kudos

Hello,

As I mentioned I am able to test the connection from WebDynpro Content Admin and the test is sucessful.

Basis is telling m ethey are having Gateway issues.

Any information about Gateway settings?

Hopefully they can resolve it

Thanks

Show replies
Show replies
suresh_krishnamoorthy
Active Contributor
‎03-05-2008 3:52 AM
0 Kudos

Hi Shilpa,

Check this thread:

Edited by: Suresh KB on Mar 5, 2008 4:58 AM

Edited by: Suresh KB on Mar 5, 2008 4:58 AM

Former Member
‎03-03-2008 7:29 AM
0 Kudos

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.

Show replies
Show replies
Former Member
‎03-03-2008 8:34 AM
0 Kudos

This is done in the Web Dynpro Content Administrator. Choose "Web Dynpro" from the homepage of your Web Dynpro server and then "Content Administrator".

Former Member
‎03-03-2008 7:19 AM
0 Kudos

Hi ,

The error stack says there is JCo is not defined...

check if the Jco Meta data BERLIN_METADATA is in active state.... otherwise create the destination .

Thanks,

Sunitha Hari

Show replies
Show replies
Ask a Question