While attempting a simple content deployment the following errors where holding back the import phase ...
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 5323
Date: 3/10/2008
Time: 10:22:57 PM
User: N/A
Computer: ServerName
Description:
Failed to transfer files to destination server for Content Deployment job 'Entire Site Collection'. Exception was: 'System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
--------------------------------------------------------------------------------------------------------------------------------------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Content Deployment
Event ID: 4958
Date: 3/10/2008
Time: 10:22:58 PM
User: N/A
Computer: ServerName
Description:
Publishing: Content deployment job failed. Error: 'System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
Solution
Turns out, this is related to "TCP Chimney" (read more here). There a registry value that needs to be changed here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters in order for the content deployment to function.
Set the value of EnableTCPChimney = 0.
OR Command line: Netsh int ip set chimney DISABLED
Then reboot the server.
Setting the following values to zero will also be include in a soon to be released hotfix ...
3 comments:
John,
Thanks for this - it's helpful. Trouble is I'm getting event ID 4958, changed the registry settings on both the 'master' and 'child' servers, ran content deployment and the problem still persists.
Even more interestingly, I have the 'master' server successfully deploying content to lots of other servers without this problem, and without editing the registry.
Any further thoughts?
Couple things to try ... 1st may be irrelevant if your installation is not new ...
1. Ping the boxes from one another to be sure there is line of sight
2. Add the source machine IP and name to to the host file on the target box (c:/windows/system32/drivers/etc)
3. Reboot the server after registry changes
If you post back your specific 4958 I will probably have more thoughts ...
John,
In case you or another reader comes across this again the problem was due to the NIC driver on the 'child' or 'target' server. There are issues with the TCPChimney on some Broadcom and HP NICs - once the NIC driver was updated all ran smoothly.
Post a Comment