Create JCO Exception

Hi Experts,
My issue is:
In Enterprise portal when i try to create Jco i am getting the following exception:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
     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:285)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
     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:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     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:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     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.doPost(DispatcherServlet.java:53)
     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: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: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:160)
     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)
Please help me out in this aspect i have created a WebAs ABAP also in SLD but still issue persists..
Urgent Help needed..Points will be awarded...

Hi,
You see an exception with a message like:
NullPointerException, maintaining JCo destinations.
java.lang.NullPointerException
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
cause for this error might be that:
some fields for the backened system used to setup the JCO destination are not updated properly that is in SLD. Once you have configured your SLD please also ensure that you have selected the relevant "Message Server Connection". The Message Server, system name and logon group must not be left empty. And ensure that SLD contains up to date and complete information about backened systems
You also need to ensure that the SLD is setup properly. click on the test connection to check that the SLD is up and running.
Hope it helps.
Regards,
Mona
Edited by: Mona Kapur on Feb 29, 2008 5:44 AM

Similar Messages

JCO$Exception when creating RFC model

Hi all,
I'm getting this fatal error when creating an RFC model in Web Dynpro for Java (connecting to a BW system):
com.sap.mw.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
I have absolutely no clue what's going wrong...
The RFC model gets created, but when running the application it doesn't work...
Any help appreciated!
Jeroen

Raj,
Thanks for your reply.
I had already solved the problem... After a long time I found out it was due to the language: when creating an RFC model one should use the language of SLD.
kind regards,
Jeroen

While created JCO i got following exception plese guide me

Hi Guru.
While created JCO i got following exception. I configured SLD also.
I dint select message server information while cretin of JCO. it would mandatory for creating JCO. because i dint get in information about message server while creating of JCO. if it need where can configure to get Message server in formation. please give me some guide lines
Failed to create new JCO client connection WD_MODELDATA_DEST: 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(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.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_MODELDATA_DEST 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.JCOClientConnection.<init>(JCOClientConnection.java:106) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) ... 35 more
Best regards
Ramana

Hi.
Thanks for your response.
But I am working for WebDynpro For JAVA with R/3 BAPI calls.
For this scenarios , we would configure for WEB AS ABAP??
I was configured for WEB AS JAVA..
Could you please confirm me.
While configure of WEB AS for ABAP. i have following attributes
1. Web AS ABAP Name (SID):
2. Installation Number
3. Database Host Name:
I need to ask BASIS guy for this setup.
Best regards
Ramana

Exception while creating JCO destinations

Hello,
I have deevloped a webdynpro application as a local DC and trying to deploy and run it. While doing this step it throws an exception as "NullPointerException" when i click on create JCO connection.
The error details are like :
"at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
    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)"
Can anyone please help me how to resolve this problem.
Thanks.
- points rewarded for helpful solution

Hi,
The Following Procedure Follow To Create JCO Destinations.
First You Configure SLD Correctly.If You Have ECC And BW.You Maintaing Two WEBAS ABAP Systems.
You Create WEB AS ABAP System In SLD And Maintain Connection Properties Of ECC.And
Similarly For BW Also.
If You Want To Create JCO Destinations.You Go To Login Portal
Content Administration->Webdynpro->Create JCO Destinatiion
A.General Data -> Specify Model Name,Client And JCO Pool Configuration
B.Specify J2EEE Cluster
C.Destination type
Data Type-> Application DataModel,Dictionary MetaDataMetadata
Destination Type->Load Balancing Or Single Server
D.Specify Either Application Server Or Message Server
E.SecurityUsername,password,confirm password,language
F.SummaryWhole Information
Similarly Metadata Created Follow Same Steps As Above
After Creating JCO Destinations, Go For Maintain JCO Destination And test The JCO Destinations Works Fine Or Not you Con Test.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/webdynpro/wd%20java/portal%20integration/how%20to%20use%20the%20web%20dynpro%20content%20administrator.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm
The Given Below Links To Help You SLD Cofiguration For J2EE
http://www.*********************/solution_manager/solution_manager_sld.html
SLD Configuration
It's Useful Rewards Points
Bye
Thanks
SubbaRao

