October 11, 2010 at 4:10 am
I install SQL Server 2008, When I opend my SSIS Project (Which is build in SQL Server SSIS 2005). It ask me to upgrade. But While upgrading
I am getting following error message.
Warning 0x80019316: : The provider name for the connection manager "EDW_STAGING" has been changed from "SQLNCLI.1" to "SQLNCLI10".
Warning 0x80019316: : The provider name for the connection manager "NAVISION" has been changed from "SQLNCLI.1" to "SQLNCLI10".
Information 0x40016019: : The package format was migrated from version 2 to version 3. It must be saved to retain migration changes.
Error 0xc0016016: : Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
October 11, 2010 at 4:16 am
The only error relates to the password.
So I would remove it (in 2005) and try again. You can always put it back after the upgrade.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 11, 2010 at 4:38 am
no I didn't get it, from where/which password I have to remove.
Can you please explain it.
October 11, 2010 at 4:44 am
saurabh.deshpande (10/11/2010)
no I didn't get it, from where/which password I have to remove.
Can you please explain it.
Have a read here and see whether it helps you.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 11, 2010 at 8:27 am
Hi Now I am able to upgrade
But, I am getting following message, while opening connection manager
"The specified provider is not supported. Please choose different provider in connection manager."
October 11, 2010 at 8:40 am
Have you tried following the advice and seeing what happens?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 11, 2010 at 8:43 am
Log Report
The Upgrade was Successful
- Upgrading package PKG_STG_CustomerDetails.dtsx (Warning)
Messages
Warning 0x80019316: : The provider name for the connection manager "EDW_STAGING" has been changed from "SQLNCLI.1" to "SQLNCLI10".
Warning 0x80019316: : The provider name for the connection manager "TYCO_MDM" has been changed from "SQLNCLI.1" to "SQLNCLI10".
Information 0x40016019: : The package format was migrated from version 2 to version 3. It must be saved to retain migration changes.
Information 0x40016041: ETL_STG_Customer_Details_city: The package is attempting to configure from the XML file "C:\PricingAnalytics\PricingAnalytics Phase II\EDW_STAGING.dtsConfig".
Information 0x40016041: ETL_STG_Customer_Details_city: The package is attempting to configure from the XML file "C:\PricingAnalytics\PricingAnalytics Phase II\TYCO_MDM.dtsConfig".
October 11, 2010 at 8:58 am
Great!
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 11, 2010 at 9:08 am
But, Connection Manager still not working.
It's not upgrading SQLNCLI.1 SQLNCLI10.1
October 11, 2010 at 9:11 am
saurabh.deshpande (10/11/2010)
But, Connection Manager still not working.
It's not upgrading SQLNCLI.1 SQLNCLI10.1
Have you tried manually rebuilding the connection manager and making the appropriate changes?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 11, 2010 at 1:15 pm
If your Connection Manager properties are set by a variable, an expression, a configuration file or a Data Source, the upgrade process will not be able to upgrade it (despite what the log says). You will need to manually change the properties as Alvin has suggested.
Also, depending on the method you use to upgrade packages, you will need to save the package before the changes are permanent. I would advise that you take backup copies of all the packages you were upgrading in case something goes wrong - there's no 'downgrade' option!
Regards
Lempster
October 11, 2010 at 11:15 pm
Thanks Lempster.
that's clear for me.
But, what is solution for upgrading connection manager.
I used configuration file option for deployment.
And I have almost 100 Packages build in SSIS 2005.
and each package using configuration file.
what steps I have to perform, so that it upgrade everthing,
including connection manager.
Thanks again
October 12, 2010 at 3:10 am
Have you also changed your configuration file? If not, the configuration file will try reset the values of your connection manager.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 12, 2010 at 8:46 am
Path="\Package.Connections[EDW_STAGING].Properties[ConnectionString]"
ValueType="String"><ConfiguredValue>Data Source=TESTDB1;User ID=TEST;Initial Catalog=STAGING;Provider=SQLNCLI.1;Auto
Translate=False;</ConfiguredValue></Configuration><Configuration ConfiguredType="Property"
Is this string I need to change? (Provider from SQLCLI.1 to SQLCLI.10)
October 12, 2010 at 10:52 am
saurabh.deshpande (10/12/2010)
Path="\Package.Connections[EDW_STAGING].Properties[ConnectionString]"ValueType="String"><ConfiguredValue>Data Source=TESTDB1;User ID=TEST;Initial Catalog=STAGING;Provider=SQLNCLI.1;Auto
Translate=False;</ConfiguredValue></Configuration><Configuration ConfiguredType="Property"
Is this string I need to change? (Provider from SQLCLI.1 to SQLCLI.10)
I believe so. Try it out and let us know how it works out.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply