DTSRun error

  • When I run my DTS package from as stored proc with the following command:

    SET @TheCommand = 'dtsrun /S "W2KS-SQL" /E /N "ImportInfoHos"'

    EXEC master..xp_cmdshell @TheCommand

    I get the following error:

    DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147217887 (80040E21)

    Error string: The property 'Use Encryption for Data' is not supported.

    Error source: Microsoft Data Transformation Services (DTS) Package

    Help file: sqldts.hlp

    Help context: 1100

    Error Detail Records:

    Error: -2147217887 (80040E21); Provider Error: 0 (0)

    Error string: The property 'Use Encryption for Data' is not supported.

    Error source: Microsoft Data Transformation Services (DTS) Package

    Help file: sqldts.hlp

    Help context: 1100

    Error: -2147217887 (80040E21); Provider Error: 0 (0)

    Error string: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

    Error source: Microsoft OLE DB Provider for SQL Server

    Help file:

    Help context: 0

    I have tried to locate the Property but I can't find it.

    Can someone help me??

    Nico

  • I have never seen names quoted in cmd line like this

    SET @TheCommand = 'dtsrun /S "W2KS-SQL" /E /N "ImportInfoHos"'

    Try

    SET @TheCommand = 'dtsrun /S W2KS-SQL /E /N ImportInfoHos'

    This has always worked fine for me. See what occurrs then.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • I've tried it, but I still get the same result.

    Nico

  • What happens when you do this from cmp prompt? How about QA?

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • If you mean command prompt when you say cmp prompt:

    Then I get a login failure for my user account.

    Otherwise what do you mean with cmp prompt and QA?

    Nico

  • Thinking about this did you happen to create this package on a SQL 7 server with a 2000 client. If so what SP are you running of SQL 7? If there is a backward compatibility issue with 2000 client to 7 server that is best fixed by recreating package on server itself or with a 7 client. Also check I cannot rememebr if it was SQL 7 service pack 3 or SQL 2000 sp 2 that addresses this to fix it.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

Viewing 6 posts - 1 through 5 (of 5 total)

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