Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/925676

From BetaArchive Wiki

Article ID: 925676

Article Last Modified on 11/15/2007


  • Microsoft BizTalk Adapter 2.0 for mySAP Business Suite


In Microsoft BizTalk Server 2004, you may experience high CPU usage when you send messages to an SAP server by using the Microsoft BizTalk Adapter 2.0 for mySAP Business Suite.


This issue occurs if a receive location is configured to connect to an SAP host name that does not exist.


Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:


You must have the Microsoft BizTalk Adapter 2.0 for mySAP Business Suite Service Pack 1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name File version File size Date Time
Sapreceiver.dll 2.0.1011.3 68,376 17-Oct-2006 19:48

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


To work around this issue, configure the receive location to use the correct SAP host.


This hotfix creates a new value in the registry. This value, RLFailureRetryCount, is located in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\BizTalk Adapter for mySAP Business Suite\2.0\

The value in the RLFailureRetryCount registry value is the maximum number of times that the receive location tries to connect to the SAP host. The default value for the RLFailureRetryCount registry value is 3. Additionally, if the RLFailureRetryCount value is missing, the BizTalk Adapter for mySAP Business Suite 2.0 uses the default value of 3.

Note The retry interval is 60 seconds.

Note The SAP connector does not expose an event or a method to determine whether the host is connected. Therefore, the retry count is not reset to 0 after a connection attempt fails. For example, if the receive location does not connect to the SAP host two times, the retry count is not reset to 0 if the connection succeeds on the third try.


For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbbtsadapters kbbts kbbug kbfix kbpubtypekc kbhotfixserver kbqfe KB925676