Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS package config issue Expand / Collapse
Author
Message
Posted Monday, July 28, 2014 8:56 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 23, 2016 1:19 PM
Points: 115, Visits: 338
Hello,

I recently upgraded several SSIS packages from SQL 2005 - 2012 using the package upgrade wizard. All SSIS packages connect via config file. Whenever I run the package either in SSDT or from package execution I get the following error, but I believe that I made the proper changes in the config file. Does this have something to do with the upgrade process? Anyone have any ideas?

[Connection manager "ole"] Error: The requested OLE DB provider SQLNCLI.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".

[Connection manager "ole"] Error: Consider changing the PROVIDER in the connection string to SQLNCLI11 or visit http://www.microsoft.com/downloads to find and install support for SQLNCLI.1.

Thanks in advance,

SQL-TG


_________________________________________________________________________
- "Just import all of the data in one shot. This way we will have data on hand if necessary."
--This is the most common mistake for a manager or DBA to make.
Post #1596905
Posted Monday, July 28, 2014 9:08 AM This worked for the OP Answer marked as solution


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, November 3, 2014 8:05 AM
Points: 1,191, Visits: 9,892
The package upgrade wizard only upgrades the package, not the config file.

In this case, your config file is specifying a provider name that's no longer the correct version, so it's overriding the value in the package.

Two possible solutions:

1) Edit the package configuration and rather than exposing ConnectionString (which includes the driver details), expose ServerName, UserName, Password etc. instead.

2) Change the ConnectionString in the config file to reference the correct driver (SQLNCLI11)
Post #1596911
Posted Monday, July 28, 2014 12:41 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 23, 2016 1:19 PM
Points: 115, Visits: 338
Thanks Howard. That worked!

_________________________________________________________________________
- "Just import all of the data in one shot. This way we will have data on hand if necessary."
--This is the most common mistake for a manager or DBA to make.
Post #1597026
Posted Tuesday, July 29, 2014 8:31 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 23, 2016 1:19 PM
Points: 115, Visits: 338
Just in case anyone else is having the same issue....

I have .NET scripts that pass values into SSIS variables and provider information was also listed in those scripts. If you are having this issue check your scripts as well. For me, Provider information was in multiple places. Make sure you check all avenues.

Thanks


_________________________________________________________________________
- "Just import all of the data in one shot. This way we will have data on hand if necessary."
--This is the most common mistake for a manager or DBA to make.
Post #1597325
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse