I am seeing a strange behavior in my SSIS package when using a network UNC for my package configuration. I’ve created a package configuration that looks to a network path for its configuration file. When I try to run this package from the designer I receive the warning that the configuration file cannot be found and failure importing configuration file. I’m using SQL Server 2012/ Sql Server Data Tools (aka BIDS).
When I store the configuration file on my local hard drive I get no warning. When I map the network path to a drive letter and set my path to the drive letter I get no warning. It’s only when I specify the path as a UNC.
As a further test, I created a simple package with a package configuration pointing to the UNC. I added a script task with some code that reads up the contents of that same config file specified as a UNC into a string variable. When I run the package from the designer, I still get the warnings that it can’t find the config file –but- the script task can read the contents of that config file without a problem.
This is a new one for me. Has anyone seen this behavior before?