Legacy DTS Package Issues


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?
Who is Participating?
Brendt HessConnect With a Mentor Senior 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.
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?
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.
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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?
Brendt HessConnect With a Mentor Senior 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:


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).
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.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.