RFCadapter error

Hi Gurus,
My scenario is proxy to RFC scenario.
Im trying to call the function module in SAP ECC system.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZAP_MB_PO_IDOC_POST in remote system (RfcClient[CC_RFC_RECEIVER_PECOS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Type conflict when calling a function module.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZAP_MB_PO_IDOC_POST in remote system (RfcClient[CC_RFC_RECEIVER_PECOS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Type conflict when calling a function module.
Can you please help me why this error is occuring when calling the function module in SAP system.
Any help appreciated.
thanks,
Jay.

Hi,
Have you tried changing the pool size settings for the JCO connection too?? You can find it under Content Administration --> Maintain JCO connections. And check it JCOu2019s Properly working or not. Just Ping and Text.
I hope this problem is comming by JCO's. Please check it SAP Note 1121978.
Hope this helps!!
Regards
Vijay K
Edited by: VijaySAPEP on Sep 21, 2011 2:59 PM

Similar Messages

  • RfcAdapter-Reciver error in channel GeneratedReceiverChannel_RFC

    Hi all,
    We had setup up ALM in XI/PI, sometime we receive alert with below content:
    Blank in below fields:
    SXMS_ERROR_CODE, SXMS_ERROR_CAT, SXMS_MSG_GUID
    SXMS_FROM_SERVICE, SXMS_FROM_INTERFACE, SXMS_TO_INTERFACE
    Have values in below fields:
    SXMS_TO_SERVICE = QA3CLNT100 (the ERP side business system)
    SXMS_TO_ADAPTER_TYPE = RFC
    SXMS_TO_ADAPTER_ERRTXT = RfcAdapter-Reciver error in channel GeneratedReceiverChannel_RFC: can not instan
    Except this alert message, there is nothing wrong on message processing between XI/PI and ERP.  May I know is this an alert about temporary error (outage) on communication channel when ERP is performing short maintenance task?  If yes, can this sort of alert be avoided?  Thanks.
    Regards,
    Donald

    Hi,
    you can modify your alert rule for throwing alert only on msg mapping error on integration engine........in this way, no alert will be generated when your ERP system is under modification but in this case, no error will be generated if there is any error in your reciver RFC comm channel........i think you will get error only if ERP is down, once your RFC comm chanel parameters are okay in the initial configuration..... so for ERP down error, you can configure CCMS and get an alert for it.............in this way, you can avoid the above type of alert for your reciver RFC comm channel.......
    Regards,
    Rajeev Gupta

  • RfcAdapter: receiver channel has static errors: can not instantiate RfcPool

    HI,
    While transferring the project from SAP system to PRIMVERA (third party system) system, iam getting the following error:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=192.168.215.138 SYSNR=02 GWHOST=192.168.215.138 GWSERV=sapgw02 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '192.168.215.138apgw02' not reached TIME Sun May 01 06:10:03 2011 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 3133 DETAIL NiPConnect2: 192.168.215.138:3302 SYSTEM CALL connect ERRNO 10060 ERRNO TEXT WSAETIMEDOUT: Connection timed out COUNTER
    experts, kindly help me out in resolving this issue.
    Regards,
    Sai

    partner '192.168.215.138apgw02' not reached
    Well if you ask me, theres something seriuosly wrong with above "partner", review the config of the RFC/JCO,
    also you could add more details as above info on its own is not enough to give you and objective answer
    Regards
    Juan

  • Internal server error while raising a claim request.

    Dear All,
    I am using claims and we have implemented badi for finding the approver and sending the request.
    Here after implementing the Badi, i am getting internal server error as this.
    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:
       com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error in module RSQL of the database interface., error key: RFC_ERROR_SYSTEM_FAILURE
        at java.lang.Throwable.<init>(Throwable.java:179)
        at java.lang.Error.<init>(Error.java:37)
        at com.sap.pcuigp.xssfpm.java.FPMRuntimeException.<init>(FPMRuntimeException.java:46)
        at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
        at com.sap.ess.in.claims.fc.FcPowerClaims.callRFC_Emp_Action(FcPowerClaims.java:421)
        ... 53 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB5; QS 4.2.2.3; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)
    Version null
    DOM version null
    Client Type msie7
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:14:54[UTC], changelist=499141, host=pwdfm101), build date: Fri Mar 13 11:09:42 IST 2009
    J2EE Engine 7.00 patchlevel 112614.44
    Java VM Classic VM, version:1.4, vendor: IBM Corporation
    Operating system OS/400, version: V6R1M0, architecture: PowerPC
    Session & Other
    Session Locale en_US
    Time of Failure Thu Apr 23 18:47:54 IST 2009 (Java Time: 1240492674705)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:31[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:37[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0017.20060719095755.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:48:53[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:06[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:40[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:34[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0017.20060719095619.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:58:48[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0017.20080801093120.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:03:59[UTC], changelist=495368, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
    SapWebDynproGenerationCore 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:12[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:31[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0017.20061002105236.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:01:37[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0017.20060719095755.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:48:53[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:06[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:40[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0017.20061002105432.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:49:34[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0017.20060719095619.0000 (release=645_VAL_REL, buildtime=2008-09-17:12:58:48[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0017.20080801093120.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:03:59[UTC], changelist=495368, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
    SapWebDynproGenerationCore 7.0017.20080801093115.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:07:12[UTC], changelist=495367, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0017.20080829103545.0000 (release=645_VAL_REL, buildtime=2008-09-17:13:16:41[UTC], changelist=499141, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error in module RSQL of the database interface., error key: RFC_ERROR_SYSTEM_FAILURE
         at java.lang.Throwable.<init>(Throwable.java:179)
         at java.lang.Exception.<init>(Exception.java:29)
         at com.sap.exception.BaseException.<init>(BaseException.java:145)
         at com.sap.tc.cmi.exception.CMIException.<init>(CMIException.java:65)
         at com.sap.tc.webdynpro.progmodel.model.api.WDModelException.<init>(WDModelException.java:68)
         at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDRFCException.<init>(WDRFCException.java:54)
         at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDExecuteRFCException.<init>(WDExecuteRFCException.java:57)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:71)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:43)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.ess.in.claims.fc.FcPowerClaims.callRFC_Emp_Action(FcPowerClaims.java:392)
         at com.sap.ess.in.claims.fc.FcPowerClaims.performEmpAction(FcPowerClaims.java:1988)
         at com.sap.ess.in.claims.fc.wdp.InternalFcPowerClaims.performEmpAction(InternalFcPowerClaims.java:8022)
         at com.sap.ess.in.claims.fc.FcPowerClaimsInterface.performEmpOperation(FcPowerClaimsInterface.java:398)
         at com.sap.ess.in.claims.fc.wdp.InternalFcPowerClaimsInterface.performEmpOperation(InternalFcPowerClaimsInterface.java:3440)
         at com.sap.ess.in.claims.fc.wdp.InternalFcPowerClaimsInterface$External.performEmpOperation(InternalFcPowerClaimsInterface.java:3616)
         at com.sap.ess.in.claims.vc.powerrequestdetail.VcPowerRequestDetail.aH_Send(VcPowerRequestDetail.java:739)
         at com.sap.ess.in.claims.vc.powerrequestdetail.wdp.InternalVcPowerRequestDetail.aH_Send(InternalVcPowerRequestDetail.java:2947)
         at com.sap.ess.in.claims.vc.powerrequestdetail.VcPowerRequestDetailView.onActionSend(VcPowerRequestDetailView.java:1423)
         at com.sap.ess.in.claims.vc.powerrequestdetail.wdp.InternalVcPowerRequestDetailView.wdInvokeEventHandler(InternalVcPowerRequestDetailView.java:1650)
         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.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         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.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
         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: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 com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Error in module RSQL of the database interface., error key: RFC_ERROR_SYSTEM_FAILURE
         at java.lang.Throwable.<init>(Throwable.java:179)
         at java.lang.Exception.<init>(Exception.java:29)
         at com.sap.aii.util.misc.api.BaseException.<init>(BaseException.java:96)
         at com.sap.aii.proxy.framework.core.FaultException.<init>(FaultException.java:34)
         at com.sap.aii.proxy.framework.core.SystemFaultException.<init>(SystemFaultException.java:29)
         at com.sap.aii.proxy.framework.core.BaseProxyException.<init>(BaseProxyException.java:39)
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.ess.in.claims.newmodel.HRXSS_IN_NEWCLMS_MODEL.hrxss_In_Cl_Emp_Action(HRXSS_IN_NEWCLMS_MODEL.java:475)
         at com.sap.ess.in.claims.newmodel.Hrxss_In_Cl_Emp_Action_Input.doExecute(Hrxss_In_Cl_Emp_Action_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 54 more
    Appreciate any quicker help on this.
    Regards,
    Rajasekar

    Hi,
    Can u give me full details ....
    What is the name of the BADI and ....coding tht you have written in method.
    Cheers
    Vivek

  • Error while sending data from XI to BI System

    Hello Friends,
    I m facing an error while sending data from XI to BI. XI is successfully recived data from FTP.
    Given error i faced out in communication channel monitoring:-
    Receiver channel 'POSDMLog_Receiver' for party '', service 'Busys_POSDM'
    Error 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: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
    Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1
    LOCATION CPIC (TCP/IP) on local host with Unicode
    ERROR partner '10.1.45.35:sapgw01' not reached
    TIME Fri Apr 16 08:15:18 2010
    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 2
    Error displaying in message monitoring:-
    Exception caught by adapter framework: 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: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM  TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '10.1.45.35:sapgw01' not reached TIME        Fri Apr 16 08:15:18 2010 RELEASE     70
    Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: 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: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM  TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '10.1.45.35:sapgw01' not reached TIME.
    Kindly suggest me & provide details of error.
    Regards,
    Narendra

    Hi Narendra,
    Message is clearly showing that your system is not reachable
    102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached
    Please check to ping the BI server  IP 10.1.45.35 from your XI server , in case its working you can check telnet to SAP standard port like 3201/3601/3301/3901 etc.
    It seems to be connectivity issue only.
    Make sure your both the systems are up and running.
    Revert back after checking above stuff.
    Regards,
    Gagan Deep Kaushal

  • Error in ABAP Proxy generation?

    hai pals,
    my intention is to push the data from XI to SAPBWSEM system throgh an ABAP PROXY.
           but , here i got an error which i already mentioned in the forum, that is " no connection to integration builder(only local data visible) ".
            i went to the integration engine configuration in "SXMB_ADM" transaction in SAPBWSEM server.
            in sxmb_adm transaction ,the system ask for the "specific configuration data-catagory" like TUNNING , MONITOR,RUNTIME,TRACELOG,DEBUG and RFCADAPTER.
             im little bit confused in choosing the "catagory of configuration data".so can u pls help me in this error.
    with cheers.
    rajesh

    Did you create the RFC Destinations LCRSAPRFC and SAPSLDAPI to point your SLD ? If not do that.
    Then create RFC Dest INTEGRATION_DIRECTORY_HMI type H. Look at your XI box and make these 3 RFC Dests.
    Then use the following thread to fix your IFR_ADDRESS
    Values for table SPROXSET
    regards
    SKM

  • PI 7.0: Error when calling an adapter by using communication channel

    Hello Experts,
    We have a mapping scenario for ERP -> PI -> web service. Few details from ERP will be sent via PI to Web service. 
    Once the web service authenticates, token and sign will be generated. Here an RFC adapter is  used for configuring the RFC receiver communication channel and provided the ERP system logon details at the RFC client parameter.
    An error is received as mentioned below.
    Error while lookup Exception during processing the payload.Problem when calling an adapter by using communication channel CC_Rcvr_RFC_Lookup_TokenSign (Party: , Service: BS_QV6_700, Object ID: 54e904ebf3d7382a84a0f83cd292b810)
    XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>'. com.sap.aii.mapping.lookup.LookupException
    The logon details in RFC parameter are corrected. Re-activated the the communication channel and refreshed the cache.
    But still the error is not resolved.Please let me know if there is anything else i need to check.
    Thanks in advance.
    Regards,
    Sri

    Hello,
    You could also check note 730870  FAQ XI 3.0/ PI 7.0/ PI 7.1 RFC Adapter
    Q 16:
    While sending a message to the RfcAdapter the error "...functiontemplate from repository was <null>" is shown. Which reasons are possible?
    Regards,
    Sarah

  • Error in RFC adapter

    Hello All,
    I am working on File to RFC Asynchronous Scenario. I am getting Error in M receiver RFC adapter. It is displaying in Adapter Monitoring as
    <b>- Error: 2007-10-03 05:28:38 EDT: Message processed for interface BAPI_CUSTOMER_CREATEFROMDATA1: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was</b>
    Can any help how to resolve this.
    Regards

    Hi,
    The RfcAdapter trys to find a Sender Agreement for this RFC call but the lookup failes. The values used for this lookup are:
    •     Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
    •     Sender Interface: The name of the RFC function module.
    •     Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
    •     Receiver Party/Receiver Service: These fields are empty. This will match the wildcard '*'.
    Chilla

  • RFC Error: A remote host refused an attempted connect operation

    Hi I received strange kind of error..
    Have anyone of you seen something like this before?
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (**) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=logon*.*.com GROUP=SPACE R3NAME=2 MSSERV=sapms2 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '.*..*:sapms*8' not reached TIME Sat Feb 11 20:37:58 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 3147 DETAIL NiPConnect2: *.*..*:*** SYSTEM CALL connect ERRNO 79 ERRNO TEXT A remote host refused an attempted connect operation. COUNTER 8</SAP:AdditionalText>
      <SAP:Stack />

    Hi,
    MSHOST=logon**.*.com is name server, but it can be recognized as in message is also part "on local host with Unicode ERROR partner '.*..**:" where *.*... is IP address..
    That problem occurred after some patches were implemented.
    @2.) I can't change it to ABAP proxy
    M.

  • Error: java.lang.NullPointerException

    Hi,
    In my File - RFC - File scenario (PI 7.1), i am facing the error in the communication channel
    File processing failed with java.lang.NullPointerException
    But in SXMB_MONI it the status shows Processed Successfully.
    From File to RFc it displays all the details like Sender Namespace, Sender Interface, Receiver component etc.
             RFC to File it doesn't display any details other than Message ID.
    The following steps are executed in RFc to File message:
        Inbound Message ( CENTRAL )
       XML Validation Inbound Channel Response
       Request Message Mapping
       XML Validation Outbound Channel Response
    these steps also contain the output file format in xml structure:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:MT_LOTUSNOTES_UNIFORM_FILE_RESP xmlns:ns1="http://lotusnotes.uniform.com">
    - <ITAB_OUT>
    - <item>
      <STR>20000000|3022|-10.25|09.11.2009|Testing 1111|</STR>
      </item>
    - <item>
      <STR>20000000|3022|800.99|10.11.2009|Testing 22222|</STR>
      </item>
    - <item>
      <STR>20000015|3022|200|09.11.2009|Testing 333333|</STR>
      </item>
      </ITAB_OUT>
      </ns1:MT_LOTUSNOTES_UNIFORM_FILE_RESP>
    pls let me know how to solve this error

    Hi,
    Please see the audit log
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:21 Information Channel CC_LOTUSNOTES_UNIFORM_SND_FILE: Converted complete file content to XML format.
    2009-12-08 07:18:21 Information Send text file  "/home/ftp/home/ftpusr/test/in/20091109PYI_UNIFOR.txt", size 402, encoding ISO8859-1with QoS BE.
    2009-12-08 07:18:21 Information MP: entering1
    2009-12-08 07:18:21 Information MP: processing local module localejbs/AF_Modules/RequestResponseBean
    2009-12-08 07:18:21 Information RRB: entering RequestResponseBean
    2009-12-08 07:18:21 Information RRB: passing through ...
    2009-12-08 07:18:21 Information RRB: leaving RequestResponseBean
    2009-12-08 07:18:21 Information MP: processing local module localejbs/CallSapAdapter
    2009-12-08 07:18:21 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
    2009-12-08 07:18:21 Information Trying to put the message into the call queue.
       Page 1 / 4 *
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:21 Information Message successfully put into the queue.
    2009-12-08 07:18:21 Information The message was successfully retrieved from the call queue.
    2009-12-08 07:18:21 Information The message status was set to DLNG.
    2009-12-08 07:18:22 Information The message was successfully received by the messaging system. Protocol: XI URL: http://sdnpi1.sap.spoolzgroupit:50800/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2009-12-08 07:18:22 Information Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
    2009-12-08 07:18:22 Information Message successfully put into the queue.
    2009-12-08 07:18:22 Information The message was successfully retrieved from the request queue.
    2009-12-08 07:18:22 Information The message status was set to DLNG.
    2009-12-08 07:18:22 Information Delivering to channel: CC_LOTUSNOTES_UNIFORM_RCV_RFC
    2009-12-08 07:18:22 Information MP: entering1
       Page 2 / 4 *
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:22 Information MP: processing local module localejbs/RfcAFBean
    2009-12-08 07:18:22 Information RfcAdapter received a synchronous message. Trying to send sRFC for Z_PI_LOTUSNOTES_UNIFORM.
    2009-12-08 07:18:22 Information RfcAdapter received a synchronous message. Trying to send sRFC for J2EE_GUEST.
    2009-12-08 07:18:22 Information MP: leaving
    2009-12-08 07:18:22 Information The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
    2009-12-08 07:18:22 Information The message status was set to DLVD.
    2009-12-08 07:18:22 Information The application sent the message synchronously using connection File_http://sap.com/xi/XI/System. Returning to application.
    2009-12-08 07:18:22 Information MP: processing local module localejbs/AF_Modules/ResponseOnewayBean
    2009-12-08 07:18:22 Information The message was successfully transmitted to endpoint http://sdnpi1.sap.spoolzgroupit:50800/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System.
    2009-12-08 07:18:22 Information The message status was set to DLVD.
       Page 3 / 4 *
    Audit Log for Message: 3c5fbcee-4b17-4afe-0ea5-a6064f47d377
    Time Stamp Type Description
    2009-12-08 07:18:22 Information MP: leaving
    *2009-12-08 07:18:22 Error File processing failed with java.lang.NullPointerException:  *
       Page 4 / 4
    Edited by: jjma1706 on Dec 8, 2009 9:05 AM

  • Server Error, test on WSNavigator

    Hi Guys! I have the scenary SOAP to RFC. The service interface is synchronous.
    I am testing the WS since WS Navigator,
    1)Testing without input data ---> response "Server Error"
        Since se37, I execute the RFC and the response is correct.
    Since Runtime Workbench, I see the message request XML ok,  and the message response not created.
    Audit Log:
    2011-07-21 11:34:36 Information RfcAdapter received a synchronous message. Trying to send sRFC for J2EE_GUEST.
    2011-07-21 11:34:36 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: Mapping failed using connection SOAP_http://sap.com/xi/XI/System.
    2011-07-21 11:34:36 Error The message status was set to FAIL.
    2)Testing with input data ---> response "OK XML"
    I need a tips in where modify the mapping in the case 1)?

    Hi. I resolved the question, the data type response was changed becouse the cardinality wrong. Then, I updated the message mapping response and all ok.
    DT_RESPONSE_old
    ADDRESS
              ADDR1
                     ADDR2   1..Unbounded   <<<<------ Error
                              COUNTRY
    DT_RESPONSE_new
    ADDRESS
              ADDR1   0..Unbounded
                         COUNTRY
    Thanks all for your replies!!!
    Edited by: ecruz2010 on Jul 22, 2011 2:59 PM
    Edited by: ecruz2010 on Jul 22, 2011 3:13 PM

  • Exception caught by adapter framework: RfcAdapter: receiver channel not in

    Hi friends,
    I am  doing a file-RFC-file scenario. This is based on the blog: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit The company ID is sent to the RFC through a xml file. RFC will return the company details which will be written again into a xml file.
    My source file is getting picked up. But while sending the company ID to the RFC, i am getting an error. It says: <b>Exception caught by adapter framework: RfcAdapter: receiver channel not in list of running clientPools:</b>. I have checked the RFC and is running perfectly.
    Can anybody help me to solve this error?
    Regards,
    Divija.

    Hi,
    it is better to restart the RFC adapter engine.
    Is this RFC adapter is active in the Adapter Monitoring ?
    Also change the RFC adapter configuration and activate it. Then activate the Receiver Agreement.
    Also refer SAP note -730870 ( question  no 17 and 20)
    Regards,
    Moorthy

  • Synch RFC error

    Hello,
    in one of our BPMs we have to use a synchronous RFC to avoid that a server error is thrown due to a timeout. The RFC triggers an IDOC to be created (we use correlations) but under some conditions there might be no IDOC created and our BPM throws a server error with timeout.
    We have already set the <b>xiadapter.inbound.timeout.default</b> to a higher value to avoid the MessageExpired (INBOUND) error. But now we have this error:
    <b>com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.MessageExpiredException: Message be79b430-aad3-11db-cf2b-001185eb2336(OUTBOUND) expired</b>
    Unfortunately the <b>xiadapter.outbound</b>-Parameters are only for asynch calls. Now, is there another parameter which has to be increased?
    Regards.
    Oliver.

    try implementing this blog - /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
    Should help you solve the reconnect issue. I assume time out should be a direct interferance with the same.

  • Error in pushing a request to R3 System using RFC Adapter

    I am trying to send a request to R3 system using an RFC Adapter as my end point and pointing to
    the Application server of the  R3 box.
    In the Transaction SM58 I see and error saying "<i><b>Exception in handleRequest of server Xmb2RfcService: java.lang.Exception:</b></i>"
    Here are the corresponding details:
    Caller: CENTRALADMIN
    Function Module: SRFC_ADAPTER_SERVICE
    Target System: AI_RFCADAPTER_JCOSERVER
    Host: .... (The XI Server)
    Program: SAPMSSY1
    Clnt: 100
    As per the SRFC_ADAPTER_SERVICE function module, the <i><b>purpose stated so...
    "This function is the glue between the JCo RFC Inbound Adapter and the XMS Pipeline."</b></i>
    By the by the RFC adapter is started and I can see no activity in the log after startup.
    I would really appreciate for any idea/leads in solving this. Thanks.<b></b>

    Here are the details
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Config File for RFC Adapter%%%%%%%%%%%%%%%%%%%%
    RFC ADAPTER CLASSNAME FOR ADAPTER ENGINE
    classname=com.sap.aii.rfcadapter.core.RfcAdapterModule
    RFC ADAPTER CONFIGURATION PROPERTIES
    Tue Jan 21 13:27:43 CET 2003
    1. GENERAL SECTION
      1.1 trace settings
    RfcAdapter.trace=2
    -> adapter trace level 0 = none
                           1 = error
                           2 = standard
                           3 = request
                           4 = payload
                           5 = binary payload outbound
    #RfcAdapter.traceStack=0
    #RfcAdapter.listenException=0
    #RfcAdapter.listenState=0
    -> additional trace switches (in general not needed)
    RfcAdapter.traceFile=./LogFiles/Adapter_rfc.log
    -> name of trace file (traces to stdout if not specified)
       NOTE: in a productive environment, the trace file should be written to the
             log-file directory of the Adapter Engine
      1.2 connectivity settings
    RfcAdapter.registerInbound=sourceBackendXD1
    -> space-delimited list of logical names for inbound R/3 systems subsections.
       The adapter will register with all R/3 systems defined in this list and
       those systems can send RFC requests into the XI via an RFC destination
       that has to be setup in SM59 to point to the RFC Adapter
    RfcAdapter.accessInbound=toXmb
    -> logical name for inbound access to XMB subsection
    RfcAdapter.registerOutbound=fromXmb
    -> logical name for outbound access from XMB subsection
    RfcAdapter.accessOutbound=targetBackend
    -> space-delimited list of logical names for pre-allocated outbound R/3 systems subsections.
       This is an option to speed up connection setup during request processing. The RFC Adapter
       preallocates sessions to all listed R/3 systems.
    RfcAdapter.clientCloseConn=1
    -> close calling connections after call (1) or just reset session (0)
       NOTE: the reset mechanism is slightly faster for request processing. However, it does
             not re-connect after a target system shutdown and hence requires a restart of the
             RFC Adapter in such a situation.
    #RfcAdapter.maxDynPools=128
    -> maximum number of dynamically allocated client pools to access outbound R/3 systems
    #RfcAdapter.minDynPoolSize=4
    -> initial number of clients in dynamically allocated client pools
    #RfcAdapter.incDynPoolSize=4
    -> increment number of clients in dynamically allocated client pools
    #RfcAdapter.maxDynPoolSize=64
    -> maximum number of clients in dynamically allocated client pools
    2. SUBSECTION FOR REGISTRATION TO CLIENT APPLICATION SYSTEMS
    (one subsection per incoming R/3 system; requires callback service user for repository access)
    RfcAdapter.sourceBackendXD1.host=db03
    RfcAdapter.sourceBackendXD1.sysnr=00
    RfcAdapter.sourceBackendXD1.progid=Rfc2XmbService
    -> recommended is: RfcAdapter.sourceBackend.progid=Rfc2XmbService
    RfcAdapter.sourceBackendXD1.poolsize=5
    RfcAdapter.sourceBackendXD1.unicode=1
    -> source system is Unicode installation (1) or not (0)
    RfcAdapter.sourceBackendXD1.client=500
    RfcAdapter.sourceBackendXD1.user=XIAPPLUSER
    RfcAdapter.sourceBackendXD1.passwd=********
    RfcAdapter.sourceBackendXD1.lang=EN
    RfcAdapter.sourceBackendXD1.trace=2
    -> enable RFC trace for this connection (1) or not (0)
    #RfcAdapter.sourceBackendXD1.sncName=<SNC_name_of_adapter>
    -> e.g. RfcAdapter.sourceBackendXD1.sncName=p:CN=USERNAME, O=ORGNAME, C=DE
    #RfcAdapter.sourceBackendXD1.sncLib=<SNC_library_path>
    -> e.g. on Win2K: RfcAdapter.sourceBackendXD1.sncLib=C:
    Program Files
    SECUDE
    SECUDE for R3
    secude.dll
    #RfcAdapter.sourceBackendXD1.sncQop=<SNC_quality_of_protection>
    -> 1,2,3,8,9 e.g. RfcAdapter.sourceBackendXD1.sncQop=1
    #RfcAdapter.sourceBackendXD1.sncAcl=<SNC_access_control_list>
    -> logical names for allowed callers e.g. RfcAdapter.sourceBackend.sncAcl=peerB6A peerB6Q
    #RfcAdapter.sourceBackendXD1.sncAcl.peerB6A=p:CN=B6A, O=SAP-AG, C=DE
    #RfcAdapter.sourceBackendXD1.sncAcl.peerB6Q=p:CN=B6Q, O=SAP-AG, C=DE
    -> details for peer ACL lists
    3. SUBSECTION FOR ACCESS TO XMB INBOUND RFC SERVICE
    (only one entry possible)
    RfcAdapter.toXmb.host=web03
    RfcAdapter.toXmb.sysnr=00
    RfcAdapter.toXmb.poolsize=5
    RfcAdapter.toXmb.client=100
    RfcAdapter.toXmb.user=XIAPPLUSER
    RfcAdapter.toXmb.passwd=******
    RfcAdapter.toXmb.lang=EN
    RfcAdapter.toXmb.trace=2
    4. SUBSECTION FOR REGISTRATION OF XMB OUTBOUND RFC SERVICE
    (only one entry possible)
    RfcAdapter.fromXmb.host=web03
    RfcAdapter.fromXmb.sysnr=00
    RfcAdapter.fromXmb.progid=Xmb2RfcService
    this value must be in sync with Program Id setting for AI_RFCADAPTER_JCOSERVER in SM59
    RfcAdapter.fromXmb.poolsize=5
    RfcAdapter.fromXmb.unicode=1
    -> source system is Unicode installation (1) or not (0)
    RfcAdapter.fromXmb.trace=2
    5. SUBSECTION FOR ACCESS TO SERVER APPLICATION SYSTEMS
    (one subsection per outgoing R/3 system; pre-allocated connection pools via service user)
    RfcAdapter.targetBackend.host=db03
    RfcAdapter.targetBackend.sysnr=00
    RfcAdapter.targetBackend.poolsize=5
    RfcAdapter.targetBackend.client=500
    RfcAdapter.targetBackend.user=XIAPPLUSER
    RfcAdapter.targetBackend.passwd=*******
    RfcAdapter.targetBackend.lang=EN
    RfcAdapter.targetBackend.trace=2
    END OF RFC ADAPTER CONFIGURATION PROPERTIES
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%Log data for the adapter%%%%%%%%%%%%%%%%%%%%%%%%%%
    Fri Sep 24 09:50:09 EDT 2004 *****
    09:50:09 (6011): RFC adapter initialized
    09:50:09 (6031): RFC adapter started
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%SM59 entries on the XI box%%%%%%%%%%%%%%%%%%%%%%%%%%
    Name: AI_RFCADAPTER_JCOSERVER
    Program ID: Xmb2RfcService
    Action Type: Registered Server Program
    Gateway: web03  (Local XI box)
    Gateway Service: sapgw00 (00 is the system number)
    Name: XI_SERVER
    Program ID: Rfc2XmbService
    Action Type: Registered Server Program
    Gateway: db03  (R3 box)
    Gateway Service: sapgw00 (00 is the system number for R3)
    Both the entries are tested fine.

  • Error in RFC Receiver Adapter: functiontemplate from repository

    Hi Experts,
    i am working on JDBC -> RFC Scenario, JDBC Sender Adapter is working fine, but RFC Receiver Adapter is throwing this error message... can some one help me to solve this issue...
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    Thanks
    Srikanth

    Possible reasons are
    The XML document, which was send to the RfcAdapter, is not a RFC-XML document. So the root element name of this document is not the name of a function module and thus can't be found in the metadata repository.
    The metadata repository doesn't contain an entry for this function module name. Normally the metadata repository will be an R/3 system and it's function module repository can be searched with transaction code SE37.
    Here my suggestion is, if you are using Java/xslt mapping, write your code in line with result structure of your mapping instead source pay load structure. May be helpful.
    Cheers
    Madhu

Maybe you are looking for