Unable to create JCO connections for ESS self service

Hello SDN,
I am configuring the ESS for an EP 7.0 and a ECC 6.0(EP and ECC are combined in one instance).
I need to configure some JCO connections at:
http://host:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
But i cannot create any JCO connection from there. I filled in all fields that are necessary. But I keep receiving this error messages:
MsgServerName is not defined.
SystemName is not defined.
LogonGroupName is not defined.
Which is strange because I have defined the right message server. The SLD connection to the SLD is working fine. I have upgraded the SLD and the EP java stack to SP 9.0 which is the highest level.
Does anyone know the solution for this problem?
Thanx in advance,
Regards,
Bart

Hi ,
Add logon group Public in the tx smlg then execute tx RZ70 then try to create RFC destination
Regards,
Sreekantha

Similar Messages

Unable to create Metadata connection for Dictionary Provider

Hi,
I am getting the following error while I try to run a Web Dynpro Application;
The initial exception that caused the request to fail, was:
   com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
    at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
    at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
    at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
    ... 37 more
The JCo Connections are tested and pinged, they work fine.
Can anyone please tell what the error could be?

The details exception list is as below:
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.dow.dc.model.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     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:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     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:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.dictionary.runtime.DdException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
     at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:191)
     at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
     at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
     at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
     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:242)
     ... 34 more

RFC Error: Unable to create Metadata connection for Dictionary Provider

I configured two RFC ('WD_XXX__MODELDATA_DEST and WD_XXX_RFC_METADATA_DEST). I tested it and it shown green light.
When I run my application that coonnect to CRM using RFC, I got the following errors:
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.xxx.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_ICEBERG_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
 at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:670)
 at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
 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.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:443)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:381)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:410)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
 at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
 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.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:311)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:347)
 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: 'WD_XXX_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_XXX_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
 at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
 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:242)
 ... 49 more
I understand that I need to configured the Metadata Dictionary type for the RFC. For this, I need to configure the Message Server properties (for load balancing).
But my Basis guy told me that CRM is an application server, so we only can configured with application server properties. Is this true? (I really doubt it) That is no Message Server connection to CRM system now.
If it is true, how can I create a RFC connection to CRM system?
Thanks for help.
Kent

Hi KC,
Try the following links, they may help you.
http://help.sap.com/saphelp_nw04s/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
JCO connection
Using the SAP Enterprise Connector for generating BAPI Proxy Classes
points if useful
Thanks
Suresh

How to Create JCO Connectionds for ESS processes?

Hello ,
I had imported Business packages for ESS and now i'am gng to create JCO connections for the corresponding ESS processes.I know where to create them but Can you please tell me what are all the fields i need to fill while creating a jco connection.Please send if you have any document.
With Regards,
Pradeep.B

Hi Krishna,
I had gone through the process and i got a error in ping and testing the JCO connection"com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=srtplecd GROUP=SPACE R3NAME=SCD MSSERV=sapmsSCD PCS=1 ERROR service 'sapmsSCD' unknown TIME Fri Nov 16 19:22:13 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 2 "
please help me
with regards
Pradeep.B

Error while creating jco connection for metadata?

Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: 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:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) 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.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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(AccessController.java:180) 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.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) 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.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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(AccessController.java:180) 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: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) 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.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
Rajendra

Hello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh.

Unable to create a connection for Discussion Forums.

Hi,
I have my WC_Spaces and WC_Colloboration Servers running actively. When I try to create a new connection by right-clicking Connections in Applications Resources and choose Discussion Forums and too I entered the URL and admin fields, I find its unable to create a new connection. The error displayed is : "Failed to verify connection". Please help me with this.
Regards,
Dinesh Vishnu Kumar

Hi,
In your webcenter application you have created the discussion forum connection and you have connections.xml file in your application.Open the connections.xml in jdeveloper and check the discussion forum connection entry.
For example here I have written down my entry on forum connection-
<Reference name="Discussion Forum Connection" className="oracle.adf.mbean.share.connection.webcenter.forum.ForumConnection" xmlns="">
<Factory className="oracle.adf.mbean.share.connection.webcenter.forum.ForumConnectionFactory"/>
<RefAddresses>
<StringRefAddr addrType="forum.url">
<Contents>http://localhost:8890/owc_discussions</Contents>
</StringRefAddr>
<StringRefAddr addrType="admin.user">
<Contents>weblogic</Contents>
</StringRefAddr>
<StringRefAddr addrType="connection.time.out">
<Contents/>
</StringRefAddr>
<StringRefAddr addrType="policy.uri.for.auth.access">
<Contents/>
</StringRefAddr>
<StringRefAddr addrType="policy.uri.for.public.access">
<Contents/>
</StringRefAddr>
<StringRefAddr addrType="recipient.key.alias">
<Contents/>
</StringRefAddr>
<StringRefAddr addrType="adapter.name">
<Contents>Jive</Contents>
</StringRefAddr>
</RefAddresses>
</Reference>
Change the required entries with your values(for serveraddress,port and admin user).
One more thing need to consider that is -
in jdeveloper proxy ,add the server address in exception list and restart the jdeveloper.
Sometimes it will show you up as "failed to verify the connection". But it will work atleast functionality-wise it will work.
Apart from this,I have a query on "Have you used any VPN connection to connect collaboration server to create forum connection?"
Hope it works for you.
Regards,
Hoque

