JCO DESTINATION ERROR

Hi Everyone,
We created JCO RFC's between PORTAL and ABAP systems, they are working fine. we also created the JCO destinations for METADATA in web dynpro. While we are trying to test the JCO destination it is throwing the following error
<h4>com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=indhcm GROUP=SPACE R3NAME=E6M MSSERV=sapmsE6D PCS=1 ERROR service 'sapmsE6M' unknown TIME Tue Feb 21 17:57:28 2012 RELEASE 701 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 1</h4>
Help me regarding this issue
Regards,
Mahesh

Hi Mahesh,
Please check
1. SPACE logon group is created in SMLG
2. Check if the below entry in maintained in services file in the system.
sapms<SID> 36$$/tcp # SAP System Message Server Port
$$ - is your instance number of the abap system.
What is the SID for ABAP and JAVA system.
Thanks
Jaianandh V

Similar Messages

JCo destination error while executing the webservice model

Hi,
I have explained what I have done so far and whats my issue right now.
My requirement is calling a PI interface (exposed as webservice) from webdynpro for java and setting some parameter value to the PI interface based on which our functional flow will continue.
Done so Far :
1. Created a webdynpro for java application using NWDI.
2. received the WSDL file of the PI interface and imported as "Adaptive webservice model" into webdynpro.
3. used the model and set the parameters to PI interface and executed the model.
4. I have created JCO destinations in the source system (where the application runs) to communicate to the PI system. A special user has been created and assigned in the connection for communicating.
5. Also I have created the "Dynamic Webseviceproxies" in visual admin with the same name as the JCO destinations. It had a property "URL" for which I have tested with providing both the PI server URL (Http://<Hostname>:<Port no>) and also the complete webservice URL (Which calls the WSDL file directly)
when I run the application, I get the following error.
1. Exception on creation of service metadata for WS metadata destination 'WD_RFC_METADATA_DEST' and WS interface '{<Interface Name>'. One possible reason is that the metadata destination 'WD_RFC_METADATA_DEST' has not been properly configured; check configuration.
after some exception the next error follows
2. Invalid Response Code 403 while accessing URL: <The URL which I have provided in the webservice proxy in Visual admin tool> Response Message: Forbidden.
after some lines of exception from PI server the next error follows.
3. Error: You are not authorized to view the requested resource
My Question :
1. Do I miss anything in Configuration?
2. Is my way of approach wrong?
3. Any additional authorization needed?
Kindly provide some ideas and inputs.
Regards,
Mahendran B.

Dear Mahendran
JCO destination will not used for the Web Service Model. While creating the webservice model, you need to use the logical destination which you have created in the Visual Admin.
Please refer to the Secured WebServices II and verify currently used webservice logical destination How To Reimport Web Service Models in Web Dynpro for Java
You can also refer to
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/900bbf94-a7a8-2910-e298-a651b4706c1e?QuickLink=index&overridelayout=true
Hope it will helps
Best Regards
Arun Jaiswal

RFC Adaptive Model,JCO destinations error

HI,
I created the tutorial application to get Flight List using RFC adaptive model.
I created the JCO destinations in web dynpro content administrator after configuring the SLD (after many problems though ).
Our Server is Web AS 6.4 ABAP + JAVA ,but no R/3 modules installed.
WD_FLIGHTLIST_MODELDATA_DEST-type application--single server connection
WD_FLIGHTLIST_RFC_METADATA_DEST-type Dictionary-load balanced
The JCo destinations status shows green.
The test for WD_FLIGHTLIST_MODELDATA_DEST is succesful but the test for WD_FLIGHTLIST_RFC_METADATA_DEST fails with the error:[code]
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR Group PUBLIC not found TIME Thu Nov 10 18:24:23 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 2 [/code]
The ping fails and if i test it again,i get another error
[code]com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 ERROR Group PUBLIC not found TIME Thu Nov 10 18:29:13 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 1 [/code]
What is wrong?Any more steps required?
If i try to edit it,the type is still the same-Application with single connection.
How can i change it?Do i need to change it to type Dictionary in the first place? How to proceed.
Please guide.
Regards,
Siddhartha
Message was edited by: Siddhartha Jain
Message was edited by: Siddhartha Jain

hi Siddhartha,
You have to configure PUBLIC group using SMLG transaction
check these links out
http://help.sap.com/saphelp_nw04/helpdata/en/28/1c623c44696069e10000000a11405a/content.htm
hope this helps you
Regards
Rohit

ESS/ MSS JCO destination error...

Hi All,
I have created all JCO destinations and when i test them , the result is successful
But once i click on ess/mss tab in portals, i get the error..
<i>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_HumanResources_MetaData' in the SLD. No such JCO destination is defined in the SLD.</i>
But i have maintained SAP_R3_HumanResources_MetaData in the SLD.. Actually i have two SAP_R3_HumanResources_MetaData services one is active and another is inactive..
For SAP_R3_HumanResources -- i have used "Logon Ticket" and for SAP_R3_HumanResources_MetaData -- used userid & pwd.
Actually i have to do UserMapping as my portal userid and R/3 userid are different.. Then in this case am i creating JCO destinations correctly.. If not how to do..
Please throw some light into this problem by your valuable suggestions.
Thanks & Regards,
Mahesh.M.R

Hi
I am having the exact same problem (i think). I believe that the problem is caused by a failed connection to the SLD.
In my case, if I scroll the bottom of the error page, the 'Detailed exception chain' has the error:
TypeBroker failed to access SLD: Error while obtaining JCO connection.
The same error can be found in the DefaultTrace.
This ESS is on a nw2004s sandbox portal (trying to reach an ECC 6.0 sandbox), but being lazy I just reused the SLD in my Development environment.
This is however a Java WAS 6.40 and according to Note 954820 (Compatibility of SLD in the system landscape)
QUOTE
In general, the connection of systems to the SLD is released for SLD client applications with releases earlier than or equal to the SLD release (to be more precise: the AS Java release on which the SLD runs). Within a release, all Support Packages are released.
UNQUOTE
So, i'll try activating the SLD on a nw2004s JAVA WAS and use that instead.
Regards
Stig

Error when trying to create a JCO Destination

Hi
I receives the following error when trying to creat a JCO Destination, clicking on the button in the host:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
I get the following error:
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:880)
     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:740)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640)
     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: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)