Exception while creating JCo client connection Failed to create

Hello all -
I am trying to create JCo metadata connections and I am getting the below error trace.
Exception while creating JCo client connection Failed to create new JCO client connection SAP_R3_HumanResources_Metadata: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to change password for key SAP_R3_HumanResources_Metadata in secure storage at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:149) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:299) 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:265) 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.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321) 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.doPost(DispatcherServlet.java:53) 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: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:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) Caused by: com.sap.security.core.server.securestorage.exception.ObjectStorageException at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.storeObject(RemoteSecureStorageClientContextImpl.java:600) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:137) ... 33 more
Could anybody please suggest what is wrong with this creation?
Thanks much!!

Hi Maria,
Please update the host and sevice file first then check the SLD test and SLD Data supplier in visual admin.
Also check and verify the data using in the Jco destination creation.
Hope it will helps
Regards
Arun Jaiswal

Failure in Model Create Step: com.sap.mw.jco.JCO$Exception: Missing R3NAME=

Hi,
I am running NW04sp10 and am trying to connect my WebDynPro to my R/3 backend app server - am running through the FlightChecking example using DevStudio 2.0.10.
Have successfully created my meta + app data JCo's, they test and ping OK from the Content Manager. SLD is fine, connecting happily to the NW and R/3 boxes. One is message server, one central instance.
When the 'create model' wizard tries to build the java proxies though, it comes back with this:
[Fatal]: com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
Can anyone help?
Cheers guys,
Andy

Hi Wael,
I'm using the tutorial 'Handling Transactions with BAPIs in Web Dynpro' [part of SAP Online Help].
The BAPI does work in se37, it's just a standard SAP delivered BAPI, and I've tried a few different ones to make sure it wasn't a BAPI specific problem.
In the content admin I've navigated through the local/FlightChecking/Applications/FlightCheckingComp and then used the wizard to add the 2 JCOs [I've kept the default names for now after your previous advice]
The data is like this:
WD_MODELDATA_DEST:
Name WD_MODELDATA_DEST
Client 800
J2EE Cluster Name NW1 on chippy
USER USER1
Password <password>
Application Server nero
System ID 00
WD_RFC_METADATA_DEST:
Name WD_RFC_MODELDATA_DEST
Client 020
J2EE Cluster Name NW1 on chippy
USER USER1
Password <password>
Application Server chippy
System name NW1
Logon Group PUBLIC
My landscape here is of 2 servers:
'Nero' SAP r/3 4.7 Application Server System ID ACI
'Chippy' SAP WebAS640 NW04 System ID NW1 ABAP+J2EE stack
The JCOs 'test' and 'ping' successfully. My WD_RFC_METADATA_DEST connection is to a message server, the WD_MODEL_DEST is to a central instance.
Here's the full log from the create model wizard [I used a random BAPI for testing, BAPI_GET_PAYSLIP, so don't worry about that]:
[Warning]: Creating a connection with Metamodel language <en_GB> failed. Continuing with language <EN>
[Fatal]: com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
[Info]: Creating Model: FlightChecking
[Info]: Creating Model Class: Bapi_Get_Payslip_Input
[Info]: Creating Model Class: Bapi_Get_Payslip_Output
[Info]: Creating Model Class: Bapireturn1
[Info]: Creating Model Relation: Bapi_Get_Payslip_Output:Return
[Info]: Creating Model Class Property: Type
[Info]: Creating Model Class Property: Id
[Info]: Creating Model Class Property: Number
[Info]: Creating Model Class Property: Message
[Info]: Creating Model Class Property: Log_No
[Info]: Creating Model Class Property: Log_Msg_No
[Info]: Creating Model Class Property: Message_V1
[Info]: Creating Model Class Property: Message_V2
[Info]: Creating Model Class Property: Message_V3
[Info]: Creating Model Class Property: Message_V4
[Info]: Creating Model Class Property: Employeenumber
[Info]: Creating Model Class Property: Payslipvariant
[Info]: Creating Model Class Property: Sequencenumber
[Info]: Creating Model Class: Bapi7004_Payslip
[Info]: Creating Model Relation: Bapi_Get_Payslip_Input:Payslip
[Info]: Creating Model Class Property: Format_Col
[Info]: Creating Model Class Property: Text_Col
[Info]: Creating Model Relation: Bapi_Get_Payslip_Output:Payslip
[Info]: Creating Model Relation: Bapi_Get_Payslip_Input:Output:Bapi_Get_Payslip_Output
So it seems to actually be able to retrieve the metadata for the BAPIs, but not to make the relevant JCo's. I've not gone on and completed the tutorial, assuming it won't work until I can sort out the above 'fatal' error.
Thanks again for all of your good advice.
Cheers,
Andy

