"File not found" when published to Integration Service Catalogs on SQL Server 2016

Greg Chen 30 Reputation points
2024-01-23T13:39:07.26+00:00

Hello fellow developers, I currently have a SSIS package that uses 4 systems tasks to copy and move files between folders on a share drive and SFTP. When I run it and deploy it everything works but when I deploy it to the Integration Services Catalogs, the packages fails and I get OnError messages "Could not find the file "\[UNC]\SharedData$....\myfile.csv" Has anyone run into this error before and how can I resolve it? Thank you in advance and have a nice day. User's image

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
3,065 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,705 questions
SQL Server | Other
0 comments No comments
{count} votes

Accepted answer
  1. ZoeHui-MSFT 41,496 Reputation points
    2024-01-24T02:54:24.7766667+00:00

    Hi @Greg Chen,

    Please ensure that the account running SSIS package in agent job has access to ALL folders and files in the path you are accessing.

    You may use a proxy account to run the job which has full permission.

    create-a-sql-server-agent-proxy

    running-a-ssis-package-from-sql-server-agent-using-a-proxy-account

    Regards,

    Zoe Hui


    If the answer is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Danish Gul Khattak 335 Reputation points
    2024-01-23T14:04:45.99+00:00

    It seems like the issue might be related to the package running under different permissions when deployed to the Integration Services Catalog. Ensure that the service account running the SQL Server Integration Services (SSIS) service has the necessary permissions to access the shared drive and SFTP location. Additionally, use fully qualified paths in your SSIS package to avoid any UNC path resolution problems. Double-check and update your file paths accordingly.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.