Dear All, When I execute a SSIS in SQL 2005 SP2 in Windows 2003 server, it sometimes return the following error. Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ". It is strange that the problem does not happen when I re-run the SSIS. Is it due to some TCP/IP issue? I found some article the command "Netsh int ip set chimney DISABLED" may solve this problem. Is it true? Thanks.

I found some article the command "Netsh int ip set chimney DISABLED" may solve this problem. Is it true? Yes. I have seen it working in one of my previous project.Nitesh Rai- Please mark the post as answered if it answers your question

I found some article the command "Netsh int ip set chimney DISABLED" may solve this problem. Is it true? Yes. I have seen it working in one of my previous project. Nitesh Rai- Please mark the post as answered if it answers your question Since there is schedule reboot of my server, do I need to run the command "Netsh int ip set chimney DISABLED" after every reboot? Thanks.

Disabling TCP Chimney offload is a one time activity and it does not require a reboot. More details here Pradeep Adiga My blog: http://www.sqldbadiaries.com

I really executed the "Netsh int ip set chimney DISABLED". However, the problem still happened. Any othter causes for the random connection failed?

Hi chanccw, From the error message "Named Pipes Provider: Could not open a connection to SQL Server [53]." you posted, the root cause is network error 53. While using command "net helpmsg 53", we can know the cause is the network path was not found. This should be due to DNS error, or network rounting error. I would ssugest you contacting the network team to check the network to fix the issue. Thanks, Jin ChenJin Chen - MSFT