JCo & qRFC / IDOC_INBOUND_IN_QUEUE Error

Hello everybody,
I have a java based server application, transporting IDocs between MES + SAP ERP. Till now I used tRFC for transfering IDocs from SAP to my server application. at the moment I'm checking out, how to use qRFC with my application. I changed everything in SAP as required, so SAP is sending via qRFC. In my server application itself I didn't change anything yet.
I'm told the following error message, while trying to receive the IDoc from SAP in my server application:
JCO_ERROR_SYSTEM_FAILURE: the call handler factory [com.sap.conn.idoc.jco.rt.DefaultJCoIDocCallHandlerFactory] returns null for the function IDOC_INBOUND_IN_QUEUE (raised by system mycomputer|a_rfc)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:662)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2450)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:278)
     at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:363)
     at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:239)
     at java.lang.Thread.run(Thread.java:619)
Caused by: RfcException: [mycomputer|a_rfc]
    message: the call handler factory [com.sap.conn.idoc.jco.rt.DefaultJCoIDocCallHandlerFactory] returns null for the function IDOC_INBOUND_IN_QUEUE
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by mycomputer|a_rfc
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2840)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2653)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2544)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2365)
     ... 4 more
Caused by: RfcException: [mycomputer|a_rfc]
    message: the call handler factory [com.sap.conn.idoc.jco.rt.DefaultJCoIDocCallHandlerFactory] returns null for the function IDOC_INBOUND_IN_QUEUE
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by mycomputer|a_rfc
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3388)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2835)
     ... 7 more
Caused by: com.sap.conn.jco.JCoRuntimeException: (128) JCO_ERROR_NOT_SUPPORTED: the call handler factory [com.sap.conn.idoc.jco.rt.DefaultJCoIDocCallHandlerFactory] returns null for the function IDOC_INBOUND_IN_QUEUE
     at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:86)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:154)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3359)
     ... 8 more
I'm using SAPJco 3.0.6 with SAPIDoc 3.0.5 and JAVA 1.6.0_16-b01
Any idea / help is appreciated.
Thanks in advance
Sebastian
Edited by: Sebastian Holzschuh on Jan 11, 2011 1:51 PM

