Microsoft KB Archive/914264

= Error message when you submit an order or create an account in Microsoft Dynamics CRM 3.0: &quot;The underlying connection was closed: An unexpected error occurred on a receive&quot; =

Article ID: 914264

Article Last Modified on 8/21/2007

-

APPLIES TO


 * Microsoft Dynamics CRM 3.0
 * Microsoft CRM Integration for Great Plains, when used with:
 * Microsoft Dynamics CRM 3.0

-



Important This article contains information about how to modify the registry. Make sure that you 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
When you submit an order or create an account in Microsoft Dynamics CRM 3.0, you receive the following error message:

The underlying connection was closed: An unexpected error occurred on a receive.

This error message occurs when you are using the Microsoft Dynamics CRM Connector for Microsoft Dynamics GP. This problem occurs intermittently.

Note The order or account may be created in Microsoft Dynamics GP after you receive the error message.



CAUSE
You may see this problem after the Microsoft Dynamics CRM or Microsoft Dynamics GP servers have been idle for a long time. When the servers are no longer idle, you can submit an order or create an account without receiving this error message.



RESOLUTION
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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, increase the number of TCP ports that are available. Then, reduce the length of time that these TCP ports must wait before they can be re-used. To do this, modify the MaxUserPort registry setting and the TcpTimedWaitDelay registry setting as follows:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

 Right-click MaxUserPort, and then click Modify. In the Value data box, enter 65534, and then click OK. Right-click TcpTimedWaitDelay, and then click Modify. In the Value data box, enter 30, and then click OK.</li></ol>

Notes
 * Modify these registry settings on the Microsoft CRM Server, on the Microsoft CRM Connector for Great Plains server, and on the Microsoft SQL Server that are used together with the Microsoft CRM Connector for Great Plains.
 * You must restart the computer after you modify the registry.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbtshoot kberrmsg kbmbsmigrate kbbug KB914264

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.