32-bit Package Execution in a SQL Server Agent Job - Option "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" is not valid. The command line parameters are invalid. The step failed.

  • Good Day Everyone,

    We're about to switch from MSSQL 2005 32 bit to MSSQL 2008 64 bit and, even though we considered reading this article on MSDN, we still experience a few issues with some of our SSIS Packages, like apparently many of us do or did.

    When I invoke a package with this command line - it works perfectly.

    "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /SQL "\MyPackages\MyPackage" /SERVER "TEST-SERVER\SQL2k8" /X86 /CHECKPOINTING OFF /REPORTING E

    Now, if I create a job to be run with SQL Server Agent, and I use the exact same command line in the 'command line' option of the package in the job (which I checked by editing a script afterward, with @command=N'"C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /SQL "\MyPackages\MyPackage" /SERVER "TEST-SERVER\SQL2k8" /X86 /CHECKPOINTING OFF /REPORTING E', )

    The job configured this way fails and we receive the following error message in the log :

    Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Option "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" is not valid. The command line parameters are invalid. The step failed.

    Any help would be appreciated,

    Thank you all in advance,

  • This was removed by the editor as SPAM

  • Thank you Stewart.

    I followed the different steps in the KB article you provided and it worked like a charm, even though I will have to read more on 'proxy accounts' configuration as I am not exactly sure if what I did is fully right : ie. going to Security > Credentials, created an entry there associated to the login I used to create the SSIS Package, then went to SQL Server Agent > Proxies, and created a Proxy which as 'linked' to the previously created credentials for both SSIS Package Execution and Operating System (CmdExec).

    Regards,

Viewing 3 posts - 1 through 2 (of 2 total)

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