Hi Sebastian,
A questionable comment coming in late; I'm hoping though that there might be at least little value to it...
First of all we have to distinguish between outbound and inbound qRFC. And though you can have a mixture of them, I recommend taking a quick peek at the online help on the [qRFC communication model|http://help.sap.com/saphelp_nw70ehp2/Helpdata/EN/e7/555e3c0f51a830e10000000a114084/frameset.htm], where you can see that obviously using an outbound RFC queue is completely transparent to the recipient (and doesn't require any changes as long as the RFC server program is capable to handle transactions). So your external JCo IDoc server should work fine with an outbound qRFC queue (e.g. see [qRFC Outbound Queue|http://help.sap.com/saphelp_nw70ehp2/Helpdata/EN/3b/befa40badbf46fe10000000a1550b0/frameset.htm]).
Now I don't know if technically you could implement a JCo server program that uses inbound qRFC. Though the help mentions qRFC for interface JCoServerTIDHandler I don't really see API support in JCo for inbound qRFC. I'm be curious to hear some comments from others about that, my guess is that one would implement a custom queuing mechanism outside the SAP API...
Cheers, harald

Similar Messages

Error in BPM: "COMMUNICATION FAILURE" during JCo call. Error opening an RFC

hello experts
i am receiving the above error incase of BPM scenario where i am having a Transform step and synchronous RFC step.
i referred to the few threads discussing such problems and was trying to find whether my mapping is correct and i tested my mappings using my payload which looks good.
When looked into the Mapping trace of the BPM "Show container" i found error ""COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection" and it seems that when BPM is attempting to call interface mapping it is throwing this error.
Thanks in advance.
Regards
rajeev

hi,
I think no problen with the mapping part,
jco connection requird when xi try to stablish the connection with the adapter .
please look the link provided.
Setup and test SAP Java Connector outbound connection
please also check the following parameter at the exchange profile
com.sap.aii.rwb.server.centralmonitoring.r3.ashost
com.sap.aii.rwb.server.centralmonitoring.r3.client
com.sap.aii.rwb.server.centralmonitoring.r3.sysnr
com.sap.aii.rwb.server.centralmonitoring.httpport
these parameter must be given properly.
if every thing is ok than and problem still exist than try to restart the system.
for us after restarting its worked fine.
regards,
navneet

Random JCO Communication Failure Error after Hardware Migration

Greetings experts,
we had a migrated our XI server to new hardware and had couple of SLD related issues which were solved by the migration team. However, we are getting JCO communication failure very frequent whenever we use JCO from JAVA to call an RFC. The weird thing, if you restarted the message it will be successful.
The error message in the message monitor :
"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection"
Any idea to solve this random issue?

Hi again,
the number of connection was increased to 200 but with no effects. Also, the user used to connect is a system user which does not need a ticket.
This is my connection code
               mConnection = JCO.createClient("600", // Client
          "USER", // Username
          "PASSWORD", // Password
          "EN", // Language
          "hostname", // Host
          "01"); // System Number
do I need to add anything else if I am using a clustered system?

Jco connection Test error

Hi Exports,
When I test the Jco connection below error message getting,
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=csslecc GROUP=SPACE R3NAME=ECC MSSERV=sapmsECC PCS=1 ERROR service 'sapmsECC' unknown TIME Fri Aug 28 04:38:05 200 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapmsECC' not found SYSTEM CALL getservbyname_r COUNTER 1
Kindly help me to solve this problem.
Thanks
Jibin.

Hi Jibin
This is mostly likely due to JCO or network setup rather than the ESS/MSS application
Please see the following link
http://help.sap.com/saphelp_nw2004s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
In particular check network services as per note
Note 52959 - sapms..., sapdp.., sapgw.. unknown (or not found)
Please check JCO connection settings as well as per
Note 723562 - SAP Java Connector: Configuration and Requirements
Please check availability of message server and that user terminal can ping Portal server
and Portal server can ping ECC server
Hope this helps
Best wishes
Stuart

[JCO.ServerThread-1] ERROR SERVER-EXCEPTION - [null,null,null,] com.sap.mw

When we execute a SAP transaction through xMII, xMII server is brought down.
I looked in the cms.log file and found this:
2007-10-16 11:07:23,355 [JCO.ServerThread-1] ERROR SERVER-EXCEPTION - [null,null,null,] com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Oct 16 11:07:23 EDT 2007.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 64 seconds.
When I try to log back onto xMII, I see the following:
Error Executing Transaction Status (500) Internal Server Error.
I created a Business Logic Services transaction within XMII. This BLS extracts data from AFPO Order Item table. A Repeater loops through the RESPONSE output table, and executes a SAP Query to load the data into Oracle tables.
I also have a BLS that executes BAPI_PRODORD_GET_LIST.
When I execute either one of these transactions, the system will fail with the above error when the amount of data being extracted reaches a specific number.
I have simplified the BLS to run a JCO block for BAPI_PRODORD_GET_LIST and a tracer block. When I execute the BLS that executes BAPI_PRODORD_GET_LIST to retrieve 2,000 production orders, the transaction hangs. After 30 minutes, I terminate the transaction so it wont take the xMII server down again. However, had I had a repeater to loop through the output and load into the oracle tables, the server goes down.
Thats my problem. My other question to the problem is this.
What are the limitations to the amount of data that can be extracted from SAP via xMII? Excel spreadsheets can download 40,000 records. You can write a SELECT * in any language and pull down 40,000 records. What is going on?

David,
Just an FYI the error message that you have found is not connected to your BLS transaction but rather the default IDoc listener trying to connect to something that doesn't exist. This listener will automatically start each time xMII starts, as a result you can set it up to connect to an RFC destination or delete the default configuration and it will go away.
Now onto your issue; How many Production Orders are being returned from the BAPI? How are you loading each of them into Oracle? How much memory is allocated to ServletExec vs. How much is available on the machine? By default xMII will limit all SQL/Tag queries to their RowCount with a max at 250k rows but this does not apply to the JCo call.
My suggestion here is to look for the other error message that pertains to your transaction which may reside in the ServletExec logs and not xMII, they can be found on your xMII machine here: http://localhost/servletexec/admin/login.jsp
Hope this helps.
Sam

SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

Hello Everyone
I am setting Up SSO between my EP 7.0 and my ECC 6.0 system. During the phase JCO RFC PRovider i am giving the following values:
The following was done;
1. start Visual Administrator -> Service : Choose JCo RFC Provider
2. Created JCo RFC provider:
Program ID: SAPJ2EE_Port
Gateway host: EPDEV ( host of my EP System)
Gateway service: sapgw00
Server Count 5
Application Server Host: ERP6 ( Host of my ECC System)
System Number: 00
Client: 000
Language: EN
User: SAPJSF
Password: ..
When i click on SET i am getting the error " ERROR When ADDING TO BUNDLE" Check LOG FOR DETAILS".
I checked the DEFAULTTRACE.TRC and get the following MEssage :
Date , Time , Message , Severity , Category , Location , Application , User
03/01/2011 , 3:33:30:101 , Error changing bundle SAPJ2EE_PORT , Error , /System/Server , com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(BundleConfiguration conf) , , Administrator
03/01/2011 , 3:33:30:085 , com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Mar 01 03:33:30 PST 2011.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=SAPJ2EE_PORT GWHOST=EPDEV GWSERV=sapgw00
ERROR       partner 'EPDEV:sapgw00' not reached
TIME        Tue Mar 01 03:33:30 2011
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
I have configured my SLD as well. Any suggestions. Please Advise.

Hi Ahmed,
Please do check the validity of the certificate.
Please do cross check these steps again.
1.     Transaction u2013 STRUSTSSO2 (Trust Manager for Logon Ticket)
2.     Double Click Owner certificate. It gets reflected under the certificate tab.
3.                  Choose Format Binary
4.                  Choose File Path.
5.                  Enter the File Name
6.                 saved in local drive.
You can import into portal as x.509 certificate.
check this thread -
Certificate no longer has signature (use restriction)
Renew certificate via SAP MarketPlace, and install from tcode slicense. If you are working on a trial version, there is a SAP license request application form. Fill the form with the hardware key. you will get the new license via email. Install using slicense. Then try exporting the certificate.
Thanks,
Divya
Edited by: Divya V on Mar 10, 2011 11:25 AM

Random JCO Communication Failure Error

Dear All,
I am facing the weird issue of JCo connection failures. I am facing the error of Max no of conversations excedeed. If i am testing it then it is giving me error. But after some time if i check it again it will be successful and also ping will be also successful for the JCo. I am facing for all JCo which we have created in the Portal System.
We have 3 landscape system here. In my Development and Quality this type of error is coming which is very randomly.
In our Production server its not coming.
So i am very confused why this type of random behaviour is of JCo Connection.
Regards,
Dhruv Shah

Hi Dhruv,
If you are using WD application, then you should use disconnectIfAlive() in finally block of try-catch while executing RFC model.
Please check the Web Dynpro Best Practices: [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] that will helps you identify maximum pool size, connections and timeout etc.
Also refer to JCo Pool Configuration and http://help.sap.com/saphelp_nw04/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm
Hope it helps
Regards
Arun

JCO Connection giving error when try to edit or preview it.

Hi,
We have in our project PD6(Portal) only java stack & CD1(ECC6.0) system is acting as respective backend.
The JCO connection has already been configured for it,but when I try to edit or preview one of the JCO connection it is giving below error.
Error :
500   Internal Server Error
Failed to process request. Please contact your system administrator.
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: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:251)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
    ... 45 more
