Home/ Questions/Q 289045
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T05:52:17+00:00

I have SSISpackage which is developed in VS2008/SQL2008(Target Database),My source data is SQL2005. This

  • 0

I have SSISpackage which is developed in VS2008/SQL2008(Target Database),My source data is SQL2005. This package is execute with in the .Net framework of webservice. while executing am getting error with SOURCE Connection
(with provider=SQLNCLI10 in connection string)

getting error,the description as follows.

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 Server Native Client 10.0"  Hresult: 0x80004005
 Description: "Login timeout expired".
An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005
 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005
 Description: "Named Pipes Provider: Could not open a connection to SQL Server [2]. ".

please let me know how to resolve this issue.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    That error message generally pops up if you have improper credentials.

    Ensure that you can connect to the server via the same credentials used in the SSIS package via Management Studio. The SQL 10.0 driver is fully compatible and able to connect to a SQL 2005 box.

    Most often, however, is that you’re running this as the SQL Server Agent account, which is a SQL Server account. And you’re connecting to a remote server. If this is the case, you need to create a Credential in SQL Server. Then, you have to create a Proxy in SQL Server Agent, and allow it to run SSIS packages. Then, assign that Proxy as the owner of the Job Step that kicks off the package.

    • 0