Jco.JCO$Exception when create a new adaptive model in NWDS

HI friends:
when I create a new adaptive model in NWDS, error occurs:
Warning:Creating a connection with Metamodel language <zh_CN> failed. Continuing with language <zh>
Fatal: com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
but when I used a existent model to reimport model , it has no error
Thank you in advance.
Yonk
Edited by: Yonk King on Nov 7, 2008 11:11 AM

Check whether you are providing the correct login credentials while importing the RFC.

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

JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: CMRCV on convId

Hi all 
 
Somtimes I am getting this kind of error message within Portal... 
 
Full Message Text: 
 
failed JCO execute function; stack trace: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: CMRCV on convId: 37753022 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR connection to partner '10.204.16.xxx:3310' broken 
TIME Sun Nov 28 18:30:17 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -6 
MODULE nixxi.cpp 
LINE 4424 
DETAIL NiIRead 
SYSTEM CALL recv 
ERRNO 10053 
ERRNO TEXT WSAECONNABORTED: Software caused connection abort 
COUNTER 3 
 
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516) 
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1514) 
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980) 
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3417) 
at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:173) 
at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:164) 
at com.sap.mdi.ddtypes.DDFactory.getDDObject(DDFactory.java:412) 
at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:292) 
at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94) 
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:169) 
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:175) 
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:260) 
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:231) 
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.ClientComponent.createComponent(ClientComponent.java:940) 
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177) 
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149) 
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141) 
at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:761) 
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920) 
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) 
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) 
at com.sap.xss.ser.xssmenu.vc.area.VcXssMenuArea.onInit(VcXssMenuArea.java:232) 
at com.sap.xss.ser.xssmenu.vc.area.wdp.InternalVcXssMenuArea.onInit(InternalVcXssMenuArea.java:257) 
at com.sap.xss.ser.xssmenu.vc.area.VcXssMenuAreaInterface.onInit(VcXssMenuAreaInterface.java:162) 
at com.sap.xss.ser.xssmenu.vc.area.wdp.InternalVcXssMenuAreaInterface.onInit(InternalVcXssMenuAreaInterface.java:144) 
at com.sap.xss.ser.xssmenu.vc.area.wdp.InternalVcXssMenuAreaInterface$External.onInit(InternalVcXssMenuAreaInterface.java:220) 
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564) 
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438) 
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196) 
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110) 
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) 
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:430) 
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) 
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783) 
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303) 
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761) 
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696) 
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) 
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) 
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) 
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869) 
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229) 
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344) 
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356) 
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549) 
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593) 
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865) 
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) 
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) 
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) 
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) 
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333) 
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712) 
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) 
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.doPost(DispatcherServlet.java:53) 
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: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:104) 
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) 
 
Thanks a lot in advance. 
Regards, 

Hi prodyut kumar sen ,
Thanks for reply.
1. Server Process is ok
2. Logon Group(Tracsation SMLG) is ok.
3. Technical system is ok in SLD.
4. We are already increasing the no of JCo connection as blow.
JCo Pool Configuration
 Maximum Pool Size: 50
 Maximum Connections: 200
 Connection Timeout (msec.): 30
 Maximum Waiting Time (msec.): 60
