In my package, I have several DataFlows that have error outputs where the errors are written to flat files (.txt). The files are located in the following directory:

\\server1\groups\Development\ETLFiles\ETL_Error_Fi les

There are 13 of these files. Each has its own flat file connection manager. The connection string of each connection manager is based on an expression. A sample of three look like this:

@[User::ErrorFilePath]+"AddressCSVProcessing_CityZipCodeStagingErrors.tx t"
@[User::ErrorFilePath]+"AddressCSVProcessing_County2ProductionErrors.txt "
@[User::ErrorFilePath]+"AddressCSVProcessing_CityTypeCityStagingErrors.t xt"

The @User::ErrorFilePath package variable (at the package level) has this value:

\\server1\groups\Development\ETLFiles\ETL_Error_Fi les\

This value has been stored in a SQL Server package configuration. A SQL Server Job executes the package. The Job (and package) are run by the SQL Agent Account (domain\sqlmaint). This account has full control over \\server1\groups\Development\ETLFiles and all subdirectories.

If the files at \\server1\groups\Development\ETLFiles\ETL_Error_Fi les\ are deleted before the package runs, the files are recreated during package execution, and there are no errors. If the package runs and the files exist, I get the following errors:

From Job History:

12/02/2008 13:28:28,CA_AddressCSVProcessing,Error,1,SQLIISDEV \SAND,CA_AddressCSVProcessing,AddressCSVProcessing _Steps,,Executed as user: domain\sqlmaint. ....00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:28:28 PM Error: 2008-12-02 13:28:31.26 Code: 0xC001401E Source: AddressCSVProcessing Connection manager "USZipCodes" Description: The file name "\\server1\groups\Development\ETLFiles\ETL_Data_Fi les\zip-codes-database-STANDARD.csv" specified in the connection was not valid. End Error Error: 2008-12-02 13:28:31.26 Code: 0xC0202070 Source: AddressCSVProcessing Connection manager "USZipCodes" Description: The file name property is not valid. The file name is a device or contains invalid characters. End Error Error: 2008-12-02 13:28:31.28 Code: 0xC001401E Source: AddressCSVProcessing Connection manager "USZipCodeDetailStagingErrors" Description: The file name "\\server1\groups\Development\ETLFiles\ETL_Error_F iles\AddressCSVProcessing_USZipCodeDetailStagingEr rors.txt" specified in the... The package execution fa... The step failed.,00:00:03,0,0,,,,0

As mentioned in the error, there is a CSV file that I'm having a similar problem with.

From sysdtslog90:

id event computer operator source sourceid executionid starttime endtime datacode databytes message
2503 OnError SQLIISDEV OCINTERNAL\sqlmaint USZipCodeDetail Staging 0707B12F-0FFF-418A-9A37-29E8F98B1223 B64F414B-2396-4E3F-A4FC-693A7FAA36AA 2008-12-02 13:28:31.000 2008-12-02 13:28:31.000 -1071636464 0x No destination flat file name was provided. Make sure the flat file connection manager is configured with a connection string. If the flat file connection manager is used by multiple components, ensure that the connection string contains enough file names.
2504 OnError SQLIISDEV OCINTERNAL\sqlmaint AddressCSVProcessing 0C52DD4C-D71E-48E9-AE0F-D4724F13E0B6 B64F414B-2396-4E3F-A4FC-693A7FAA36AA 2008-12-02 13:28:31.000 2008-12-02 13:28:31.000 -1071636464 0x No destination flat file name was provided. Make sure the flat file connection manager is configured with a connection string. If the flat file connection manager is used by multiple components, ensure that the connection string contains enough file names.
2505 OnError SQLIISDEV OCINTERNAL\sqlmaint USZipCodeDetail Staging 0707B12F-0FFF-418A-9A37-29E8F98B1223 B64F414B-2396-4E3F-A4FC-693A7FAA36AA 2008-12-02 13:28:31.000 2008-12-02 13:28:31.000 -1073450982 0x component "USZipCodeDetail Staging Errors" (534) failed the pre-execute phase and returned error code 0xC0202010.
2506 OnError SQLIISDEV OCINTERNAL\sqlmaint AddressCSVProcessing 0C52DD4C-D71E-48E9-AE0F-D4724F13E0B6 B64F414B-2396-4E3F-A4FC-693A7FAA36AA 2008-12-02 13:28:31.000 2008-12-02 13:28:31.000 -1073450982 0x component "USZipCodeDetail Staging Errors" (534) failed the pre-execute phase and returned error code 0xC0202010.
2521 OnTaskFailed SQLIISDEV OCINTERNAL\sqlmaint USZipCodeDetail Staging 0707B12F-0FFF-418A-9A37-29E8F98B1223 B64F414B-2396-4E3F-A4FC-693A7FAA36AA 2008-12-02 13:28:31.000 2008-12-02 13:28:31.000 0 0x

The Job is running the package from the file system: \\Sqliisdev\ETLFiles\ETL_DeployedPackages\AddressC SVProcessing.dtsx

The package ProtectionLevel is set to 'Don't Save Sensitive'. Each of the connections to the error files is configured to overwrite the files.

What could be causing this problem? Why is it that the files can be created with the package runs, but not written to?

Thank you for your help.

cdun2