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

When you submit an order or create an account in Microsoft Dynamics CRM 3.0, you receive the following error message: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.

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.

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:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Right-click MaxUserPort, and then click Modify.
4. In the Value data box, enter 65534, and then click OK.
5. Right-click TcpTimedWaitDelay, and then click Modify.
6. In the Value data box, enter 30, and then click OK.

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.

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