none
BizTalk 2009 - Not recovering from SAP Backup RRS feed

  • Question

  • Environment: Multi-node BizTalk 2009 group, Windows Server 2008 64 Bit, Microsoft BizTalk Adapter v2.0 for mySAP Business Suite (NOT BizTalk Adapter Pack adapter)

    Every Saturday night at 9pm, SAP goes down for a backup.  All interfaces, users are locked out of the system.  This backup takes around 30 minutes to complete.  Our on call person received a call aroun 11pm indicating that SAP IDOCs were not being sent to BizTalk.  He logged onto the BizTalk Servers, verified that all applications(and receive locations) were online/enabled.  He was also able to validate that BizTalk was sending IDOCs( from within this same application/host instance) to SAP without any issues.

    Upon restarting the Host Instances responsible for receiving SAP IDocs, the messages flowed through without issue.

    What is interesting is that we have been running Biztalk 2006 R1 for several years with this version of the SAP Adapter and have never had issues with recovering from SAP backups. 

    We could schedule a restart of these host instances for every Saturday night after the backup but that is not an ideal situation.

    In the event viewer, we did notice a few of these errors.  But, like I said, there were no receive locations offline when our on-call guy logged onto the servers.  He did not enable or start any applications - only restarted host instances.

    Event Type:        Error
    Event Source:    BizTalk Server 2009
    Event Category:                (1)
    Event ID:              5741
    Date:                     11/14/2009
    Time:                     9:02:30 PM
    User:                     N/A
    Computer:          *BizTalkServer*
    Description:
    The receive location "SAP://*BizTalkServer*:*SAPServer*/*ParterProfile*/*SAPGateway*/" is shutting down. The adapter did not provide any error description.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    On the SAP side, in transaction SM58,  we received some errors indicating "Target system/gateway not active" Message no. SY358

    So it is almost as if BizTalk could not re-connect to SAP or was trying to use the old connection that it had established before the outage. 

    Has anyone experienced any similar behaviour?

    Thanks,

    Kent


    http://kentweare.blogspot.com
    Monday, November 16, 2009 6:26 PM

All replies

  • Hi Kent,

    The 
    only thing that I can think of for this situation is that the adapter may be using a persistent connection to the SAP instance.   I know that this is the case for UNC file shares to allow the underlying .Net FileWatcher to catch events on the share.  Something similar may be happening here.  Hopefully this will lead you into the correct direction.

    Thanks,

    William

    Wednesday, November 18, 2009 11:15 AM
  • This is normal behaviour.
    When SAP goes offline, while the SAP Receive Location is still active, the adapter will keep trying to re-connect every minute (60 seconds interval). When the retry count reaches the maximum retry attempts (default set to 3), the adapter stops re-connecting to SAP instance and as a result does not receive messages even though the SAP instance is restarted.

    This behavior is by-design and the default behavior requires that the SAP Server should be up within 3 minutes in order to receive further messages. This
    can be resolved by configuring the “RLFailureRetryCount” registry value. The value in the “RLFailureRetryCount” indicates the number of minutes
    the retry attempts will be made. The value (of type string) should be created in the following location:
    HKEY_LOCAL_MACHINE\Software\Microsoft\BizTalk Adapter for mySAP Business Suite\2.0

    This Registry key is only implemented with Sapreceiver.dll version 2.0.1011.3 and higher.
    For more information on the Registry Key can be found in the article: http://support.microsoft.com/kb/925676 und "More information".

    Nevertheless to say, please do thourough testing before applying!


    This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Kent Weare Wednesday, November 18, 2009 2:07 PM
    • Unmarked as answer by Kent Weare Thursday, December 10, 2009 6:48 PM
    Wednesday, November 18, 2009 11:33 AM
  • Thanks Jozef,  this sounds like a viable solution.  The only question that comes to mind is why we didn't see this behaviour in BTS 2006.  I am going to double check those servers to see if this fix was previously applied, but to my knowledge it wasn't.

    It may take some time for me to get the SAP team to take a Dev or Test outage to validate this change so I am going to mark this thread as Answered and will come back if our tests fail.

    Thanks again...

    Kent
    http://kentweare.blogspot.com
    Wednesday, November 18, 2009 1:47 PM
  • We had the opportunity to take an outage in Test and try this 3 times.  We have 3 applications that receive SAP IDocs, each has their own Partner Profile but all connect to the same SAP environment.

    Note that the fix provided in the link above cannot be installed on BizTalk 2009 servers...only 2006.  What we did configure was the RLFailureRetryCount registry entry(and rebooted servers just in case) and set the value = 600.

    When we were running our tests this morning we were taking SAP down for around 20 minutes so the RLFailureRetryCount definately exceeds the SAP down time considerably.

    What is interesting is that only 1 out of 3 receive locations shut down during out 3 separate tests.  So it appears that this fix is "kinda" working but was not conclusive as the following receive location did shut down.  Here are the two error messages that we received:

    Event Type:        Error
    Event Source:    BizTalk Server 2009
    Event Category:                (1)
    Event ID:              5649
    Date:                     12/10/2009
    Time:                     11:07:38 AM
    User:                     N/A
    Computer:          *SERVER*
    Description:
    The receive location "*Receive Location Name*" with URL "SAP://*BTSServer*:*SAP Server*/*PartnerProfile*/*SAP GATEWAY*/" is shutting down. Details:"Connect to SAP gateway failed
    Connect_PM  TPNAME=*PartnerProfile*, GWHOST=*SAPServer*, GWSERV=3374

    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner not reached (host *SAPServer*, service 3374)

    TIME        Thu Dec 10 11:07:38 2009
    RELEASE     620
    COMPONENT   NI (network interface)
    VERSION     36
    RC          -10
    MODULE      ninti.c
    LINE        972
    DETAIL      NiPConnect2
    SYSTEM CALL SO_ERROR
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     588
    ".


    ----------------------------------------------------------------------
    Event Type:        Error
    Event Source:    BizTalk Server 2009
    Event Category:                (1)
    Event ID:              5741
    Date:                     12/10/2009
    Time:                     11:07:38 AM
    User:                     N/A
    Computer:          *BTS SERVER*
    Description:
    The receive location "SAP://*BTS SERVER*:*SAP SERVER*/*ParternerPofile*/*SAPGATEWAY*/" is shutting down. The adapter did not provide any error description.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    http://kentweare.blogspot.com
    Thursday, December 10, 2009 6:56 PM