Microsoft Knowledge Base Email Alertz

(870949) - Discusses a problem where you cannot save messages that are larger than 18 MB from the Orchestration Debugger in BizTalk Server 2004.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 870949 - Last Review: January 12, 2007 - Revision: 1.3

BUG: You cannot save messages that are larger than 18 MB from the Orchestration Debugger in BizTalk Server 2004

Notice
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/ ) Description of the Microsoft Windows Registry

On This Page

SYMPTOMS

When you try to save a message that is larger than 18 MB from the Orchestration Debugger in Microsoft BizTalk Server 2004, you may receive the following error message from the Health and Activity Tracking (HAT) tool:
The following error occurred when extracting variable information from the Runtime:
Only one usage of each socket address (protocol/network address/port) is normally permitted

CAUSE

This problem occurs because new TCP ports are opened every time that data is read from the message stream across the remoting boundary. When remoting opens and closes a TCP connection, it takes four minutes for the connection to finally close. This time delay is dictated by RFC-793 Section 3.5.

RESOLUTION

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

We recommend that you save live messages from the HAT Operations view. However, to resolve this problem, you can use one or both of the following methods:

Method 1: Adjust dynamically allocated ports

The
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort
registry key determines the upper limit of the socket number that can be dynamically returned. By default, the upper limit is 5000 unless you specify the upper limit. You can increase this number, but it costs some kernel memory. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then expand the
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    registry key.
  3. Locate and then right-click MaxUserPort.
  4. Click Modify, type the appropriate value, and then click OK.

    Note The valid range of this value is 5000 through 65534 (decimal).

    Note You must restart your computer for this change to take effect.

Method 2: Adjust port reserved time

The
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay
registry key determines how long before the port is available for use again. By default, this value is 4 minutes. The recommended value is 30 seconds. To set this value, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then expand the
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    registry key.
  3. Locate and then right-click TcpTimedWaitDelay.
  4. Click Modify, type the appropriate value, and then click OK.

    Note The valid range for this value is 30 through 300 (decimal), and the time value is in seconds.

    Note You must restart your computer for this change to take effect.

STATUS

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

APPLIES TO
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
Keywords: 
kbtshoot kbbug KB870949
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate