How to see the dtexec command used by SQL Agent when executing a package from the SSISDB in a job...

  • I am getting an error while trying to execute a package deployed to the SSISDB catalog from with in a job. A parameter has a UNC path as it's input and the error shows some offending doublequotes that seem to have been snuck into the dtexec command that executes my package.

    1. I assume that when SQL Agent executes a package, it is just using dtexec, right?
    2. The error only shows a snippet of the full command, so I can only see the details of one of the parameters that is getting doublequotes added into the path. I cannot see the full command, I believe there is something wrong earlier in the command that has thrown off the doublequotes elsewhere.
    3. This package works when run from my desktop. It only fails in this manner when run from SSISDB catalog.
    4. The path, of course, does not include the dlbquote that is being added in during execution. The path is built with an expression and does not contain the doublequotes before or during execution form  my desktop.
    5. This is executing on a server I cannot access logs or event viewers on the OS. I have access to SSISDB reports, but execution does not make it that far, so nothing there.

    I dont have a local copy of sql server and can only work on distributed/shared sql server. Otherwise, I'd dig in to see this cmmand myself (I think could).

    I just want to see the full command that Agent is building and trying to execute so I can see where the doublequotes are going awry.

Viewing 0 posts

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