Detailed Error Information
Detailed Exception Chain
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:251)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
     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: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(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Please let us know your input on this.
Regards
Nilesh

Likely Cause would be some fields for the backend system used to setup the JCO destination are not updated properly (i.e.
empty) in SLD. Once you have configured your SLD please also ensure that you have selected the relevant u201CMessage Server Connectionu201D. The Message Server, System Name and Logon Group must not be left empty. Ensure that SLD contains up-to-date and complete information about backend systems.
Check that the SLD is setup properly, check whether you have registered the system through config tool into SLD If not please register system into SLD so that all the parameters are transfered to SLD automatically. You need to do this even the u201CTest Connectionu201D to SLD is successful. Once you are registered you should be able to create the JCO destinations with out any issue.
Thank you.
Shyam

(SUP for Blackberry) JCo unknown type error when using PT_ARQ_REQUEST* RFC

Dear community,
I am encountering a weird error when trying to execute the PT_ARQ_REQUEST_PREPARE RFC in a Leave Request scenario for BlackBerry with the SUP.
When creating the MBO from the RFC PT_ARQ_REQUEST_PREPARE and testing it with the parameters
im_command = create
im_modus = r
im_pernr = 00001000
im_wi_id = 000000000000 (initial value)
im_request_id = *emptyString* (initial value)
I get an "execution suceeded" everytime EXCEPT when I try to return the output structure ex_request! However, this is exactley the information needed to execute the following RFCs PT_ARQ_REQUEST_EXECUTE and PT_ARQ_REQUEST_CHECK. The error I get when executing is the following:
unknown JCO type
java.sql.SQLException: unknown JCO type
I checked for short dumps in the transaction ST22 and found an OBJECTS_OBJREF_NOT_ASSIGNED_NO (CX_SY_REF_IS_INITIAL) error that marks an error when retrieving the attributes (most likely from the ex_request structure). I looked at the structure and found out that it is a deep structure. Could that be the reason for the error? How can I fix it and get the correct output? Does anybody has experience with a similar problem?
Thank you for your help in advance!
Best regards,
Jenny
PS: some additional info about the error message:
unknown JCO type
unknown JCO type
java.sql.SQLException: unknown JCO type
com.sybase.vader.jca.sap.connector.cci.SapJcoResultSetMetaData.getColumnType(SapJcoResultSetMetaData.java:135)
com.sybase.uep.eis.RecordSetImpl.<init>(RecordSetImpl.java:69)
com.sybase.uep.tooling.eis.BaseEISOperation.getRecordSetFromResultSet(BaseEISOperation.java:980)
com.sybase.uep.tooling.eis.BaseEISOperation.execute(BaseEISOperation.java:259)
com.sybase.uep.tooling.eis.BaseEISOperation.execute(BaseEISOperation.java:154)
com.sybase.uep.tooling.eis.SapEISOperationImpl.execute(SapEISOperationImpl.java:401)
com.sybase.uep.tooling.ui.ModelsUtil.getEEISOperationMetaData(ModelsUtil.java:252)
com.sybase.uep.tooling.ui.ModelsUtil.refreshAttributes(ModelsUtil.java:892)
com.sybase.uep.tooling.ui.ModelsUtil$3.run(ModelsUtil.java:778)
com.sybase.uep.tooling.om.util.MobileObjectModelsUtil.execUpdate(MobileObjectModelsUtil.java:1027)
com.sybase.uep.tooling.ui.diagram.extension.commands.CommandUtils.runUpdate(CommandUtils.java:219)
com.sybase.uep.tooling.ui.ModelsUtil.refreshRead(ModelsUtil.java:742)
com.sybase.uep.tooling.ui.ModelsUtil$6$1.run(ModelsUtil.java:1046)
org.eclipse.gmf.runtime.diagram.ui.properties.sections.AbstractModelerPropertySection$3.doExecuteWithResult(AbstractModelerPropertySection.java:584)
org.eclipse.gmf.runtime.emf.commands.core.command.AbstractTransactionalCommand.doExecute(AbstractTransactionalCommand.java:247)
org.eclipse.emf.workspace.AbstractEMFOperation.execute(AbstractEMFOperation.java:150)
org.eclipse.gmf.runtime.common.core.command.CompositeCommand.doExecuteWithResult(CompositeCommand.java:403)
org.eclipse.gmf.runtime.common.core.command.AbstractCommand.execute(AbstractCommand.java:135)
org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:511)
org.eclipse.gmf.runtime.diagram.ui.properties.sections.AbstractModelerPropertySection.executeAsCompositeCommand(AbstractModelerPropertySection.java:315)
com.sybase.uep.tooling.common.ui.property.view.UEPPropertySheetSection.executeAsCompositeCommand(UEPPropertySheetSection.java:406)
com.sybase.uep.tooling.common.ui.property.view.UEPPropertySheetSection.runAsCommands(UEPPropertySheetSection.java:389)
com.sybase.uep.tooling.ui.properties.sheets.mbo.MBOAttributesBoundMappingPropertySection.runAsCommands(MBOAttributesBoundMappingPropertySection.java:583)
com.sybase.uep.tooling.ui.tableviewer.common.editingsupports.PropertyViewCommandDelegate.runInCommand(PropertyViewCommandDelegate.java:48)
com.sybase.uep.tooling.ui.ModelsUtil$6.run(ModelsUtil.java:1039)
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Edited by: Jenny Bachmann on Feb 8, 2011 6:29 AM

