Error in RFC communication

I am trying to make a communication RFC  ( ECC - > XI ), but when I verify in transaction SXMB_MONI of the XI the message does not arrive.
If I verify the SM58 of the ECC I see the following error message.
"Commit fault: com.sap.aii.af.rfc.afcommunication.RfcAFWException: Channel"
If I test the connection for the SM59, everything is OK.
Somebody would know what it is happening?
Thanks!!

Hi,
Can you look into the Sender RFC adapter and provide us with the exact error message from Comm Channel Monitoring?
Also, make sure that the same program Id is used in the TCP IP Connection and the sender rfc adapter and try to make some dummy change and activate your adapter again,
Regards
Bhavesh

Similar Messages

  • Error in RFC communication with Collaboration Room API

    I am trying to setup collaboration rooms integration with learning solution.
    while trying to fetch templates, existing rooms available on portal into R/3 (ecc 6) we are getting this error
    "Error in RFC communication with Collaboration Room API"
    i am trying to perform
    SPRO>Training & Event Management>SAP Learning Solution>Training management>Integration>Collaboration room.>Edit Room Profiles and
    Edit Role Profiles
    we have setup all SSO parameters required for this communication.
    Subhash
    Message was edited by:
            subhash soni

    Hi All,
    I'm having the same problem myself...  There is another simmilar thread at:
    [/message/448277#448277 [original link is broken];
    It seems that thread has progressed further that this one.
    Both seem to be errors connecting LSO to Collaboration rooms.  I'm getting both error messages when I try to do the same API connection functions from different points in the system, so I'm guessing that they are the same error.   IT seems to be an SSO issue.
    Regards,
    Matt

  • Error in RFC communication:imsdefault_reg

    hi
    iam getting this error in trex admin toool..please advice me to resolve this
    error in RFC communication:imsdefault_reg
    prabash

    Hi Prabash,
    could be a handful of reasons.
    Please open a support message to SAP and grant remote access to your system. Apart from that, please consult the documentation on RFC connection to TREX:
    http://help.sap.com/saphelp_erp2005/helpdata/en/19/752e4241f51a2ae10000000a1550b0/frameset.htm
    Best, Karsten

  • Error in RFC communication with XI

    Hi,
    We are trying to establish SAP -> XI communication. I think we have done all the required configurations in SAP, XI SDL and XI Directory. When we execute RFC in Se37, We get a short dump. The error details in ST22 (Dump Analysis) are:
    Runtime Error: CALL_FUNCTION_REMOTE_ERROR
    Error: "call to to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500"
    This is very urgent. Any prompt help will be really appreciated.
    best regards,
    Sanjeev Kumar

    Hi,
    I suppose you are using a RFC sender adapter to communicate with XI. This is the error that you get when u configure your RFC sender adapter wrong. Check teh followign weblog and make sure you have specified teh parameters correctly.
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    Hope this helps you.
    Cheers,
    Siva Maranani.

  • RFC communication error

    hi guys,
    our company has SAP servers in location A which often communicates with servers in location B. recently we moved both DEV and PRD servers to location C from A. the servers from B and C communicates via a VPN link.sequel to this movement we changed the IP configuration of all the systems. presently users in location B can access the PRD server in C but are not able to access the DEV server.
    the following error messages appears:
    ON PRD
    TMS Alert viewer
    transport control program tp ended with error code 0212
    error:could not access file as supposed
    command:SHOWBUFFER PRD PF=
    SAPDEV\sapmnt\trans\bin\TP_DOM
    while on DEV
    message:RFC-communication failure
    RFC communication error with system/destination
    partner not reached
    would appreciate if u culd profer a solution as soon as possible
    Regards walata

    Hi Walat,
    User access problem :-
    You located at location B are not able to access server DEV which is located C
    Pls take help from your system administrator for doing below task if you are not aware about output
    From location B try to telnet server DEV on port 32<NN> or 36<NN>  ( <NN> is your instance no of DEV )
    for e.g
    from command prompt run the following command
    telnet < dev server ip >  32<NN>
    check the ouput
    How to check the ouput
    1   after giving the above command, if you get blank screen it mean ports are open
    2  after giving the above command, if you get ouput on screen like " conneting to server < dev server ip > it mean ports are not open
    If the ports are not open then inform you network team that port mention aboev should be open for users.
    once the ports get open check above step again , if you get the blank screen , then you wil be able to login to SAP
    Server to Server Access problem :-
    From server DEV to PRD and vice versa check whether you can share the drives .
    if yous system team that yor PRD system should be able to to access the share folder sapmnt of server DEV ( SAPDEV )
    As well as check server to server port 33<NN> is open or not
    Any query pls reply.
    Thanks
    Anil

  • ERROR in the RFC communication when parabatch is set to more 3 (default)

    Hi experts,
    We have a 10 blades BIA system connecting to our BW Production. When we set the parabatch to more than the default 3 (we set to 4 or 5), We keep getting 'Batchpara Error' and 'Error in the RFC Communication: Error when opening an RFC Connection' during the initial index build. Here are what we do and what we see:
    1. set parabatch to 5 and build 1 initial index (cube is 46 mil rows, 22 GB in size) - Failed with the above errors
    2. set parabatch back to 3 and build 1 initial index (same cube as above)- successful but slow
    3. set parbatch back to 3 and build 2 initial indexes simultaneously (16 mil rows/4GB and 6 mil rows/2 GB) - Failed with the above errors.
    In the BIA index log I see the following error:
    Error in the RFC communication: Error when opening an RFC connection (TREX_BIP)
    Message no. STREX005
    In SM37 in one of the logs I see the followings:
    Parabatch Error
    Any light you can shed on why we are encountering this issue will be much appreciated. Also, I observed that there is a long idle time in all systems (BIA, DB2, BW) and seemed like their respective resources were not utilized at all. Once in a while I do see surge of cpu/memory usage in all systems but not too terrible. I'm puzzled by why there is such long interval of idle time in all systems while the initial index build is going on.
    BTW...we did the same thing (set parabatch to 5, and run parallel initial builds) in our non-prod BIA (2 blades) and QA BW landscape and do not have any issue at all.
    Thanks!
    Kee

    Hello
    PLease check the sapnotes and check the developer trace for more information.
    Note 314530 - Number of RFC/CPIC connections for external clients
    Note: 1070034
    It can also be because your system has reached it its max gateway connections...also check whether you are getting error message "Communication error, CPIC return code 017, SAP return code 450
    " in sm21  ???
    Regards
    Karthikeyan.K

  • RFC Communication error when doing initial indexing

    Hello Everyone,
    I have a quick question, when doing the initial index rollup for a BIA index the job is failing with RFC communication error.
    We currently have the setting related to " TREXRfcServer threads" set to "Automatic Changes" in order to avoid the RFC Communication errors when loading big loads in BI system.
    We currently are on Revision 49.
    I also have referred to OSS Note 1138603.
    The issue is when I am rolling up the BIA Index the rollup job is failing with RFC Communication errors.
    The Global parameters within BIA are:
    BATCHPARA - 2
    NUMPROC - 5
    PKGSIZE - 10000000
    SUBPKGSIZE - 20000
    We have two app servers with 52 Dialog processes and 25 Background processes.
    Any help would be really appreciated.
    Thanks
    Dharma.

    Removing references to systems and ports
    Issue:
    When the initial indexing is being carried out for an InfoCube to
    create the BIA Index and there is more than one application server in
    the system the job is failing with the http error.
    Hello Everyone,
    Thanks for the input, after the automatic changes was configured for concurrent requests the error is different right now.
    The error message is,
    "Remote communication failure with partner http://<Removed>:<removed>/indexCellTable"
    Overview/Background:
    When the indexing job is triggered as a background job the failure happens when the S table index is being filled.
    In our system where we are trying to do the stress testing we currently have two app servers and one central instance.
    When I limit the RFCGROUP in RSDDTREXADMIN table to one App server in terms of logon group the job finishes fine.
    Whereas, when I do not limit the RFCGROUP and all app servers are open for access the background job finishes with the error message
    Remote communication failure with partner http://<Removed>:<removed>/indexCellTable.
    We have looked into the OSS Note 1102652 and our BASIS team confirmed that they were able to ping from BI App servers into BIA blades and vice versa.
    We also confirmed if the local gateway was used for connectivity.
    The above issue was not in other systems where we only had one server.
    We currently are at Revision 49 and SP 13 in BI.
    We have E5345 Clowertown blades (2 x 4) 16GB blades.
    Please let us know if you need additional information.
    Thanks in advance for the input.
    Dharma.
    Edited by: Arun Varadarajan on Apr 24, 2009 1:36 AM

  • BPC 7.5 NW- error 'Name or password of RFC Communication user is invalid '

    Hi
    Environmen: Win 2008 R2, CPMBPC 7.5 SP09, BW 7.2 Sp09, .NET BPC 7.5 SP09
    I just completed installing .NET BPC 7.5 and when I try to open BPC Server manager, i get "cannot coonect to ABAP server' error.
    When I try to open the website http://localhost/osoft I get the error "name or password of RFC communication user is invalid".
    I see the same error in the BPC logs as well.
    I have the tried the following so far:
    1. Created single domain user for the three communication users BPC_sysadmin, BPC_admin & BPC_user.
    2. I momentarily changed to dialog users and logged in to check their fucntioning.
    3. I have generated their relevant profiles. Inlcuded SAP_ALL, SAP_NEW for the sysadmin ID
    4. I have disabled firewall, allowed port 80 on Windows firewall.
    5. I have disabled UAT
    6. I have followed the rest of the installation as per inst guide.
    When I run BPC server manager diagnostics, I see error "SAP ABAP server connection:database connection:status error".
    Can someone tell is there anything else that I could try ?
    many thanks
    Sreekanth

    Hi,
    If when you launch BPC Server Manager, you do not get "Cannot connect to ABAP server", this means user BPC_SYSADMIN is connecting correctly. And assuming you had invalid RFC user in BPC Web, your issue is then only with user BPC_USER (or BPC_ADMIN if the issue is with BPC Admin client only)
    If you do get that error, it means the error is for more than one user, so I would look for something big missing.
    In point 1 you mention domain users, make sure in BPC Server Manager under "reset login credentials" that you do not have windows users specified there as it's a common mistake, those should be your 3 BW communication users
    On BPC .Net server, if you installed SAP GUI, run an MDX_PARSER test in SM59 to check librfc32.dll is working correctly
    Also quite common issue it is possible your background users have wrong authorizations; in PFCG check the roles SAP_BPC_SYSADMIN SAP_BPC_ADMIN and SAP_BPC_USER were copied to customer namespace and that the role are active (user tab should be displaying green light) and assigned to the background communication users
    Also check the background users are not locked in SU01 (if they are locked the password saved on .Net server was or is not matching the real password defined on NW server)
    Thanks,
    Julien

  • "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

  • Error in RFC & to Solution Manager System

    Hi,
    Error in RFC & to Solution Manager System
    can anyone tells me why this error occurs???
    With regards
    kulwinder

    FYI
    We have just had same issue thaat in certain scenarios with RFC communication BACK to Solution Manager from Satellite system we got the error.  We resolved this by looking at the RFC user used in the BACK connection (i.e. SOLMAN<SID>) on the Solution Manager and changing the user type from communications.
    Hope this helps someone else, I spent ages digging around for an answer to such a simple fix
    Paul

  • Error got  in Communication channel monitoring ( component monitoring)

    Hi Experts,
    When i executed the RFC from R3, i got the below error in runtime work bench.
    please help me out if any one knows, i already gone through some of sdn line, but i am not able to get exact solution.
    com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool: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=qa2.syec.sshe.ed SYSNR=13 GWHOST=qa2.syec.sshe.ed GWSERV=sapgw13 PCS=1
    LOCATION CPIC (TCP/IP) on local host with Unicode
    ERROR max no of 100 conversations exceeded
    TIME Thu Mar 20 15:44:08 2008
    RELEASE 700
    COMPONENT CPIC (TCP/IP) with Unicode
    VERSION 3
    RC 466
    MODULE r3cpic_mt.c
    LINE 10713
    COUNTER 1
    1) Registered Server Program  has been created in RFC destination in R3, and RFC destination has been tested successfully,  in R3 System we have 9 clients,  but i have created one client independent RFC detonation type TCP/IP. is it right way to create client independent single RFC destination for multiple clients?? (  3 unit test clients, 3 development clients, 3 configure clients), but in SLD  only 3 business are created ( which are for 3 unit test clients), i have imported business system for client 300 and  i have created communication channel under this business system,  but when i run the RFC in this client i am gettin above error in component monitoring.
    2) I have created  incremented  100 to 300: Set the following environment variable CPIC_MAX_CONV=300
    3) In sender RFC  communication channel i have all correct parameters like: gateway service,Program ID, client number, password, userid etc
    Pleas help me out.
    thanks
    siva grandhi

    Hi,
    This solved this issue for me:
    Setting Maximum Database Connections
    Perform this step only if you want to check or change the values.
           1.      Open the Visual Administrator tool.
    &#9675;       j2ee admingo.bat if you also use SAP WAS ABAP.
           2.      Log on as an administrator.
           3.      Choose Server ® Services ® JDBC Connector.
           4.      Choose the Properties tab strip and select sysDS.maximumConnections.
    Regards,
    Hugo Mendoza

  • RFC 2 File Error in RFC sender: java.lang.ArrayIndexOutOfBoundsException

    Hello,
    I'm sending data asynchronously from R3 to a file through XI, I've got the RFC destination (in R3) and sender RFC channel (in XI) configured and tested. Working fine.
    Then in my report I've got the following code that sends 1 string and 4 internal tables 2 to XI:
      CALL FUNCTION 'Z_RFC_ENVIAR_DATOS_PSP'
        IN BACKGROUND TASK DESTINATION 'SAP_2_XI'
        EXPORTING
          RUTA                       = p_ruta
        TABLES
          IT_DEMANDA           = p_gt_demanda
          IT_STOCKS              = lt_stocks
          IT_CUARENTENAS   = lt_cuarent
          IT_COMPRAS           = lt_repartos.
      COMMIT WORK.
    I've done that king of connection several times and allways worked but now I've got that error in the communication channel monitoring at RWB:
    Error in processing caused by: java.lang.ArrayIndexOutOfBoundsException
    And no message is created in XI. What can it be?
    Thanks for your help

    Hi Chen Lin,
    The problem is with the adapter but no message is generated yet in XI, so I don't have XML yet.
    The RFC sends the data to XI through the RFC destination and at this point something is wrong because that error is produced. The error is visible in both sides, In transaction SM58 at R3 I can see the error that tRFC hasn't been precessed because the ArrayIndexOutOfBoundsException.
    But if I go to communication channel monitoring I can see the same error too, so that confirms that the communication between R3 and XI works fine but something is wrong and the error don't give me more details

  • Error in proxy communication with BI (special characters in fieldnames)

    Hi experts,
    We are on our way to create some interfaces between PI 7.1 and BI 7.0.
    These interfaces will communicate each system by means of ABAP proxies.
    In BI side, in order to operate with the most up-to-date information,
    we are using APD (Analysis Process Designer). It consists of a query
    execution that at last inserts data into a DSO. This DSO is a table the
    system creates, its fields are named with the prefix /bic/ and that is
    the problem. BI team tried not to use it but with no success, this
    prefix seems to be mandatory when working this way. Currently, RFC
    communication is used, that is Outbound RFCs come along with DSO tables
    and thus, data acquisition and assigning is done inmediately. Problem
    is that we want to move to proxies without losing this benefit. That is
    the clue.
    So, back again in PI, once we try to create all the necessary stuff for
    ABAP proxies, the system prevents us from creating the Data Type for
    fieldnames starting with '/' so we cannot create the Service Interface
    and so the proxy.
    Error message looks like:
    Value "/" is not allowed for the attribute "name" of type "NCName" in
    element
    Besides, we have tried to use the RFC metadata as a service interface
    but it didnt work out, because '/' characters in BI were represented
    by '-_' once we imported this metadata.
    Basically, this is the problem we are facing right now. We know that
    ABAP proxy is one of the best practises in terms of communication
    between WAS servers and due to this, we think we might be missing
    something in between.
    Is there a way to work with ABAP proxies and this BI internal
    fieldnames without having to reassign fields before calling the Proxy
    methods and classes in BI?
    Could you please help us on this issue?
    Thanks a lot in advance and best regards,
    David

    Your request is described in this how-to guide:
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40574601-ec97-2910-3cba-a0fdc10f4dce
    / in interface and data types names are represented as -_ inside PI, it will be translated to / in application system automatically.

  • Error in remote-communication

    Hello BIA experts,
    last Saturday my process chain aborted. The reason in the application log (SLG1) was:
    Error in remote-communication with partner http://<blade>:30003/IndexCellTable.
    At first I thought the rfc connection or the index service was not available, but in both logs are no entries for this time.
    The system runs with Rev48 and this is the first time this error occured.
    Any ideas?
    Best Regards,
    Jens

    Hello Vitaliy,
    I mean there are entries in the log files, but not for this date and time. I looked into the traces TrexIndexServerAlert, TrexNameServer_History, TrexRfcServerAlert, TrexRfcServer and TrexTCPClientAlert. I couldn´t find any information.
    Since 3 weeks we run with Rev48 and I never get an error like this.
    I will have a look at this, if it occurs again I´ll create an OSS.
    This is not the first time this cube is indexed.
    This is something I found also in the application log:
    Creation of the BIA index for InfoCube 'FACPRJPRD' terminated while filling (RSD_TREX (Messages from TREX Aggregate Area))
    Thanks for your answers
    Best Regards,
    Jens
    Edited by: Jens Gleichmann on Nov 4, 2008 7:35 AM

  • Schedule Receiver RFC communication channel to call R3 RFC-FM.

    Hi,
    I have requirement that I need to schedule/trigger from PI to RFC call R3 function module. Wonder if anyone here has done similar thing before? I tried to use ATP (Availability time planning) in RWB. But this seem does not success for me as there is no response and error message for this.
    Below is my configuration detail:
    Configured:
    1. Receiver communication channel - RFC
    2. Receiver agreement with the RFC message type assigned.
    3. Scheduled receiver RFC communication channel via ATP daily
    *(It is possible to make scheduling job in R/3 but we are not considering this way)
    Please let me know if anyone has done this before or any other suggestion to do the scheduling from PI.
    Thanks!
    Regards,
    SP

    Hi SP,
    As you mentioned, ATP would allow adapter to be open and in start state. Adapter's RFC, SOAP, JMS would need some other application to trigger the message processing because these are not like pooling adapter's File, JDBC and Mail. RFC adapter channel always listening to the RFC port and FM execution. Once FM from R/3 executed then the RFC adapter would trigger it's message processing.
    For Sender RFC channel: In order to trigger the RFC adapter execution at particular time then you should write a simple ABAP code which would act a batch application and which does the triggering the FM and Sender RFC channel.
    For Receiver Channel: For Receiver RFC channel it's bit trichy because here you have force Receiver RFC adapter to connect backend the execute or initialize the variables without having any XI message triggered from Sender PI channel.
    I have 2 ideas:
    1. A little difficult approach, similar to the ABAPbatch code, you need to write a java adapter module which can trigger RFC receiver channel to connect and do an initialisation at FM at regular interval.
    2. Simple approch configure a File-> 2-> RFC receiver scenario, configure File sender adapter to pick a dummy file at regular interval and RFC receiver channel does the rest.
    Please let me know still you have any doubts,
    Thanks,
    RK

Maybe you are looking for