DTSrun/DTExe in sql server 2005

  • I've tried running both in sql server 2005 to run a migrated dts package with sql server agent scheduled job and no luck. Can this be done?

    ¤ §unshine ¤

  • If it has been migrated, it is now an SSIS Package.

    Add a job step and select the Integration Services Package step type. You should then be able to select the package from the server in the job step details.

  • It is in the Legacy Folder, it has not been migrated as an SSIS package but it is in the sql server 2005 as a dts package legacy.

    ¤ §unshine ¤

  • You can do it but you can't just right-click on the package and schedule it like you could in Enterprise Manager. You'll have to explicitly create a job and add a step to run the package. Make the Type 'CmdExec' and put a DTSRun command in the Command box. You can generate the DTSRun command by using the dtsrunui utility.

    Greg

  • DTSRun from what I understand is replaced with dtexec and that is not working either.

    ¤ §unshine ¤

  • Dtexec only works for SSIS packages. You still have to use DTSRun for DTS packages.

    Greg

  • DTSRun is not working for us.. error I receive

    Server does not exist or access denied. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0. Process Exit Code 1. The step failed.

    Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:23:12 PM Could not load package "Packange Name" because of error 0xC001000A. Description: The specified package could not be loaded from the SQL Server database. Source: Started: 4:23:12 PM Finished: 4:23:13 PM Elapsed: 0.282 seconds. Process Exit Code 5. The step failed.

    Code I have tried running...

    DTSRUN /S [CHI-SQL-Servername]\Instance /E /N Package Name

    and also tried

    exec master..xp_cmdshell 'DTSRUN /S "CHI-SQL-Servername]\instance" /E /N "PackageName" '

    ¤ §unshine ¤

  • Try DTSRun without the server parameter.

    Greg

  • I tried that and nothing. I'm thinking it has to do with the dashes or instance. I also tried the following

    DTSRUN.exe /S~[chi-sql-servername\instance] /E /N~[package name]

    and got...

    Error: -2147467259 (80004005); Provider Error: 17 (11)

    Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

    Error source: Microsoft OLE DB Provider for SQL Server

    Help file:

    Help context: 0

    ¤ §unshine ¤

  • I don't think square brackets are allowed in the command string. Try using quotes around the server/instance name and the package name e.g.

    DTSRun/S "CHI-SQL-Servername\instance" /E /N "PackageName"

    Greg

  • using the dtsrun by itself does not work, but executing it does. what is going on??? is it a setting?

    ¤ §unshine ¤

  • You're still trying to run the package in a job step, right? I have lots of jobs that run legacy DTS packages and their steps look like this:

    Type:

    Operating system (CmdExec)

    Run as:

    SQL Agent Service Account

    Command:

    DTSRun/S "CHI-SQL-Servername\instance" /E /N "PackageName"

    Greg

  • Sunshine -

    ditch the ~. That's an instruction telling DTSrun that you're passing an encrypted/hex value for a parameter. Plain-text parameters should be passed without the ~.

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • I've tried dtrun with the quotes as well. also removed the ~. ive done this several times at other companies, for some reason, it is not working here. could it be sp4?

    ¤ §unshine ¤

  • Is there special permissions to use the Operating system (CmdExec)? I am trying to schedule a job using this and the dtsrun with no success

    thanks

    Kristi

Viewing 15 posts - 1 through 15 (of 29 total)

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