Microsoft KB Archive/826210

= &quot;The Underlying Connection Was Closed&quot; Error Message When You Run Site Deployment =

Article ID: 826210

Article Last Modified on 8/6/2003

-

APPLIES TO


 * Microsoft Content Management Server 2002

-





SYMPTOMS
When you run Site Deployment in Microsoft Content Management Server (MCMS) 2002 and you use Microsoft Internet Information Services (IIS) 6.0 on a Microsoft Windows Server 2003-based computer, you may receive the following error message:

Error: 0

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

Severity: 5

Source: System Debug info: N/A

Extra info: N/A

Client Source: CImProgress::ProcessPackage

Recommended Action: N/A

When you click OK and try to close the Import window, you may receive the following error message:

The item has been deleted on the Server

When you click OK again, you receive the following error message:

Error: 0

Description: Element not found

Severity: 5

Source: Nodes

Debug info: N/A

Extra info: N/A

Client Source: AETree::RefreshRecycleBin

Recommended Action: N/A



CAUSE
This problem may occur if you are importing a large amount of data and if the connection timeout value for IIS 6.0 is too low.



RESOLUTION
To resolve this problem, you must increase the connection timeout value in IIS 6.0. To do so, follow these steps:
 * 1) Click Start, and then click Control Panel.
 * 2) Double-click Administrative Tools, and then double-click Internet Information Services Manager.
 * 3) Expand Web Sites, right-click Default Web Site (or the site where your MCMS Web application is installed), and then click Properties.
 * 4) Click the Web Site tab.
 * 5) In the Connections section, in the Connection timeout box, increase the seconds to a value that is sufficient for the length of the import.
 * 6) Click OK.



MORE INFORMATION
You may also want to adjust some values in your environment to help ensure a smooth Site Deployment process. To do so, follow these steps:  Increase the responseDeadlockInterval value in your Machine.config file. To do so, follow these steps:  On the computer that is running MCMS, open the Machine.config file. By default, this file is located in the %windir%\Microsoft.Net\Framework\< >\Config folder. In the  tag, change the value of responseDeadlockInterval from 00:03:00 to 12:00:00.

The value is now set to 12 hours for any aspnet_wp process.  Make sure that the maxRequestLength value of the Web.config file in your Site Deployment virtual directory is sufficient for your Site Deployment file. To do so, follow these steps:  On the computer that is running MCMS, open the Web.config file that is located in the < >\Server\MCMS\SiteDeployment folder.</li> In the <httpRuntime> tag, set maxRequestLength to the nearest multiple of 1,024 that is greater than the size (in KB) of the .sdo file (1,024 KB = 1 MB; 102,400 KB = 100 MB). For example, if the .sdo file is 3 MB, set 4,096 as the value (4,096 KB is greater than 3 MB and 4,096 = 4 x 1,024).</li></ol> </li></ol>

In Windows Server 2003, you can configure the maximum amount of data for resource uploading in IIS, but the default limit is too low for MCMS Site Deployment. For more information, see the &quot;To increase the size of the SDO files&quot; section in the MCMS 2002 Service Pack 1 (SP1) documentation. To access this documentation, visit the following Microsoft Web site:

http://www.microsoft.com/cmserver

<div class="references_section">