5. Network connection (Ping EP and ERP) is OK.
 Ping <host> -l 65500 -t
6. Hosts and Service file is OK.
 We have DNS Server. It is ok too.
7. We are already settings for these values as below. (Note 316877).
Environment Variable
 CPIC_MAX_CONV = 5000
SAP-Gateway
 gw/max_conn = 4000
 gw/max_sys=3000
 gw/max_overflow_size=60000000
 gw/max_shm_req = 400
Profile parameters
 rdisp/tm_max_no=10000
 rdisp/max_comm_entries=2000
Sometimes, I still occur an error in Web Dynpro for Java.

JCO$Exception: RFC_ERROR_SYSTEM_FAILURE in WAD Template

Hi All!
I have a problem when executing a WAD Template that calls a Planning Sequence with a botton. If I execute the same sequence in the Portal --> Bussines Planning It do it correctly, but When I execute it from WAD Template the following error appears:
Access via 'NULL' object reference not possible.
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Access via 'NULL' object reference not possible.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3962)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3399)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Proxy.executeFunction(Jco640Proxy.java:255)
com.sap.ip.bi.webapplications.runtime.controller.MessageException: Error while executing function module: BICS_CONS_CREATE_PLANNING_FUNC at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2520) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:841) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:775)
I have checked the JCo connections in Content Administrator --> Web Dynpro --> Mantain JCo Connections and the test is successful.
Any Idea??
Thnks a lot!!
Yolanda.

Hi Yolanda
Please refer the following links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f3f93ee7-0c01-0010-2593-d7c28b5377c2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/526bd490-0201-0010-038e-d3ff7eb1d16e
Also which Patch level are you using for BI 7.0 . Your basis team should set the Integration of RSPLAN i,e web based planning modeller . Also hope you created the Input ready query correctly with Key figures having property set to Data can e changed using a planning function or by user.
Also check on WAD if you have configured the button group correctly to the planning function.
Hope this helps
Raja

JCO Exception

Hi Gurus,
I have created two JCO Destinitation for my RFC, when i am trying to ping the connection it says "ping successful" but when i test i am getting the following error.
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: The initial password has expired; request a new one
Can anyone please help me on this , this was not coming in my pervious system for which i have created the conection.
Is someting wrong on the ABAP system ?
points will be rewarded for quick solutions.
Rakesh

Hello Rakesh,
Change the user type of the communication user that UME uses in Transaction SU01 to "System" (B) in the ABAP end.
FYI
Due to an error in the installation program (SAPInst) for NetWeaver 2004 and due to an incorrect documentation, the communication user used by the UME has the type "Communication" (C).This type is incorrect because it is subject to the mandatory password change and the initial password ageing just like type "Dialog" (A) (see Note 622464).
The following profile parameters affect the system's response:
o rfc/reject_expired_passwd
o login/password_max_reset_valid (ABAP 6.20 / 6.40) or
login/password_max_idle_initial (ABAP 7.00) and
login/password_max_idle_productive (ABAP 7.00)
In delivery status, these profile parameters are set in such a way that the RFC logon is not affected.
This information is at SAP note 959242.
Thanks
Pankaj

RFC Adapter - JCO Exception - Please Urgent

I am developing a scenario from File--RFC integration. I am using File and RFC adapter to perform this transaction.
The File Adapter is picking the file properly and the trnaformation (Mapping Program) is also happening properly. But the RFC is throwing the following error. I got this error info from the Runtime Workbench.
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR
Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR.
The RFC is executing without any problem when I execute this from the transaction SE37.
I have created communication channel in Integration Directory in appropriate manner.
I also created RFC destination in the XI system (TCODE SM59) and the same is using in the "Receiver Determiiation - Service".
I have not done any configuration at SAP R/3 side. Is any config required at R/3 end for this scenario - please let me know.
Please throw some light on this. I will greatly appreciate your help.

Friends,
Please suggest on this vague problem that I am facing. Your help would be greatly appreciated.
1. I am using SAP-PS (Projects & Systems) BAPI 'BAPI_BUS2002_ACT_CREATE_MULTI' to create the activities for a project. According to this BAPI documentation,
- First call 'BAPI_PS_INITIALIZATION' before make this BAPI call
- After BAPI call, we should use 'BAPI_PS_PRECOMMIT' and 'BAPI_TRANSACTION_COMMIT'.
2. Hence, I have developed Z-Func Module with Initialize, BAPI call - then Pre Commit and Commit.
3. This is executing from SE37 without any issues. Other parameters to make a remote call is also set properly.
4. To make sure that, I made a JCO call from Java Program using PDK for Java. This is also working fine.
5. But when I used this in the XI scenario (File-XI-RFC) this is showing ABAP dump and this is invoking from Pre-Commit module.
I couldn't figure it out why it's happening like this.
I did lot of troubleshooting and the details are as follows for your reference.
1. The mapping program is working fine without any issues. I confirmed this by writing these input values to the file (ofcourse lot of pain) inside the function module. All the values have been parsed by XI and coming to Func Module as expected.
2. No issues with logical destinations (SM59).
3. I have tried other options such as clearing the Cache...etc.
Hence, please throw up some light. If any body tried with these kind of BAPI (needs initialize, pre-commit and commit) I really appreciate your effort.
Can we enable the debugging of func module when the XI makes a call...? - I tried with Standard options that seems doesn't work.

Problem with RFC adapter (JCO Exception RFC logon failure)

Hi ,
I have SOAP to RFC scenario.
Scenario with same configuration (RFC adapter) is working in QA system.but when I have transported to PRODUCTION system
it is showing
com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE:
I have gievn max conn=10 ;Refresh the cache also
and checked Roles and authorization also but still I am getting the same error.
Regards

Hi ,
I have created all the objects manually. and it is working.
now it is showing other error when I am sending the messages from SOAP side it is showing
MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6 does not exist in runtime cache</SAP:Stack>
for this I checked the Interface determination step and receiver determination ,mapping program all looks correct.
I have refershed cache also both Complete and SLD.
but nothing is wroking
Please advice.
Regards

Message Servers not appearing when creating JCO Destination

Hello Experts,
I had created a System Object in the Portal system landscape based on System Template (Template) and choosed SAP system with load balancing (to connect to R/3 server).
Given parameters to Connector, ITS, WAS and User management, when i test the connection test on these settings, All are successful except the connector settings. but when run the transaction code(System Administration -> support-> portal runtime-> SAP Transaction) by selecting this message server, it is executing.
And i want this message server to be selected when creating JCO destination.
This System Object is not showing in the message servers dropdown box selection when creating the JCO destinations.
What may be the issue.
Could anyone help me in solving this.
Thanks in advance
Regards
Sunil

Hi,
Have you checked the Technical systems in the SLD ? When you click on check sld , you appear an SLD url ,,,
Typing the same URL in browser and loging inwith SLD USER .... have you seen all the technical system which you want to appear while creating the JCO's ..
Regards,
Srini

AS Java 7.10: Can't create JCO destination 'WD_RFC_METADATA_DEST' in SLD

Hello,
I registered my J2EE 7.10 in the central SLD (sldmain.wdf.sap.corp:53000) successfully and created JCO destinations WD_RF_METADATA_DEST + WD_MODELDATA_DEST there. But the deployment of a WD application using Adaptive RFC fails because the above JCO destinations are not found (or access to SLD fails at all?). I didn't find any documentaion on how exactly the 2 destinations must be configured. On the central SLD there's no test/ping function for JCO-destinations! Could it be that my WD-deployer still tries to access a local SLD?
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 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:442)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:230)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:215)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:106)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138)
Thanks and regards,
Jens

Jen,
Edit your JCo destinations and make sure you have Metadata as data type. I am guessing you are getting this error becuase you might have selected Application data as data type.
Hope this helps

Create JCO Exception

Similar Messages

Maybe you are looking for