SSIS Package Configuration Warning: Failure importing configuration file

  • 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?

  • Swap to project deployment with different server configurations, it's so much easier.

  • Setup Integration Services Catalog and switch to project based deployment - deploy to the catalog.  So much easier...

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Mike Dwyer - Monday, March 27, 2017 5:00 PM

    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?

    I'm not fond of the Project Deployment model, but I am a fan of using an SSIS configuration database on each instance where SSIS runs.   It's much more practical than using a physical file for configuration, and there's a lot less complexity to at least getting that done before you even think about the Project Deployment model.

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)

  • Understood.  However in this case I needed an external config file as it contains metadata about a fileset that comes from somewhere else.

    In any event I solved the problem.  And this is a rather obscure glitch for those of us out there that have to use package deployment.
    My UNC was in the form of \\servername\SubfolderA\SubfolderB\SubfolderC\myconfigfile.dtsconfig.
    I actually had full access rights to SubfolderC and the package itself had a vb task that reads up the contents of the actual config file as proof of my access, HOWEVER, it turns out I wasn't given rights to list folder contents of "SubfolderB".  SSIS must be doing some sort of reading up of the folder hierarchy when setting the config.  When it gets to SubfolderB it can't see what''s in it and then chokes.  Once the network folks gave me these rights, it ran just fine.
    Another quirky SSIS bug...

Viewing 5 posts - 1 through 4 (of 4 total)

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