Hi Jenny,
I can't remember what the issue exactly is but I think it's related to one of the data types used in the returned structure.
In any case it's probably a good idea to create your own RFC enabled function module to call the 3 standard function modules instead of calling them one after the other. This way you will avoid unnecessary network communication and you have more control on the data that is exchanged.
Regards,
Pierre

QRFC & tRFC Errors at the time of Production

Hi all,
If i got the qRFc 0r tRFC Errors in PRD system, then do we generally release those queues manually by going SMQ1 & smq2 and for tRFC Errors SM58 or do we schedule the STD programs to clear those strucked queues???
Dont provide any Blogs plzzzz
Regards
Suman

Hi
1) clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
2)You may need to re-register your queues.
Follow SXMB_ADM -> Manage Queues -> Deregister Queues
Afterwards, re-register the queues and activate from the same screen
3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
a double click on the entry shall take you to detailed list.
if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
Now go to SMQ3, right click on the queue and give Restore LUW.
6)this basically means tht message is waiting in the queue.
in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

"COMMUNICATION FAILURE" during JCo call. Error opening RFC connection

Hi
I am trying the following scenario
/people/varadharajan.krishnasamy/blog/2007/05/11/how-to-use-digital-certificates-for-signing-encrypting-messages-in-xi
In SM 59 test connection of AI_RUNTIME_JCOSERVER throws error " Error opening RFC connection"
Do I need to activate any service in SICF and do I need to do any IE configuration (sxmb_adm)
pls let me know the steps to solve this
thanks
manian

