I am tryingto create a package configuration which won't give this error , when its checked-out by other team members (using TFS) and runned: Warning: 0x80012012 at Package: The configuration file name "C:SomePath\filename.dtsConfig" is not valid. Check the configuration file name. Warning: 0x80012059 at Package: Failed to load at least one of the configuration entries for the package. Check configuration entries for "ConfigurationFileName 1" and previous warnings to see descriptions of which configuration failed. It runs good without any warning at my desktop. But it gives warning to other team member. But at both places the SSIS runs good, even if there are warnings. avm

So here is the obvious question -: Does C:SomePath\filename.dtsConfig exist on the other team members machine? And your path should be C:\SomePath\filename.dtsConfig You're missing a \Chuck Pedretti | Magenic North Region | magenic.com

Thanks for the quick reply!! No. the path does not exist because we have included the dtsConfig file into our project and then checked-in in TFS. I don't want the team members to again create another dtsConfig file, because they can not edit the one which I created as the file does not exist in on his PC. Sorry about the URL: I missed it in here while giving example. avm

Thanks for the quick reply!! No. the path does not exist because we have included the dtsConfig file into our project and then checked-in in TFS. I don't want the team members to again create another dtsConfig file, because they can not edit the one which I created as the file does not exist in on his PC. Sorry about the URL: I missed it in here while giving example. avm Well, then you need to change your package so that it is not looking in a hard coded location for your config file. Having the config in the project doesn't mean that the package will be able to access it. This is a good argument for having dev teams use the same local paths for their TFS root.Chuck Pedretti | Magenic North Region | magenic.com

Thanks!! Yes, I agree with you. But, it seams that it is using the config file included with the project. Cause I am using totally different server and they have no idea about that server authentications. And the SSIS is fetching the data from my server. How can I not give hard coded location in "Specify Configuration settings directly" hwen I choose "XML Configuration file" in Configuration file. Is there any way I can use variables in here. Using same local paths is good idea. But the thing is we are going to export this SSIS package to client location and I want to avoid this step.avm

Thanks!! Yes, I agree with you. But, it seams that it is using the config file included with the project. Cause I am using totally different server and they have no idea about that server authentications. And the SSIS is fetching the data from my server. How can I not give hard coded location in "Specify Configuration settings directly" hwen I choose "XML Configuration file" in Configuration file. Is there any way I can use variables in here. Using same local paths is good idea. But the thing is we are going to export this SSIS package to client location and I want to avoid this step. avm I doubt it is using the config file since it is saying that it isn't - Might want to check if you have the connection information saved into the package as well. As for the hard coded location, you can change the path to a relative path. Chuck Pedretti | Magenic North Region | magenic.com

ok. I will try this.... Thanks :)avm