Problems executing a SSIS package deployed to the file system

Question

I have a SSIS master package, which executes several child packages. It works great, but when I deploy it to the file system on the server, I get an error code "0xC00220DE". "The system cannot find the file specified."

When I run the package on the server by double-clicking it, it works correctly. But when I use DTExec:

dtexec /FILE "d:\cmcdx\ssis\MAESTRO_FACTURACION.dtsx"

I get the mentioned error.

The package configuration is correct, and the user I'm executing the package with is administrator of the machine.

Should I deploy the packages to Sql Server? What are the best practices for deploying a master-child package? I'm running out of ideas here...

By the way, I'm running Sql Server 2005 sp3.

Answer 1

Is the package not getting a path or location value from a package configuration file? If so make sure you include the /ConfigFile argument and the path to the config file. Another thing to possibly check is if you have any connections in the package that refer to mapped network drives, these may not work running under the different service account than your local console account.

[Edit] Try this command line below on the server (notice the double slashes).

dtexec /FILE "d:\\cmcdx\\ssis\\MAESTRO_FACTURACION.dtsx"

Answer 2

There are several things that could be going wrong here. You mention that you're using a master package to run several child packages. Are all of your child packages in their proper location on the server as well?

Remember that the paths to the child packages should be variables in your master package so that those values can be changed through a configuration file on the server if need be.

You might also want to check out this set of tutorials on MSDN:

Package Deployment How-To Topics

These tutorials explain how to properly enable package configurations on the server when your package runs.

Answer 3

Solved it.

I was using relative paths to point to the child packages, and in runtime SSIS was unable to find them.

In the end I used a specific path, set in a configuration file. Then I used the deployment utility, copied everything to the server, run it by double clicking on the SSISDeploymentManifest file and changed the paths to the proper location.

Thank James and Justin for your answers.