August 25, 2011 at 2:07 pm
The goal of my package is to create and FTP an extract file in three steps:
1)Execute some SQL to create a view
2)Export view to Flat File where the file is dynamically named with date stamp
3)FTP file that was just created
using a well known link...
I have entered the following expression in the connection string property of a Flat File Connection (for the export) and a File Connection (for the FTP put).
@[User::SharePath] + "ORG_DEPT_EXTRACT" +
RIGHT("0" + (DT_STR,4,1252) DatePart("yyyy",getdate()),4)+
Right("0" + (DT_STR,4,1252) DatePart("m",getdate()),2) +
Right("0" + (DT_STR,4,1252) DatePart("d",getdate()),2) + ".txt"
Now the package won't save; instead it throws this error :
"Error1Error loading OrgDeptExtract.dtsx: The connection "\\server\folder1\folder2\ORG_DEPT_EXTRACT20110825.txt" is not found. This error is thrown by Connections collection when the specific connection element is not found. \\server\folder\ssis\testftp\testftp\OrgDeptExtract.dtsx11"
What the Monkey? It's as if the package chokes because the file referred to in the connections doesn't exist until created by the second step
Any thoughts?
August 25, 2011 at 2:14 pm
Set the DelayValidation property of your File Connection to True.
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
August 25, 2011 at 2:20 pm
Thank you for responding so fast!
As soon as I changed that property and closed the dialog box I got this error:
"TITLE: Microsoft Visual Studio
------------------------------
Nonfatal errors occurred while saving the package:
Error at OrgDeptExtract: The connection "\\server\folder\folde\ORG_DEPT_EXTRACT20110825.txt" is not found. This error is thrown by Connections collection when the specific connection element is not found.
------------------------------
BUTTONS:
OK
------------------------------
Added Note: I have turned off all logging in this package
August 26, 2011 at 11:29 am
Is the error happening when you run the package, or just when you save it?
Either way, the best way to deal with these sort of situations, is to just not use variables when setting up your project. Do everything using real files and real values.
Once you know everything works properly, *then* change them to variables.
In your case, you're exporting to a file with a dynamic date. So, instead of a dynamic date, put a static date in, create your output file, and map all the values.
Run your project, and once you're satisfied with the results, switch DelayValidation to False on your Flat File Connection, and put the variables in.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply