Article ID: 898106
Article Last Modified on 11/15/2007
APPLIES TO
- Microsoft BizTalk Server 2004 Service Pack 1
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Standard Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Partner Edition
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
After you install Microsoft BizTalk Server 2004 Service Pack 1 (SP1), message processing may slow or stop when the maximum number of concurrent FTP connections is exceeded.
This problem may occur when you are using dynamic send ports and when the OutboundTransportLocation property changes from message to message.
CAUSE
BizTalk Server 2004 SP1 introduced FTP adapter throttling. FTP adapter throttling improves the response time of the FTP adapter and minimizes the use of system resources when you use the FTP adapter. This problem occurs because FTP adapter throttling causes remote FTP server connections to remain open on the remote FTP server.
FTP adapter throttling is enabled when you create or set the FtpMaxConcurrentConnections registry entry. The FtpMaxConcurentConnections registry entry controls the number of FTP connections for every FTP send port in a BizTalk process. As soon as a connection to the remote FTP server is successfully established, the connection will remain connected until the send port is stopped or until the remote FTP server forcefully disconnects. This new behavior causes remote FTP server connections to remain open on the remote FTP server and to consume resources.
For more information about BizTalk Server 2004 SP1, visit the following Microsoft Web site:
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
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:
Prerequisites
To apply this hotfix, you must have BizTalk Server 2004 SP1 installed on the computer.
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 tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------------------- 22-Apr-2005 20:57 3.0.6120.0 122,880 Microsoft.biztalk.coreadapter.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
For this hotfix to fix the issue addressed in the Symptoms section, you must add the new FTPReuseConnection registry entry after you apply this hotfix. The FTPReuseConnection registry entry closes the FTP client connection when the FTP adapter has completed the send.
Setting this registry entry can cause a decrease in performance because the change causes the FTP send adapter to open the connection and to close the connection for every message that is sent. This registry entry should only be used when the destination URL frequently changes.
To add this registry entry, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc{
GUID
}GUID
is a placeholder for the GUID of the host instance. - On the Edit menu, click New, and then click DWORD Value.
- Type FtpReuseConnection, and then press ENTER.
Note By default, a value of 0 turns off FTP connection reuse. - On the File menu, click Exit.
For more information about the standard terminology that is used to describe Microsoft software updates, 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
Additional query words: BTS2004
Keywords: kbbug kbfix kbftp kbqfe kbprb kbbtsadapters kbbiztalk2004presp2fix kbhotfixserver KB898106