I created new menu For Manager Self SErvice and added the transfer manager

Hi SSHR Gurus
I Manager transfer sshr function to Custom menu.But This function is not functioning the way it works on Manager self service. Any thoughts on this greatly appreciated.
Cheers
kumar cs

Hi kumar,
You need to double check in your custom menu you have added Manager Menu action without prompt and you setup profile option HR:Manager Actions Menu against responsibility.
Also, after that you need to bounce Apache and clear cache.
For more information about Manager Action Menu please refer to note :
Note 263015.1:Deploying SSHR Capability Implementation Guide
Chapter 2 page 2-11 ----- > Menus for Managers
Thanks,
Mounir

Problems creating JCO Connections

Hi experts,
I have a question regarding the JCO Connection creation in Content Administrator.
My first doubt is if it's necessary to create each JCO Connection for each backend system that I'll run RFC functions?
If is it true, during Creation I must specify user and password. I have to specify the Backend User and Pass, right?
Finally, could you explain me why there are several JCO connections created?
When I create the JCO connection I will be able to invoque Backend RFC functions from, for example, a webdynpro?
Kind Regards,
Martin.

Hi Martin,
1. Yes, provided you want to use the RFC functionality.
2. Yes, you would be giving the username and password for the metadata.
Please refer to [Creating JCo Destinations|http://help.sap.com/saphelp_nw70/helpdata/EN/3a/3b1b40fcdd8f5ce10000000a155106/frameset.htm]
3.Generally, when you install business packages like ESS MSS etc, there are a bunch of JCO which are installed as well, but all you would have to do is edit its properties and point them to the correct location.
4. Yes, you can.
Regards,
Sandeep Tudumu

Error - unable to establish JCO connection with SSO

Hello,
I have implemented XSS on WebDP and this is working fine. So my JCO connections SAP_R3_HumanResources must be configured correctly. However I have just done the 'GetFlight' BAPI tutorial and upon execution I get the error:
'com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.sap.tut.wd.flightlist.model.FlightModel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!'
CAUSED BY
'User not authenticated (is anonymous) - unable to establish JCO connection with SSO'
Can anyone help here?
Thanks
Mr.T

HI
GOOD
GO THROUGH THIS LINK WHICH CONTAINS THE A SINGLE SIGN-ON IN A COMPLEX SYSTEM LANDSCAPE.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/80fbc690-0201-0010-1aba-93d5c8232b4a
http://www.sap-press.de/download/dateien/1020/sappress_sap_security_authorizations.pdf
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ff65b5a2-0a01-0010-5b97-e747192a1d49
THANKS
MRUTYUN

Unable to get a connection for pool - ResourceUnavailableException

Hi
I have a BPEL process which starts a child instance of another asynchronous BPEL process for each message in an XML file. The child BPEL process makes a call to the Oracle Apps JCA Adapter to push the data into E-Business Suite.
All works perfectly except when the number of messages exceeds a certain limit (15 or so). The error received is as follows:
"Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'SyncPersonRecord' failed due to:
JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection.
ebsPeoplesoftEmployees:SyncPersonRecord [ SyncPersonRecord_ptt::SyncPersonRecord(InputParameters,OutputParameters) ] :
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue:
javax.resource.spi.ApplicationServerInternalException:
Unable to get a connection for pool = 'eis/Apps/Apps',
weblogic.common.resourcepool.ResourceUnavailableException:
No resources currently available in pool eis/Apps/Apps to allocate to applications.
Either specify a time period to wait for resources to become available, or increase the size of the pool and retry.. Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections.
Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution."
Obviously what is happening is the connection pool maximum is reached (currently 15) and this is throwing the error.
What I need to do is to implement the suggestion of "specifying a time period to wait" and I was hoping someone could tell me how I do this?
I have tried setting the 'Connection Creation Retry Frequency' parameter to 30 seconds which made no difference and also have checked the documentation on "Configuring and Managing JDBC Data Sources for Oracle WebLogic Server".
Does anyone know if this is something that is implemented directly in the BPEL process/composite or in the connection source itself.
Many thanks

Open the jndi : eis/Apps/Apps in /console - config tab - increase the initial and max conn capacity and save it. Retry the scenario

Unable to create a connection in SQL developer

hii
I'm unable to create a connection in SQL developer..it says I/O Exception, Network Adapter could not establish a connection...i provided the username and password which i used for SQL*Plus, which is working fine. And i gave the host as localhost. I don't know how to fill the connection name field..can anyone help me in connecting to the database...By the way I'm using Oracle 11g. Thankssssss

you could try to change the connection type to TNS and pick the database name available to you in the Network Alias drop-down list.
Edited by: Alex Nuijten on Sep 5, 2008 10:13 AM

Problem create jco connection in webdynpro application run time

Hi There,
I created webdynpro application using rfc model.
After deploy the project , i created two jco connection
for data & meta data this is work o.k (test with no errors). the sld is o.k.
We are using application server (Single Server) for data
& message server for meta data (Load Balance).
During run time there is an error message:
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.ness.crm.customerlasttwo01pckg.model.types.Datab could not be loaded: com.sap.dictionary.runtime.DdException:
 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:471)
 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.getMappableContext(Component.java:371)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 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.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 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:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 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:
 at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
 at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
 at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:78)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:64)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:39)
 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)
 ... 44 more
