Error with RFC receiver channel

Hi,
Getting this below error for receiver RFC channel. Can anyone please look into this error urgently.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.adapter.rfc.core.config.RfcConfig.getChannel() of a null object returned from com.sap.aii.adapter.rfc.core.client.RfcClientPool.getConfig()

Hi,
Restarted but no result. Getting another error :
Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling Z_SD_XI_BAPI_CREATE_VA_SLSORD3 in remote system (RfcClient[CC_RFC_Z_BRONZE_VA_RCVR]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Could not open file /usr/sap/XP3/interfaces/va/br_vaout_20140401_04204.
I do not understand why RFC receiver channel is giving this error.
Can any one please look into it on priority.I need it to get resolved very soon.
Thanks

Similar Messages

  • Error with JMS receiver channel

    Hi,
    We have a scenario in which Order response will be sent from ECC to WebLogic (JMS system) through PI.
    After the restart of JMS, we are facing issues with JMS receiver channel.
    Some of the responses are delivered, and for few we have the error as described below.
    Also, one of the cluster node of the JMS receiver channel has the below error.
    Please anybody throw some light on this.
    Error description:
    " Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Pending message discovered: dfff2e2b-80f5-94f1-a068-001cc4d99b3e.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling  channel parameter to 'Bypass' and restart the message afterwards.. "
    Thanks in advance.
    Regards
    Bhanu Tiruveedula.

    Hello Bhanu,
    we have been getting this error from long time with JMS channel but no solution except changing the configuration so that it can throw exception and move on.
    we have also noticed that this happens for some time and then gets resolved automatically. so it seems to be some data which is not expectable by jms channel.
    regards,
    Ratna

  • Error in RFC Receiver Channel

    Hi Experts!
    In my scenarios i am using Receiver RFC for Look up. The RFC Channel is working fine in Dev server after we transport it to the QA. Now we are getting an error message :GenericRFCChannel" is not found in SXMB_moni.
    ID we have made the new configurations. When i have tested in IE the RFC is working fine. so we getting a strange why it is not working while runtime.
    Also i am having one doubt, Is it is mandatory to give the SAP BI details in the Software Component in the IE.Here our RFC are in SAP BI system.
    Pls give me some ideas to debug this issue. Thanks in Advance.
    Regard's
    Preethi.

    Hai !
    I have made a dummy changes nad reactive the channel even now i am getting the error as
    Give me some input to debug this issue. Pls.
    <Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
    <Trace level="1" type="T">Mapping-Object-Id:995C3CC70F88314694147FC81DEB10D0 </Trace>
    <Trace level="1" type="T">Mapping-SWCV:E179B290F08511DFAAACDF94C0A80049 </Trace>
    <Trace level="1" type="T">Mapping-Step:1 </Trace>
    <Trace level="1" type="T">Mapping-Type:JAVA_JDK </Trace>
    <Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_dealTicket_OPS_iOam_MM2_ </Trace>
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_dealTicket_OPS_iOam_MM2_
    Thrown:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: com.sap.aii.mapping.api.UndefinedParameterException: The input-parameter GeneratedReceiverChannel_RFC does not exist.at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:148)
    at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:626)
    at com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:92)
    at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60)
    at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87)
    at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:71)
    at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:119)
    at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:72)
    at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
    at sun.reflect.GeneratedMethodAccessor555_10000.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy587_10000.processFunction(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183)
    at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:269)
    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:152)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused by: com.sap.aii.mapping.api.UndefinedParameterException: The input-parameter GeneratedReceiverChannel_RFC does not exist.
    at com.sap.aii.ib.server.mapping.execution.MappingParametrization$InputParametersImpl.getValue(MappingParametrization.java:84)
    at com.sap.aii.ib.server.mapping.execution.MappingParametrization$InputParametersImpl.getValue(MappingParametrization.java:71)
    at com.sap.xi.tf._dealTicket_OPS_iOam_MM2_.__CreateStructures(_dealTicket_OPS_iOam_MM2_.java:276)
    at com.sap.aii.mappingtool.tf7.AMappingProgram.preStart(AMappingProgram.java:307)
    at com.sap.xi.tf._dealTicket_OPS_iOam_MM2_.preStart(_dealTicket_OPS_iOam_MM2_.java:802)
    at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:489)
    at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133)
    ... 40 more

  • "Error establishing socket" error on JDBC Receiver Channel.

    Dear All,
    Scenario: Soap to JDBC.
    I m getting error on JDBC Receiver Channel. messages are processed succesfully on ABAP Stack and receiver channel is on below error:
    ERROR : Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:microsoft:sqlserver://156.5.202.194:3312;DatabaseName=ODW': SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
    Note: i already tested another interface with this same IP and it was fine with different port.
    jdbc:microsoft:sqlserver://IP:PORT;DatabaseName=Name
    Regards,
    Manikandan

    and it was fine with different port
    socket exception is (always) related to port....did you check with the network team about this new Port?

  • Error in File Receiver Channel

    Dear All,
    I am Getting below error in File Receiver Channel.
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: User ABC cannot log in.
    Regards,
    Manikandan

    Hi Manikandan,
    Check the username and the password for the FTP server. If the username or the password is wrong then you would be able to post the message.
    Also, there might be a timout issue, In the timeout parameter enter some value.
    Ref: FTP Server connection Problem
    Check and update us.
    Thanks,

  • Error with the Receiver JMS Adapter (Connection On-Demand feature)

    Hi,
    In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
    Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
    Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
    The message status was set to WAIT.
    Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
    Any idea?
    PI 7.1 EHP1
    Thanks,
    Martin
    /people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
    Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

    Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

  • Error in RFC Receiver adapter

    Hi,
    I am trying to send data into sap R/3 system from SAP XI 3.0 and I am using RFC adapter for this purpose. When I configured the receiver RFC adapter I am getting the following error in SXMB_MONI:
    No receiver agreement found for sender ,FILESYS to receiver ,IDS47800,urn:sap-com:document:sap:rfc:functions,BAPI_MATERIAL_SAVEDATA
    Please help us as we are stuck at this Juncture in a very important assignment.
    Thanks and Regards,
    Anil Kumar Damodara

    Hi Anil,
    1.Check whether the receiver agreement is properly configured with the "RFC_Receiver" communication channel.
    2.Check whether the same Receiver agreement("RFC_Receiver" communication channel) is set in the receiver determination configuration.
    check out my article "Validating a Connection Between SAP R/3 and SAP XI with RFC"
    Regards,
    Sridhar Rajan N

  • Error in SOAP Receiver channel

    Hi,
    We are working on IDOC to SOAP Scenario (Connecting to third party).
    We have configured the SOAP Receiver channel with the Target URL and teh corresponding SOAP Action.
    But the SOAP Receiver channel gives the error while processing and sends back the following error message in log :
    "Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Value cannot be null. Parameter name: s."
    Payload seems to look fine in XI and SAP.
    Any help on this ?
    Thanks and regards,
    Vikas

    Hi Vikas,
                Copy the payload from SXMB_MONI  after mapping and check with SOAPGUI or Altova, if it working fine then your payload is good. You can use the WSDL to ganarate and send independent soap request from these tools.
    Besides this IDOC is Asyc, you need to use RequestResponseBean and ResponseOneWayBean to get the response from SOAP.  Check the following  and try to simulate it.
    https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without+BPM%29
    Server was unable to process request. ---> Value cannot be null. Parameter name: s."
    The error specifies that the request has null value, check the parameter specified in the error message and make sure that is not null while you are sending the request.
    Regards,
    Prasanna

  • Error in file receiver channel "Unknown payload format 0 in the message"

    hello
    there is an errror in my receiver file channel with the status "Unknown payload format "
    my channel is file receiver channel.
    we implemented one sap note 1295430 and after that channnel is giving the error.
    Please forward your views.
    thanks.

    Hi there,
    First of all, what TBDL means - It means that the message was successfully delivered from Integration Server and that the messages are handed over to the Messaging System.
    TBDL occurs when the message is put into the receiving queue of the Messaging System.
    What can be done?
    Go to Messaging System receive servlet:
    http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
    If this was executed successfully, then the MS returns HTTP 200 to the Integration Server and the status TBDL moves to DELIVERING (check whether you have authorization to go to the above link).
    --> Log-in to SAP using - XIAPPLUSER & XIAFUSER, and check if they are blocked
    --> Check the messages:
    AF
    com.sap.aii.adapterframework.serviceuser.language
    com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
    com.sap.aii.adapterframework.serviceuser.pwd
    AS
    com.sap.aii.applicationsystem.serviceuser.language
    com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
    com.sap.aii.applicationsystem.serviceuser.pwd
    Also, worth reading - /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Let us know if you have more questions.
    regards,
    Neetesh

  • 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

  • Error in SFTP receiver channel

    Hi,
    We are getting following error while processing the SFTP receiver channel. There is a 64 MB file which need to be processed and while processing we started getting the error log.(We have processed more that 80 MB files from the same channel.)
    The error log:
    Message could not be forwarded to the JCA adapter. Reason: Fatal exception: com.seeburger.xi.connector.queue.TaskBuildException: failed to build seemessage object: java.io.IOException: Retry count limit is reached! Nested error: Error in BackupOutputStream::write( byte, int, int ): Insufficient system resources exist to complete the requested service, failed to build seemessage object: java.io.IOException: Retry count limit is reached! Nested error: Error in BackupOutputStream::write( byte[], int, int ): Insufficient system resources exist to complete the requested service

    Hi,
    Seems lile some issue with your server resources....Please contact your basis team.
    Regards,
    Naveen

  • Error on JDBC Receiver Channel

    Hi,
    I configured a Receiver JDBC Channel to read data from XI own DB. We are using MS SQL Server 2005.
    During the test, I'm running to the following issue. Any ideas on what could be causing this error:
    Log for CC monitor:
    2010-07-20 13:53:20 Success The message was successfully retrieved from the receive queue.
    2010-07-20 13:53:20 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    2010-07-20 13:53:20 Success JDBC adapter receiver channel RPI_LOOKUP_JDBC: processing started; party  , service RPI_DB
    2010-07-20 13:53:20 Success Delivering to channel: RPI_LOOKUP_JDBC
    2010-07-20 13:53:20 Success MP: Processing local module localejbs/CallSapAdapter
    2010-07-20 13:53:20 Success MP: Entering module processor
    2010-07-20 13:53:20 Success select sem_datetime, sem_user, sem_host, sem_flag from "/RPI/T_USER" where sem_user=dom1\user1
    2010-07-20 13:53:20 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'query' (structure 'stmt'): com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name '/RPI/T_USER'.
    2010-07-20 13:53:20 Error Unable to execute statement for table or stored procedure. 'query' (Structure 'stmt') due to com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name '/RPI/T_USER'.
    2010-07-20 13:53:20 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'query' (structure 'stmt'): com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name '/RPI/T_USER'.
    2010-07-20 13:53:20 Error Exception caught by adapter framework: null
    2010-07-20 13:53:20 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'query' (structure 'stmt'): com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name '/RPI/T_USER'..
    2010-07-20 13:53:20 Error The message status set to NDLV.
    Here is the payload:
    <root>
    <stmt>
      <query action="SQL_QUERY">
       <access>
        select sem_datetime, sem_user, sem_host, sem_flag from "/RPI/T_USER" where sem_user='dom1\user1'
       </access>
      </query>
    </stmt>
    </root>
    Connection Settings:
    JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
    Connection: jdbc:sqlserver://hostname.domain.net;databaseName=XI1;
    I did check on the DB and am able to see the table /RPI/T_USER, with 0 records.
    Thanks in advance,
    Sumant.

    <root>
    <stmt>
      <query action="SQL_QUERY">
       <access>
        select sem_datetime, sem_user, sem_host, sem_flag from "/RPI/T_USER" where sem_user='dom1\user1'
       </access>
      </query>
    </stmt>
    </root>
    Not sure if select, from, where will work in lowercase. Instead of query (node under stmt) should you not mention the table_name?
    <root>
    <stmt>
      </RPI/T_USER action="SQL_QUERY">
       <access>
        SELECT sem_datetime, sem_user, sem_host, sem_flag FROM /RPI/T_USER WHERE sem_user='dom1\user1'
       </access>
      <//RPI/T_USER>
    </stmt>
    </root>
    I did check on the DB and am able to see the table /RPI/T_USER, with 0 records.
    How will the SELECT work then, if the table is with 0 records?
    Regards,
    Abhishek.

  • Error in RFC Receiver Adapter: functiontemplate from repository was null

    Hi Friends,
    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

    Hi,
    I think the logon details what you are giving in Receiver CC may be wrong. Check all those details like Application Server,System Number,User,Password and client.
    Thanks.

  • Error in SOAP receiver channel: java.io.IOException: invalid http response:

    Hi experts,
    I have a IDOC to SOAP scenario where SOAP receiver channel is sending data to web service. In the receiver channel I am getting error as below. Kindly help me to resolve this issue. Thanks.
    "Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null"

    Did you check this?
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
    Regards
    Pothana

  • Error in JMS receiver channel

    Hi,
    I have a JMS receiver channel which is connected to message queue of TIBCO which is working fine.
    But if I use the same channel after a day it goes into error and after restart of the channel it again works fine.
    Error: Message process failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to write newJMS Message body for message: 343241-......... Connector Exception: ... session ended..
    Thanks,
    Aravind

    Hello Aravind,
    I have made similar experiences while accessing JMS queues.
    Maybe the JMS queue was not available for a short time. So the receiver channel could not connect.
    Best regards,
    André

Maybe you are looking for