Any ideas?
Regards
Kay-Arne

Hi,
Have you configured your SLD? Check JCO Destination error out or search for "com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus" in the SDN forums.
Best regards,
Vladimir

How to Maintain Jco Destinations ( using ARFC2 )

Hi Friends
I call ARFC2 setting WD_MODELDATA_DEST and WD_RFC_METADATA_DEST.
... then get error message.
com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination WD_RFC_METADATA_DEST does not exist
    at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:195)
    at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:344)
    at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:96)
    at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
    at com.sap.tc.cm.arfc2.metadata.RFMParser.<init>(RFMParser.java:78)
    ... 74 more
I wnat to Maintain the demo01's JCo Destinations, but the page is null.
Where can I create WD_MODELDATA_DEST、WD_RFC_METADATA_DEST.
thx.

Hi BenChen,
You need to create JCO Destination in the SAP Portal >> Content Administration >> Web dynpro >> Maintain Jco Destinations.
If "Create" button not active,then you need to check SLD running or not and SLD data supplier.
Please refer to below documents will helps
[System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?quicklink=index&overridelayout=true]
[JCO Destination Errors|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0?quicklink=index&overridelayout=true]
[How to Configure the JCo Destination Settings|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf]
Hope it will helps
Regards
Arun Jaiswal

Getting error in creating JCo destination for WebDynpro

Hi Guys,
I am getting an error in creating JCo Destination under Web Dynpro Content Admin.I am deploying MSS on Netweaver portal SR1 and ecc 5.0.I am getting a message"An error has occurred: "Failed to process the request."Contact your System Admin.
When I am seeing the details:
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322), 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.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
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:
6.40 patchlevel 87289.311
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows 2003, version: 5.2, 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)
Please help me guys.
Paritosh

You should post your question to the Webdynpro forum:
Web Dynpro Java

ERROR WHEN I CREATE A JCo DESTINATIONS

Hi to all
I have the SLD running. I want create two JCo destinatios. I want create a Web Dynpro application with adaptive RFC Model.
But, I login to http:///webdynpro/dispatcher/sap.com/tcwdtools/Explorer
and when I attempt create a JCo destinations, appear the following error:
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:985)
    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)
    ... 45 more
Can someone say me, why occurs this error ? I have reviewed all my configuration, but I haven´t found nothing.
Thank you very much.
Regards
Dario Rodriguez

I think while creating the JCOs you must hav left some field with a NULL value.Try to check out that all the connection properties hav been specified correctly also make sure that the connection pooling has a small range.

Error while creating the JCO destinations

Hi All,
I am getting the following error while creating the JCO destinations.
<b>There are no message servers maintained in the associated SLD. Please contact your system administrator.</b>
Please help me in resolving this
Thanks

