Thursday, January 31, 2008

SSIS configuration file warning

While trying to run one of our SSIS packages after migrating from development to string testing I got an interesting warning message.

Warning: 2008-01-31 16:02:38.88
Code: 0x80012014
Source: Package_Name
Description: The configuration file "X:\\Package_Name.dtsConfig" cannot be found. Check the directory and file name.
End Warning
Warning: 2008-01-31 16:02:38.88
Code: 0x80012059
Source: Package_Name
Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed.
End Warning

I was trying to run the package using the dtexec utility with the /conf option. At design time the package was bound to the dev config file. After the migration to the string environment I wanted to run the same package but pointing to the string config file. And that raised the above mentioned error.

This happens because the package configuration file name and location are embedded into the package.

<:Property DTS:Name="ConfigurationString">X:\\Package_Name.dtsConfig</DTS:Property>

And at run time the package first looks for the file bound at design time rather than the one you specified in the dtexec command. But this is only a warning. The package runs properly after this warning message.

So I understand that the SSIS package first looks for the design time configuration file and then goes for the file specified in /conf option.

One more thing I noticed while deploying a package to a file system is you are not allowed to type the path. The control is disabled!!

I had to install the SSIS package in a LAN share whose path I know very well. As I was not able to key in the path, I had to search hard for the share in the "Entire Network" node in the folder browser dialog. This is a tedious way of doing it as the company I work for has N number of systems and servers out there in the network. It would be much better if you were allowed to key in the path.

1 comments:

Anonymous said...

Since writing this, have you found a way to eliminate the warning message? Seems a little short sighted of Microsoft to think that the various environments that companies use to escalate design changes through would all allow exactly the same path as your development workstation.

Saravanan Kanagaraj