Roxanne25
asked on
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?
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?
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
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?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
(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?