Flat File Destination failed the pre-execute phase and returned error code 0xC020200E.

On SQL Server 2012 (or newer), when you are running a SSIS package (which accesses a network share), you can retrieve the following error message:

Flat File Destination failed the pre-execute phase and returned error code 0xC020200E.
and
Cannot open the datafile "\\<remoteserver>\<remotefile>"



This is a permissions issue accessing the file on the network share.

When you start the execution of a SSIS package from SSISDB, this will start in background the ISServerExec.exe using the Login credentials. You must check that the Windows user, with which you are logged in on the SQL Server instance, has access on the network share.

You may still receive this error message, despite the fact that the user has full permissions on the network share, when you are connected remotely to the SQL Server instance. In this situation the SQL Server service account is not able to delegate the windows user. On the server where the share is located, you will see an entry in the Security event log:

An account was successfully logged on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

Impersonation Level: Impersonation

New Logon:
Security ID: <domain>\<SQL Server hostname>$
Account Name: <SQL Server hostname>$
Account Domain: <domain>
Logon ID: 0x2435C7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x0
Process Name: -

Network Information:
Workstation Name: <SQL Server hostname>
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: NtLmSsp 
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): NTLM V2
Key Length: 128

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The impersonation level field indicates the extent to which a process in the logon session can impersonate.

The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

There are two possible reasons why this would fail:
1. The connection to the SQL Server is not made over KERBEROS. You can test if you are running KERBEROS or NTLM by running the following statement.

SELECT auth_scheme FROM sys.dm_exec_connections WHERE session_id = @@spid ;

If you get NTLM,verify that the SPNs are set correctly for the SQL Server instance.

2. The SQL Server service account does not have delegation permissions