10

when i execute dtsx package through command line i am triggered with the following error saying

1.The connection is not found , the error is thrown by connections collection when the specific connection element is not found

2.Cannot resolve package path to an object in the package "xxxxxxx".Verify that the package path is valid

3.The package path referenced an object that cannot be found , this occurs when an attempt is made to resolve a package path to an object that cannot be found

But this works fine when i run the package through Business Intelligence development studio.

mahesh
  • 3,067
  • 16
  • 69
  • 127

3 Answers3

32

Taking a guess here while I wait on an answer to the comment, generally when a package runs fine in BIDS but doesn't work from the commandline, I find it's related to 64/32 bit incompatibility.

Are you using Excel, Access or anything else that under the sheets uses the JET driver? That only works in 32 bit mode.

On a 64 bit OS, by default when you create a new ODBC connection, you'll be creating it in the 64 bit namespace which the 32bit version won't be able to access?

Are you using Informix or UDB/DB2 drivers? I only ever found 32 versions of those.

Running a package from the command line

dtexec is the command line mechanism for running an SSIS package. It comes in 2 flavors for 64 bit OS, both are named dtexec and generally the 32 bit is referenced in the Windows Path environment variable

On a 64 bit OS, the default path to the 64 bit would be "c:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe"

Still on 64 bit OS, the path to the 32 version would be "c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe"

To run a package named FooBar.dtsx that lives in C:\Src\MyProject\MyProject, invocation would be

"c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /file C:\Src\MyProject\MyProject\FooBar.dtsx

If that package lives on SQL Server (DEVSQL01) in the folder MyProject, this would be the call to run the same package.

"c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /SQL \MyProject\FooBar /SERVER DEVSQL01

Edit

To apply a configuration, you need to specify the /CONF option

"c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /file C:\Src\MyProject\MyProject\FooBar.dtsx /CONF C:\FooBar.dtsConfig

Looking at your comments, the only difference between our usage is you have wrapped everything in double quotes. Try it without the preceding and trailing quote.

billinkc
  • 59,250
  • 9
  • 102
  • 159
  • 2
    Thanks this command works fine for me""c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /file C:\Src\MyProject\MyProject\FooBar.dtsx" , the critical problem is i am not able to refer the configurations dtsConfig file – mahesh Jan 10 '12 at 10:08
  • For example like ""c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /file C:\Src\MyProject\MyProject\FooBar.dtsx" /conf C:\FooBar.dtsConfig" – mahesh Jan 10 '12 at 10:10
  • I question the part being able to use the 32 bit DTEXEC if you are reading Excel or Access. I haven't tried it, but I think if you install the 64 bit Access Engine after uninstalling the 32 bit one it should work. https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0ahUKEwj3-eLi_PjLAhUBOBQKHVp7DjgQFggqMAI&url=https%3A%2F%2Fsocial.msdn.microsoft.com%2FForums%2Foffice%2Fen-US%2F82354387-66e9-423b-9b13-0468066f9641%2Fdatabase-engine-redistributable-for-access-2013%3Fforum%3Daccessdev&usg=AFQjCNHuqcyVWhEDTiq6_YoJTmy2BIY5Dg&sig2=BRapEClsoqyOFk72g0o6Gg&bvm=bv.118443451,d.amc – Chad Apr 06 '16 at 02:33
1

type below text to call SSIS package

dtexec /f /set \package.variables[Variable]; value

Example:- dtexec /f E:\test_package\test_package\Package.dtsx /set \package.variables[id];1

enter image description here

Reference Ways to execute SSIS package

Samanth
  • 346
  • 3
  • 10
0

The /SQL option is for packages deployed to the MSDB -> servername\StoredPackages\MSDB\

Aram J. Dodakian
  • 1