May 7, 2008 at 11:00 am
Hi, I'm trying to 1) create a Raw file on the fly in the directory C:\SSIS, 2) write data to a Raw File Destination in a DFT, and 3) read data from the same raw file using a Raw File Source in another DFT. All three steps occur in the same package.
I have set "ValidateExternalMetadeta = False" for both the destination and source. The destination is also set "WriteOption = Create Always" to ensure that the file gets created if it doesn't exist. The destination is no longer giving me validation errors, but the Raw File Source is alerting me of the following (see below). Is it possible to use a Raw File Destination and Source, created on the fly by the same destination, in the same package? It appears that the source continues to validate, even though I have told it not to do so until runtime.
Thanks!
TITLE: Package Validation Error
------------------------------
Package Validation Error
------------------------------
ADDITIONAL INFORMATION:
Error at DFT Retrieve Location_* Sub-Class Data [RFS LocationTablesData [2350]]: File "C:\SSIS\LocationTablesData.txt" cannot be opened for reading. Error may occur when there are no privileges or the file is not found. Exact cause is reported in previous error message.
Error at DFT Retrieve Location_* Sub-Class Data [DTS.Pipeline]: component "RFS LocationTablesData" (2350) failed validation and returned error code 0x80004005.
Error at DFT Retrieve Location_* Sub-Class Data [DTS.Pipeline]: One or more component failed validation.
Error at DFT Retrieve Location_* Sub-Class Data: There were errors during task validation.
(Microsoft.DataTransformationServices.VsIntegration)
------------------------------
BUTTONS:
OK
------------------------------
May 14, 2008 at 12:39 pm
A former instructor helped me find the answer to my problem.
Click either on the DFT in the Control Flow level or on the canvas in the DFT level to see the package level properties. Set "DelayValidation = True" and it will not attempt to validate the non-existent file.
July 9, 2009 at 10:03 am
Excellent answer! Make sure to thank your former instructor for that! I've read a dozen different work-arounds, but none of them worked around this problem.
To get rid of the red X I guess you have to close and re-open the package, but I have a feeling it'll come back when you try to edit it.
Larry
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply