TCP Provider: An existing connection was forcibly closed by the remote host.

Question

TCP Provider: An existing connection was forcibly closed by the remote host.

Igor Santos

Mr or Mrs. 500

Points: 530
More actions
July 17, 2015 at 4:31 pm

#309952

We have a setup involving 3 servers:
ServerA - Source, SQL Server 2008R2
ServerB - SSIS/ETL, SQL Server 2014
ServerC - Destination, SQL Server 2014
ServerD - Alternative Source, SQL Server 2008R2
We are receiving the below error message while executing a package reading from ServerA to ServerC:
7/17/2015 5:10:47 PM : [-1071636471] SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: The specified network name is no longer available. ".
We then tried a different source, ServerD, and received the same exact error message.
We then rebooted ServerC and the issue went away.
Any ideas of what could this be related to?

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply

Eirikur Eiriksson SSC Guru Points: 182912 More actions · Answer 1

Looks to me like a permission issue (the credentials used for running the package), was anything changed that could affect this. Seen similar in the passed where permissions to read and write to the Agent's temp directory were missing.

😎