Can some one help me with this matter?
Best regards Nir Shohat.

Hi Nir,
We also had same problem but no we won't. Check ur config on SLD again and the try to the test connection from the http://localhost:4444/webdynpro ( WAS 6.4 )server.
If this connection is OK then deploy some small application n see.
Is ur's JCo connection working for J2ee application?
Arnigs

JCO connection for Meta Data fails

Hi,
I have installed the WebAS Preview version with SP9. I had installed it once and had succesfully configured the JCo connection to my R/3 system. After I re-installed the WebAS after a system format, I have configured the JCo for both model & metadata. Both are configured to connect to the same R/3 sytem with the same user/password combination. But the JCo connection for model data pings and test come OK. But the one for metadata fails (ping as well as test).
I have tried creating more JCo connections with different names, but again the model one works, but not the metadata one.
Can anyone figure out why this is happening?
Regards,
Sumith.

Hi,
The error that I get when testing the JCo connection is:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=ltilsap GROUP=PUBLIC R3NAME=LTI MSSERV=sapmsLTI PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service 'sapmsLTI' unknown TIME Fri Jan 21 16:37:40 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 MODULE ninti.c LINE 494 DETAIL NiPGetServByName2: service 'sapmsLTI' not found SYSTEM CALL getservbyname_r COUNTER 1
and when I ping it gives:
Failed to ping JCo destination 'LTI_WDMETADATA_DEST'.
But the connection for model data works perfectly for the same set of configuration.
Thanks & Regards,
Sumith

Error in creating JCo connection with destination type'Load-Balanced Con'

Hi,
I am working on webdynpro application(NW 04s), i need to connect with the backend system(ECC 6.0) using model.I configured my SLD and created technical system successfully.
The technical system got created with an error:
CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_BCApplicationServer.CreationClassName="SAP_BCApplicationServer",Name="ID1.Number.01.HostName.ahsides"
But the system got created so I proceeded with Jco connection creation:
I need to create 2 Jco connections for this,
First with Data Type 'Application Data' & Destination Type 'Single-Server connection'. Second with Data Type 'Data Dictionary' & Destination type 'Load-balanced Connection'.
The first Jco with 'Single-Server connection' got created successfully and ping and test is also successfull.
The second Jco connection with 'Load-Balanced Connection' got created successfull but it is throwing error while pinging and testing.
Ping Error : Failed to ping JCo destination 'WD_EMPLOYEE_RFC_METADATA_DEST'.
Test Error : com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call
Please help me in this.This problem was with 'Load-Balanced Connection' only.

Hi,
Have you taken a look at the file %windir%\system32\drivers\etc\services?
If you haven't, try and find the line sapms<sid>, where sid is de SID of the system you-re trying to reach.
If the line isn't there write it down like this.
sapms<sid> 36<nr>/tcp
That works for me.

Creating JCO connection

Hello
I am trying to create a JCO Connection in our EP6-SP9 (Menu Content Administration -> Web Dynpro -> Create JCO Connection). I have not installed a SLD for EP6 but have configured the EP6 to use the SLD of the XI 3.0 SP9. The test connection works OK. The creation of the JCO fails with the message below
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
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.4009.00.0000.20041011171310.0000 (release=630_VAL_REL, buildtime=2004-10-19:21:48:59[UTC], changelist=290362, host=PWDFM026)
Web Dynpro code generators of DC sap.com/tcwdtools:
No information available
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
No information available
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
java.lang.NullPointerException
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:737)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
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.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
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)
I request help in resolving the above error
Thanks & regards
S Lahiri

Hi
Can you be more specific as to what stage you get this particular error.
Couple of Questions :
When you are creating a JCO connection are you able to see the systems configured in SLD of the XI machine.
Can you tell the steps that you have done to point your WebAS to SLD of the XI machine.
Also try clicking on the Check SLD connection and see if the connection is ok.
regards
Ravi

Unable to create JCO connections for ESS self service

Similar Messages

Maybe you are looking for