Legacy DTS Package Issues

Hi,

We are in the process of upgrading from 2000 to 2005.  And of course, we're having issues with our legacy DTS packages.  We are kind of in a time crunch for the release so we cannot reengineer all the DTS packages to SSIS packages.  We just need the old ones to work for now.  However, they aren't cooperating! :)

One in particular, which connects to a sql 2000 database to push a table is failing.  I have set up a proxy account for the DTS packages for the jobs.

When you execute the DTS by itself and set the passwords in the connection strings it works.  When you do it in a job step (with my proxy account) it fails and it says:  

Version 9.00.4035.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  1:14:27 PM  Error: 2010-04-16 13:14:56.74     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "DTS:Password" with error 0x80070002 "The system cannot find the file specified.". 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.  End Error

I think this has something to do with the protection level of the job... and I read about how to change this within visual studio when you have the SSIS package open but this is not an SSIS package... its a DTS package.  And I have no idea how to change this or how to resolve this.  We're not trying to encrypt anything so I dunno why its yelling at me.

Any ideas?
Roxanne25Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brendt HessSenior DBACommented:
I need to check a couple of things:

(1) How are you accessing the DTS package?  Is it through the Management/legacy/Data Transformation Services in the SSMS interface?

(2) DTExec is the SSIS command line package.  DTSRun is the DTS command line package.  Which are your commands using?
0
Roxanne25Author Commented:
The packages are stored in integration services under stored packages > MSDB ... I migrated them in from 2000.

I don't see any of those commands you mentioned in the job.  I select SQL Server Integration Services as the type and run it as the proxy account I created and then I chose all the information I want from the general tab and tell it which package to run.
0
Brendt HessSenior DBACommented:
Ah.  If it has been migrated in, then it is an SSIS package now, not a DTS package.  So, you will need to manually open and re-save the packages with a modified security context - Depend on server access control - or assign a password and use that in all execution calls.

When I had to do this in a hurry, I did not migrate the DTS packages, and used them as legacy DTS packages... which worked fine, and meant I did not have to resave hundreds of packages, then test, then fix (where changes mean that the package will no longer work as migrated), test, resave, etc.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Roxanne25Author Commented:
So, if I used them just as DTS packages ... how would I do it?  The only way I saw to get them into sql server was use the migration wizard...

And assuming they were still dts packages... what would be the way to execute them?  

I guess our problem is also that some of them were using UDL files for passwords and stuff and we are just really confused as to what the best way to do this is.  I'm kind of overwhelmed with trying to fix these darned things... some of them are kinda complicated.

Also, these jobs need to run by themselves with no human intervention... so I need it to store the passwords and not rely on me to put them in every time for the connections... if I left them as SSIS packages, what security context do I need to save them in?
0
Brendt HessSenior DBACommented:
Ah, migration.... it's SO MUCH FUN!  </sarcasm>  My basic problem on advising you here is that we did a backup and restore for all of the DBs for the migration from SQL 2000 to SQL 2005, which meant that the DTS packages remained in the Legacy DTS area of the DB.  It seems that you used the Migration wizard instead.  Well, here's my best help currently:


If editing the SSIS packages created by the migration wizard, re-save them with the "Rely on server storage and roles" security level.  Note that you MUST store the SSIS package in the database to use this security level.  Otherwise, you will need to set up security on the packages to run ones that have secure items, such as (say) connections to the DB with usernames and passwords.

To use straight DTS packages in SQL 2005, you will need to install the legacy DTS components from this location:

http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en


Things to do:  If you look in SSMS, under Database / Management / Legacy / Data Transformation Services, do you see your DTS packages there?

If not, you will have to migrate the DTS packages individually (sigh) or edit all of the SSIS packages (double sigh).
0
Anthony PerkinsCommented:
If you cannot see your DTS Packages in the Legacy folder and want to continue to use DTS instead of SSIS, consider copying over the data from the old SQL Server 2000 msdb database to the SQL Server 2005 masdb database using a simple INSERT statement with a linked server.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.