Hi Manian,
pls chk with ABAP system tha tu have given the correct PWD and CLNT No
Use
You need to create the following RFC destinations with both transaction SM59 (ABAP) and the Visual Administrator (Java):
●     AI_RUNTIME_JCOSERVER
Points from the Integration Server to the mapping runtime. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used for the mapping runtime, value mapping, and the exchange profile).
●     AI_DIRECTORY_JCOSERVER
Points from the Integration Server to the Integration Builder. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used to refresh the runtime cache).
●     LCRSAPRFC
The RFC destination LCRSAPRFC is required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile.
●     SAPSLDAPI
The RFC destination SAPSLDAPI is required for the connection to the SLD. It is used by the ABAP API.
Depending on your client settings, it may be necessary to log on to your Integration Server host as SAP system user with the authorization to maintain customizing tables and to release transport orders.
User SAP* or DDIC does not have these authorizations
Thanx
Sampath

JCO monitor creation error

Hi all,
I'm trying to configure the Mobile administrator. For this I've followed all the steps in the SAP library regarding this.
But, when I try to activate the two JCO monitors: ME_MONITORS_MODELDATA_DEST and ME_MONITORS_METADATA_DEST, I simply can't do it.
The system dosn't give any error message but although I try to create them and follow all the screens, at the end the status of both of them remains in red (not created).
What could be the error??
Thank you!!
Best Regards,

