Search code examples
sqlsql-serverssisetlssis-2012

SSIS File System Task Error while copying files between servers


I can copy files between two servers say Server A and Server B manually and I have permissions to folders on either side.

I am using File System Task to Copy files.

When my Source and Destination are within the Server the Package works fine in visual studio as well as SSISDB.

When my Source and Destination are in different Servers the Package works fine in visual studio but package fails in SSISDB. It is saying access is denied. My Account is mapped to SSISDB.

Any idea to solve this issue.

The package runs fine using the the SQL Server Agent JoB. The job is run through the proxy account.

Any way we can configure Package to Run through proxy account.

Error Screenshot

enter image description here


Solution

  • First of all @Nick.McDermaid provided a very helpful link in the comments to learn more on Which user credentials does Integration Services Catalog use to execute packages?

    Suggested Solutions

    After searching there are many issues that may causes this problem, so i will provide many solutions that can solve your problem.

    When Running package SSISDB

    1. SQL Server Accounts Permissions

    Add Read & Write permissions to the The account you are logged in on the specified paths

    2. Add a windows authentication to the Network account

    You can add a Windows authentication login for the network account (used as proxy in sql server agent) and run the package using it.

    When Running package from SQL Agent

    This is not your case, but these infos may helps

    1. SQL Server Accounts Permissions

    Add Read & Write permissions to the following accounts on the specified paths:

    • NT SERVICE\SQLSERVERAGENT
    • NT SERVICE\MSSQLSERVER

    2. Setting up a Proxy

    You can setup a proxy for the SSIS package and run the job using that proxy account.

    You can refer to one of the following links to learn more:

    3. Map Network Drives to SQL Server instance

    Some articles suggests to map the network drives you are using on SQL Server (not the OS).You can refer to one of the following links to learn more:

    4. Adding SysAdmin Role

    Add SysAdmin Role to the following accounts:

    • NT SERVICE\SQLSERVERAGENT
    • NT SERVICE\MSSQLSERVER

    Other Links having Similar issue