3
votes

When I try to execute a SSIS package created in sql server data tools (vs 2010) using dtexec, I receive an error "is not a valid server package path". The documentation says use: dtexec /ISServer [path to package]. If I connect via SSMS I can browse the Integration Services Catalog, and the path is: "SSISDB\KTAKTranslator\Projects\KTAKTranslatorPro\Packages\KTAKTrans.dtsx" However,

  • dtexec /ISSERVER \SSISDB\KTAKTranslator\Projects\KTAKTranslatorPro\Packages\KTAKTrans.dtsx

produces the above error. I've also tried:

  • dtexec /ISSERVER SSISDB\KTAKTranslator\Projects\KTAKTranslatorPro\Packages\KTAKTrans.dtsx
  • dtexec /ISSERVER \SSISDB\KTAKTranslator\Projects\KTAKTranslatorPro\Packages\KTAKTrans.dtsx
  • dtexec /ISSERVER \SSISDB\KTAKTranslator\KTAKTranslatorPro\KTAKTrans.dtsx
  • dtexec /ISSERVER SSISDB\KTAKTranslator\KTAKTranslatorPro\KTAKTrans.dtsx

Still same error.

3

3 Answers

4
votes

When I tried to execute the package from the integration services catalog, and viewed the execution report; the package was listed (under the Name component) as "KTAKTranslator\KTAKTranslatorPro\KTAKTrans.dtsx" with none of the "folders" that appear while browsing the catalog in SSMS. I added a SINGLE "\" before that string and the package ran.

dtexec /ISSERVER \SSISDB\KTAKTranslator\KTAKTranslatorPro\KTAKTrans.dtsx

Oh paths; help me help you.

0
votes

not an expert but can you try this one: DTExec /ISSERVER "\SSISDB\KTAKTranslator\Projects\KTAKTranslatorPro\Packages\KTAKTrans.dtsx" /SERVER "." Regards M

0
votes

This was the command that I used. I also am making use of an environment variable (/ENVREFERENCE 3 - pointing to my "test" environment) as well as a couple of optional parameters.

dtexec /ISSERVER "\"\SSISDB\KTAKTranslator\KTAKTranslatorPro\KTAKTrans.dtsx\"" /SERVER servername /ENVREFERENCE 3 /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /REPORTING E

Hope this helps