How to find DTS package Name from JOB step

Question

Post reply

How to find DTS package Name from JOB step

shashi kant

SSCommitted

Points: 1659
More actions
December 17, 2007 at 3:53 am

#119872

Hi all,

How to find DTS Package name from a job steps. As it was encrypted like this

DTSRun /~Z0x63739A9F0C47A5C6D8BFEC64E6301C6E3E4892

but i want to find out which DTS package is used in this job step.

Thanks & Regards

Shashi kant chauhan

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply

Chandra Sekhara Vyas Dhara SSChampion Points: 10207 More actions · Answer 1

Chandra Sekhara Vyas Dhara

SSChampion

Points: 10207

December 17, 2007 at 5:30 am

#760653

Right click on the job and do a Generate SQL Script. CLick the Preview button and look at the line for:

--Add the job

and take a look at the variable @description. It should state the package name that the job is executing, like this:

@description = N'Execute package: XXX'

Greg Charles SSC-Forever Points: 45403 More actions · Answer 2

That will only work if the package name was used in the step description. What you need to do is

decrpyt the DTSRUN command. Do this:

copy the command to a cmd prompt, append /!X /!C to the end, and run it. The !X argument blocks

execution of the package and the !C argument copies the unencrypted command to the Windows clipboard.

Just open Notepad and paste to see the unencrypted command. Look for the package name after the 'N'

argument.

Greg

shashi kant SSCommitted Points: 1659 More actions · Answer 3

Thanks to both of you,

The first reply is only applicable when you use the name as an unencrypted form...

The second reply i check and tried before my testing but i have not got the result at all..

In my case this is not work fine .

I got a very good reply from one of my friend Named Neeraj Malik 🙂

he suggest me to use DTSRUNDEC.exe for getting exact name of package which is used.

You just download this package and use the exe as i used.

Please check this link for download this file http://jimmers.info/software.html

Steps.

Start-> Run-> Cmd

extract your DTSRUNDESC.exe file on desktop.

after that cd c:\documents and settings\User\desktop\DTSRUNDESC.exe 0xh1........

the last parameter is you encrypted name of the DTS package which comes after /~z option.

after running this you got the Package name, server Name.

Regards

Shashi Kant Chauhan

(Share your knowlege with others, Really it grows. So don't hesitate while giving some one somthing)

Greg Charles SSC-Forever Points: 45403 More actions · Answer 4

Greg Charles

SSC-Forever

Points: 45403

December 17, 2007 at 12:20 pm

#760787

I've used DTSRUNDEC and it does work, but the method I described was easier to use so I've stuck with it. I'm curious about why it didn't work for you.

Greg

homebrew01 SSC Guru Points: 55454 More actions · Answer 5

Greg Charles (12/17/2007)

That will only work if the package name was used in the step description. What you need to do is

decrpyt the DTSRUN command. Do this:

copy the command to a cmd prompt, append /!X /!C to the end, and run it. The !X argument blocks

execution of the package and the !C argument copies the unencrypted command to the Windows clipboard.

Just open Notepad and paste to see the unencrypted command. Look for the package name after the 'N'

argument.

Greg

Worked like a charm for me .. Thanks !

shashi kant SSCommitted Points: 1659 More actions · Answer 6

shashi kant

SSCommitted

Points: 1659

December 18, 2007 at 3:21 am

#760931

Thanks Greg Charles,

for your alternative suggestion, Now /!x /!c works in my case

Output is same in both the solution.

Regards

Shashi Kant chauhan

Scott Coleman One Orange Chip Points: 27451 More actions · Answer 7

The /!X /!C tricked worked fine for me and is definately a good tip. But instead of scripting the job so you can see what it is going to set the Description property to, why don't you just look at the job properties to see the Description property?

I've usually relied on the fact that when you schedule the job it has the same name as the package that was scheduled. In my experience, none of these scheduled packages has been edited later to add steps or change the description property so I didn't have to do much guessing. If there's any doubt that the DTS command line doesn't match the job name or description, decrypting the command line is the only way to be certain.

kate-395233 Say Hey Kid Points: 694 More actions · Answer 8

kate-395233

Say Hey Kid

Points: 694

December 19, 2007 at 2:32 am

#761315

That's a really nice tip - it worked for me too. I inherited a few encrypted jobs when I took over this position so have now been able to unencrypt them and update the jobs with the real name of the DTS package. Thanks.