August 25, 2011 at 4:51 pm
I have a job which is on sql 2008r2 pointing to a package which is stored in sql 2005 and both of these are 64 bit versions. Mentioned below is the error:
Message
Executed as user: mydomain\username. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 4:13:28 PM Error: 2011-08-25 16:13:34.65 Code: 0xC0209303 Source: MyConnectionManager Connection manager "DTSConnection" Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider SQLNCLI.1 is not registered -- perhaps no 64-bit provider is available. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2011-08-25 16:13:34.65 Code: 0xC020F42A Source: MyConnectionManager Connection manager "DTSConnection" Description: Consider changing the PROVIDER in the connection string to SQLNCLI10 or visit http://www.microsoft.com/downloads to find and install support for SQLNCLI.1. End Error Error: 2011-08-25 16:13:34.65 Code: 0xC00220E4 Source: DTS_ExecPackage Description: Error 0xC0209303 while preparing to load the package. SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider %2 is not registered -- perhaps no 64-bit provider is available. Error code: 0x%1!8.8X!. . End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:13:28 PM Finished: 4:13:34 PM Elapsed: 6.562 seconds. The package execution failed. The step failed.
I couldn't find a right solution. Any suggestion will be highly appreciated. Thanks
August 25, 2011 at 9:51 pm
They are on separate boxes right? The 2008 and 2005 instances? And the package is executing in the context of the 2008 box?
I would expect that, as described by the error, the SQLNCLI.1 provider is not available on the 2008 box.
2008 by default will use the SQLNCLI10 provider and doesn't know about the SQLNCLI.1 that was default in 2005
Either alter the package to use a different provider (one that is known to the 2008 box) or make the provider available on the 2008 box.
August 25, 2011 at 9:55 pm
sam.dahl (8/25/2011)
They are on separate boxes right? The 2008 and 2005 instances? And the package is executing in the context of the 2008 box?I would expect that, as described by the error, the SQLNCLI.1 provider is not available on the 2008 box.
2008 by default will use the SQLNCLI10 provider and doesn't know about the SQLNCLI.1 that was default in 2005
Either alter the package to use a different provider (one that is known to the 2008 box) or make the provider available on the 2008 box.
Yes they are on different boxes. I tried altering but i am not able to upload the package after altering. How can i instal 'SQLNLI.1' on a 2008 box? Any idea
August 25, 2011 at 10:02 pm
This ought to do it: http://msdn.microsoft.com/en-us/library/ms131321%28v=SQL.90%29.aspx
In addition to installing SQL Native Client as part of the SQL Server installation, there is also a redistributable installation program named sqlncli.msi, which can be found on the SQL Server 2005 installation disk in the following location:
%CD%\Setup\
August 26, 2011 at 4:20 am
sam.dahl (8/25/2011)
This ought to do it: http://msdn.microsoft.com/en-us/library/ms131321%28v=SQL.90%29.aspxIn addition to installing SQL Native Client as part of the SQL Server installation, there is also a redistributable installation program named sqlncli.msi, which can be found on the SQL Server 2005 installation disk in the following location:
%CD%\Setup\
Thanks again. I thought i need to install sql 2008 R2 tools on sql 2005 box? Situation is something like this:
i) SSIS package - sql 2005
ii) Package has connection to another package - sql 2005 ( same server as i)
iiii) Package has connection to a sql 2008 R2 database.
iv) The job is ran from sql 2008 R2.
I thought sql 2008 is backward compatible so i will need to install sql 2008 R2 tools on sql 2005 box?
August 28, 2011 at 5:41 pm
I still think you're better off altering the packages, but...
Why not try both? My money would be on the 2008 box needing the 2005 client.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply