SSIS File System Task: "The network path was not found"

Erik Nikolai 21 Reputation points
2022-12-05T09:23:08.937+00:00

We've got an SSIS-job that needs to copy an xlsx-file between 2 network drives:

  • Source: \sourcedrive\Source\excelfile.xlsx
  • Target: \targetdrive\Target\

Trying to make this work using a simple "File System Task". And it does, but only when I execute the task via my personal user.

When the SSIS-job runs as scheduled (executed by the SSIS service account), the File System Task fails:

File System Task: Error: An error occurred with the following error message: "The network path was not found".

We know that \targetdrive works fine. It's located on the same server that SSIS runs on. If I use \targetdrive as both the source and target, the job runs & copies successfully.

So \sourcedrive is the problem. Although we've verified that the SSIS service account user has been granted read/write permission to the network drive.

Do we need to establish a Connection Manager to \sourcedrive in the SSIS-project (even though the file copy works fine when the task is executed via my personal user) in order for it to detect the network drive? And if so, do we need to configure the file copy using something other than the File System Task?

I'm working in Windows 10 (x64), and Visual Studio 2017, with SQL Server Data Tools 15.1.6. Need to use these old versions due to compatibility issues.

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,452 questions
0 comments No comments
{count} votes

Accepted answer
  1. Olaf Helper 40,816 Reputation points
    2022-12-05T14:06:46.537+00:00

    It's a permission issue.
    By default the package is executed under the service account and that one don't have permissions to access then network share.
    Either grant read/write permissions for the service account on the share or create & use a SQL Server-Agent proxy account with your credentials.
    See Create a SQL Server Agent proxy

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. YufeiShao-msft 7,056 Reputation points
    2022-12-06T02:53:03.847+00:00

    Hi @Erik Nikolai

    It may be due to the permissions, the service account user should have access to the share and path,
    others also find use "Rename File" operation can replace moving the file, you can try it.

    -------------

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments