SQL Server Home
SSIS File Connection makes the dtsx package think it's corrupt
3/2/2007 9:08:32 AM
User(s) can reproduce this bug
I am setting the path for a flat file to a directory my user account does not have access to. Everything works at runtime, when I open the dtsx package claims to be corrupted and I get errors stating the ConnectionString cannot be written to the property.
SQL Server 2005 SP2 - Enterprise Edition
Windows XP SP2 Professional
Operating System Language
Steps to Reproduce
1) Create new SSIS project.
2) Right click Connection Managers, click 'New Connection...'
3) Select File, Click Add
4) Select an existing file, and click OK.
5) In the Connection Managers windows, right click the file you just created, click properties.
6) Expand Expressions and click the ellipsis.
7) For property select ConnectionString, click the ellipsis in the expression column.
8) Enter something similar to this:
** You must not have permissions to this **
9) Click ok, click ok.
10) Save the file, ignore the error, close the dtsx package.
11) Reopen the dtsx package.
The package thinks it is corrupt.
The package should not think it is corrupt.
to post a comment.
Please enter a comment.
on 4/28/2008 at 2:35 PM
We have only been able to reproduce the problem if we enter the expression without including the double quotes (") which we believe is required for string constant.
Once we reproduced the problem, we did see an error message from BIDS saying the package "might" be corrupted. This is a general message for any package we fail to load and we do not think we need to change anything here. From the actual error list (tab), you should be able to see the real error messages and there is nothing there that says the package is corrupted. As a result, we are closing this case. If you disagree, please feel free to open a new case with us. We appreciate your time and effort and moreover, your support of SSIS.
to post a workaround.
Please enter a workaround.
Integration Services Project1.zip (restricted)
© 2014 Microsoft