none
SAP keeps on losing RFC Connection to BizTalk RRS feed

  • Question

  • Hi

    We have been running BizTalk Server 2006 R2 with BizTalk Adapter pack 1.0 for 3 years. We have been connecting to SAP fine for some time up until our Gateway Service changed recently from sapgw00 to sapgw01 because of some clustering that had to be done on our SAP environment. Since this change SAP to BizTalk RFC has been giving problems 4 to 5 times a day, the error is "Error opening an RFC connection". When we test on sm59 on SAP we get an RFC connection error but the Receive Location is green with no warnings on BizTalk. While sm59 shows that there is an RFC connection error, BizTalk can send messages(IDocs) to SAP with no problem and we can see them on SAP we02. To establish the RFC connection from SAP to BizTalk again, we always have to stop and start the BizTalk Location. We then push all SAP Outbound IDocs that might have been blocked on sm58.

    Our URI on our BizTalk Receive Location and a Send Port is as follows:

    sap://CLIENT=400;LANG=EN;@a/10.0.5.11/01?ListenerGwServ=SAPGW01&ListenerGwHost=10.0.5.11&ListenerProgramId=EPROCUREMENT

    On SAP sm59

       We have an RFC Destination EPROCUREMENT with:

       Program ID : EPROCUREMENT

       Gateway Host : 10.0.5.11

       Gateway Service : sapgw01

    Is there something we might have missed when setting up this connection (either on SAP or BizTalk)?

    Thanks

    Wonder


    Wonder Andile Hlongwane MCTS

    Tuesday, May 29, 2012 4:09 PM

Answers

  • Hi,

    I already meet this trouble in a large customer installation because of too many SAP connections. In my case, the receive location was not disabled but RFC connection was not mounted.

    To fix it, we change the max worker thread of the Host instance and also the maximum number of permitted connection to SAP (CPIC_MAX_CONV environment variable).

    Hope this will help you.


    David GROSPELIER ReachSOA - Architect and co-founder dgr@reachsoa.com http://www.reachsoa.com

    Tuesday, June 5, 2012 9:18 AM

All replies

  • Sending iDocs from BizTalk to SAP will work because it doesn't need an active RFC connection unlike receiving IDocs. That being said

    On your send port using the ff will work as well:

    sap://CLIENT=400;LANG=EN;@a/10.0.5.11/01?ListenerGwServ=SAPGW01&ListenerGwHost=10.0.5.11.

    On Receive Location, sometime its icons plays a trick, after clicking the Receive Locations be sure to click F5 (Refresh) to be sure that it's really green.

    Also, it can be useful  to restart the Host Instance wherein your receive location is running when SAP Server gets restarted.

    Lastly, be sure that there's only one receive location listening to a program ID (In SAP they can have multiple clients sending on the same RFC destination, but in BizTalk you only need 1), if you have other Biztalk servers like DEV or TEST check it as well.


    Randy Aldrich Paulo

    MCTS(BizTalk 2010/2006,WCF NET4.0), MCPD | My Blog


    BizTalk Message Archiving - SQL and File
    Automating/Silent Installation of BizTalk Deployment Framework using Powershell >
    Sending IDOCs using SSIS


    • Edited by Randy Paulo Wednesday, May 30, 2012 7:45 AM
    Wednesday, May 30, 2012 7:42 AM
  • Thank you Randy

    We do refresh our Receive Location and also check our Application Log and nothing shows there.

    We keep on Restarting the host instance and receive location all the time this happens.

    This is intermittent and I am not sure whether it is purely a network problem or on the SAP side.

    We are just looking for a permanent solution.


    Wonder Andile Hlongwane MCTS

    Wednesday, May 30, 2012 2:12 PM
  • Hi,

    I already meet this trouble in a large customer installation because of too many SAP connections. In my case, the receive location was not disabled but RFC connection was not mounted.

    To fix it, we change the max worker thread of the Host instance and also the maximum number of permitted connection to SAP (CPIC_MAX_CONV environment variable).

    Hope this will help you.


    David GROSPELIER ReachSOA - Architect and co-founder dgr@reachsoa.com http://www.reachsoa.com

    Tuesday, June 5, 2012 9:18 AM
  • Hi Wonder,

    Did you mange to find the solution for this issue yet? Im also facing the same issue but on Send port where the messages just get stuck and not sent to SAP rather one of the below two situations arise :

     1. Sometimes they error out with warnings as SAP connection timeout in event log and eventually get suspended and we need to manually restart the Biztalk host instance to get these messages pushed to SAP  

    2. They do not error out rather show up as running instances in Group Hub and when biztalk host instances are restarted the messages are sent to SAP. 

    We have 2 biztalk servers not clustered but just to have high availability so not sure how the wcf-sap adapter works when it comes to 2 servers as it works well with single biztalk server. Is this something also a cause ? 

    Please if you or anyone aware of this problem responds would be of great help. Thank you.

    Wednesday, December 6, 2017 2:37 PM