January 15, 2014 at 4:39 pm
I tried to run a package under SQL server agent. Most of my error messages indicate that I have to - change connection string to SQLNCLI10 or find and install support for SQLNCLI.1.
I need to know the meaning of this error. Is it as simple as installing a driver and registering it or is it more than just drivers. Could there be non-driver related reasons for this problem ?
Thanks.
Full error -
Code: 0xC0209302 Source: MyPackage Connection manager "MyOleDBConnection" Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_ERROR. The requested OLE DB provider SQLNCLI.1 is not registered.
Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
End Error
Code: 0xC020F42A Source: MyPackage Connection manager "MyOleDBConnection" 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
Code: 0xC020801C Source: MyPackage Log provider "SSIS log provider for SQL Server" Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "MyOleDBConnection" failed with error code 0xC0209302.
There may be error messages posted before this with more information on why the AcquireConnection method call failed.
COM error object information is available. Source: "MyPackage" error code: 0xC0209302
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
Code: 0xC0209302 Source: MyPackage Connection manager "MyOleDBConnection" Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_ERROR.
The requested OLE DB provider SQLNCLI.1 is not registered. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
End Error
Code: 0xC020F42A Source: MyPackage Connection manager "MyOleDBConnection" 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
Code: 0xC020801C Source: DFT Insert Execution Log OLE_DST Insert SSIS Execution Log [25] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "MyOleDBConnection" failed with error code 0xC0209302.
There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Code: 0xC0047017 Source: DFT Insert Execution Log SSIS.Pipeline Description: component "OLE_DST Insert SSIS Execution Log" (25) failed validation and returned error code 0xC020801C.
End Error
Code: 0xC004700C Source: DFT Insert Execution Log SSIS.Pipeline Description: One or more component failed validation.
End Error
Code: 0xC0024107 Source: DFT Insert Execution Log Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
January 16, 2014 at 2:19 am
This error message means that you are trying to run a 2005 SSIS package in a 2008R2 environment; is that the setup you have?
If you run the Package Upgrade Wizard or open the package in BIDS 2008, the package will be upgrade and all your connection strings should be automatically changed to use the SQLNCL10 drive rather than the older SQLNCL1 version. In order for the upgrade via BIDS to persist, you must save your package(s) post upgrade.
If you're using package configurations to store your connection strings then you'll need to update them manually, i.e. edit your XML config files or update the database table that contains your connection strings.
There is a good article explaining the options here[/url].
Regards
Lempster
January 16, 2014 at 11:10 am
Lempster (1/16/2014)
This error message means that you are trying to run a 2005 SSIS package in a 2008R2 environment; is that the setup you have?If you run the Package Upgrade Wizard or open the package in BIDS 2008, the package will be upgrade and all your connection strings should be automatically changed to use the SQLNCL10 drive rather than the older SQLNCL1 version. In order for the upgrade via BIDS to persist, you must save your package(s) post upgrade.
If you're using package configurations to store your connection strings then you'll need to update them manually, i.e. edit your XML config files or update the database table that contains your connection strings.
There is a good article explaining the options here[/url].
Regards
Lempster
Thanks. Actually, the package was ssis 2008. But the config was copied from a ssis 2005 file. I changed the driver manually in the config file. The errors went away, but I got another one -
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply