Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides a solution to a connectivity issue in which SQL Server Integration Services (SSIS) packages that use SQL Server Agent fail to run.
Symptoms
When you try to run an SSIS package as a SQL Server Agent job, the package doesn't run, and you receive the following error messages:
An OLE DB record is available. Source "Microsoft OLE DB Driver for SQL Server" Hresult. 0x80004005 Description "Protocol error in TDS stream".
An OLE DB record is available. Source "Microsoft OLE DB Driver for SQL Server" Hresult. 0x80004005 Description "Communication link failure".
An OLE DB record is available. Source "Microsoft OLE DB Driver for SQL Server" Hresult. 0x80004005 Description "TCP Provider: An existing connection was forcibly closed by the remote host".
Resolution
To resolve this issue, follow these steps:
- Open SQL Server Management Studio (SSMS), and then connect to your SQL Server instance.
- In the Object Explorer, navigate to SQL Server Agent.
- Locate your SSIS job that runs the package.
- Right-click the job, and then select Properties.
- In the Steps section, find the step that runs your SSIS package.
- Select the Edit button to open the Job Step Properties.
- In the Job Step Properties dialog box, navigate to Configuration > Connection Managers.
- Select the connection that's experiencing the issue.
- Change the value of the RetainSameConnection property from False to True.
- Select OK to save your changes.
Note
You can also adjust the RetainSameConnection property directly in the SSIS package connection manager properties.
See also
An existing connection was forcibly closed by the remote host (OS error 10054)