Thank you!!
With this guide I managed to start the JCO monitors succesfully. However, there is a step that this guide does not include to correctly configure the Mobile administrator and is the JRA configuration.
After all I configurated correctly the Mobile Administrator.
Thanks again.
Best regards,

Rfc Jco communication channel error in BPM integration process

Hi,
when we are processing the records some records are processed succussfully some records does not in integration process view. when we restart the workflow we can able to process the error messages succussfully.
but here not understanding how to reprocesse automatically error messages in the BPM integration process level.
thanks and regads,
krushi.

Hi
re-submission of messages after corrections that were failed
Reconciliation of Messages in BPM
Reconciliation of Messages in BPM Contd. - Restart Workflow

JCO Return Type error for BAPI_GOODSMVT_CREATE

I'm working against a 4.6c instance using the BAPI_GOODSMVT_CREATE to do a 261 movement type. When running through Xacute, I am getting the attached Return message:
<RETURN>
<item>
<TYPE>E</TYPE>
<ID>M3</ID>
<NUMBER>351</NUMBER>
<MESSAGE>Material not maintained in plant 0066</MESSAGE>
<LOG_NO />
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1 />
<MESSAGE_V2>0066</MESSAGE_V2>
<MESSAGE_V3 />
<MESSAGE_V4 />
<PARAMETER>GOODSMVT_ITEM</PARAMETER>
<ROW>1</ROW>
<FIELD />
<SYSTEM>QAS150</SYSTEM>
</item>
</RETURN>
I know for sure that this item is maintained in this plant as I can perform the 261 through SAP GUI and through ABAP. Has anyone else run into this problem? There is an OSS note (570790) for this BAPI, but I think this patch has already been applied.

Hi Rick - thanks for your quick response.
I'm fairly confident I have the right config as I can do other BAPIs without any problems. I did check the material number as well; it is zero padded correctly - again I believe.
I could be wrong. I have someone looking into the patch in the OSS note. Perhaps that is the answer.

Error while deploying the aplication-jco error

Hello Experts,
i know   thousends of questions in jco error. I have followed that threads , still i am getting an error.
Plz help me out from that error.
My EP server is running on was 6.20,
and xi server is running on was 6.40.
what i have done:
I have downloaded fightslist application from sdn.
i have deployed that application to was 6.40.
i created one technical system for abap.
i configured sld.
i entered service name(sapms147 3600/tcp(this is ides(4.7) serversid and port)) in servicefile in was 6.40 machine.
when maintaing jco connections the following error has come:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=mlbpsap06 GROUP=PUBLIC R3NAME=I47 MSSERV=sapmsI47 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapmsI47' unknown TIME        Fri Dec 01 15:27:10 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 MODULE      ninti.c LINE        494 DETAIL      NiPGetServByName2: service 'sapmsI47' not found SYSTEM CALL getservbyname_r COUNTER     7
My doubts are:
1.where i have to enter service i.e which machine (6.40 or 4.7 machine).
2.while creating technicalsystem which product i have to choose).
3while creating jco connection
    whichone i have to choose either dictinory mata data or applicationdata.
    in message server connection which user id & password i have to give means 4.7 userid or xiserver userid & password.
Plz helpme out from this.
Thanks in advance.

Hello Sai,
NWDS is local means which machine i am using.
My EP 6.0 SP2 in 172....202 but it is reunning on was 6.20.(mlbpsap02)
and here was 6.40 ip is 172.....203 IP ,but XI is installed on this server)(mlbpsap03)
and R/3 ECC ip is 172......201.(mlbpsap01)
no sneak preview edition and all.
I have downloaded application(sample flight) in webdynpro.
and i configured sld in 203(cim test connection is successfull) ip.and also entered the service name(sapmsecc 3600/tcp).After entering the service name i restarted the server
and created technical system for abap (and here selectiong products ecc components are not there.)
in webdynpro content admin while maintaing jco , the above error is coming.
i am unable to find where the problem is
the main thing is ep is not in was 6.40
further what i do
and where i enter the host ip and aliases.

JCo & qRFC / IDOC_INBOUND_IN_QUEUE Error

Similar Messages

Maybe you are looking for