http://help.sap.com/saphelp_erp2005vp/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
Creating New Web AS ABAP Technical Systems
/*Reward if helpful
Message was edited by:
Anant
Message was edited by:
Anant

RFC error while creating JCo Destinations

Hi Team,
We have been getting RFC_Communication_Error over time and again while creating MetaData type JCo Destination in EP 7. Actually We am configuring a Business package for ESS.
I am pasting the error,
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=<server> GROUP=public R3NAME=<xxx> MSSERV=sapms<yyy> PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service 'sapms<yyy>' unknown TIME Tue Jun 12 16:43:08 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapms<yyy>' not found SYSTEM CALL getservbyname_r COUNTER 4
We have created Application type connections successfully. the tests on these were also successful.
Thank you,
Vamshi

Can u pl check for the entry in the services file of the JAVA Engine/portal.
sapmsQ10 36XX/tcp
If this entry is not there please create the same @ ..WINDOWS\system32\drivers\etc\ open the services file in notepad and make an entry in the last line.
format is
sap<SID> Press TAB once 36XX/tcp<Press Enter>
where XX is the Instance no of your Java Central Instance.
If the prob persists please update.
Priyabrata

Error In JCO Destination Creation

Hi,
I'm creating JCO Destination in Web Dynpro for Java. While finishing the JCO Destination wizard it shows a error as follows:
Root Cause
The initial exception that caused the request to fail, was:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:507)
    at java.util.ArrayList.get(ArrayList.java:324)
    at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.getElement(Node.java:2022)
    at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:617)
    at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:749)
    ... 45 more
But the JCO Destination is created successfully and I can test and ping tit successfully. But it becomes the part of System Denied JCO Destinations.
In the server log file I'm getting the following log:
1.5#00112F5374F1005B0000011100000EDC000443BF97417983#1200390062389#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0#####SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Cannot navigate via outbound plug tointeractiveForm of view InvoiceListView because there is no navigational link attached to it
Exception id: [00112F5374F1005B0000010F00000EDC000443BF974176DF]#
#1.5#00112F5374F1004F0000055B00000EDC000443BFA0A4587B#1200390219953#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#subhayuds#116#####J-Integra for .NET TP Thread 2##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of a Web Dynpro application: "java.lang.IndexOutOfBoundsException: Index: 0, Size: 0".
[EXCEPTION]
#1#java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     at java.util.ArrayList.RangeCheck(ArrayList.java:507)
Can anybody help to find out this problem.

Hi,
This is a Web Dynpro bug. You need to apply the latest patch for Web Dynpro runtime.
Regards
Srinivasan T

Java error when testing JCo-Destination

hi,
i create a JCo-Destination with connection type 'ticket', when testing it i got the message:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Der Aussteller des SSO-Tickets ist nicht authorisiert
What do i have to do ?
best regards, Martin

Hi Martin,
Just to ensure that the error is because of SSO ticket configuration. Please create a SAP Transaction iview for any transaction and assign the SAP System configured for SSO.
If you are able to test it successfully then the issue is different. Otherwise as pradeep said configuration of SSO is not done. Search for some blogs or messages in forum for the same. There are a lot. Even the link given by pradeep will also help.
Hope this helps!
Regards
Atul Shrivastava

Error when creating a JCo destination

Dear All,
I am trying to create a JCo destination using the 'Content Administrator' but am getting the following error:
"Please choose another name for the new JCo destination. The defined name 'SLD_PROBE_XYZ' is used in the SLD."
It seems that whatever name I give the JCo destination, a similar error occurs.
I have read a couple of pdf's on JCo destinations but to no avail. Any pointers would be much appreciated...
Kind Regards
Chris Jackson

>Hi,
> "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed >attempts"
As you can clearly see that logs are stating that user you are entering in JCO destination to connect to backend system has wrong password.
Check the password of the user that you are entering in JCO destination.
Thanks
Sunny

500 internal error at Jco destination

When tring to create any Jco destination, we get "500 internal error".
Anybody has the experience to fix it? Thanks! Points!

Hi, Jennifer.
i'm sorry but "500 internal error" has too many possible causes.
You need more detailed info in the log files under the following folder.
/usr/sap/<SID>/JC00/j2ee/cluster/server0/log
So, please reproduce your problem and check the files - usually
defaultTraceX.trc and applicationX.log
Good Luck.
Sejoon

Error with Metadata Jco destination....

Hello All,
I have created Modeldata destination which i have tested and working fine.
And i am trying to create my metadata Jco destination here i am getting error some thing like Message
server error.... what i should do over come from this error.
Thanks in advance....

Hi,
Are you using any service user in R/3 for user mapping in meta data destination. And check this service user password is not locked/expired.
I hope you are using the sso logon ticket for model data destination. So that is the only difference..
Check R/3 Message server is configured in SLD properly or not.
You need to create the technical system for R/3 in SLD. To create this system you need to know the message server host and port information. So you can use this function module "SLDAG_GET_MESSAGE_SERVER_INFO" to get this information required to configure the R/3 technical system in SLD.
Anfter configuring this technical system you need to configure the JCO destinations in WebDynpor content administartor.
Go through the below document for step by step procedure.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5
Regards,
Charan

JCO DESTINATION ERROR

Similar Messages

Maybe you are looking for