We have a simple import SSIS package that imports data from flat file on a network share to our SQL database table.
After we deploy the package into SSIS catalog, we execute from the SSIS catalog by right click execute, then if fails with message of cannot open the file, the file is on the network share, and I do have full permissions on it.
The package has no problem to execute either in Visual studio or SQL agent job, or if deployed to file system.
I understand this could be a Kerberos authentication issue. But our server is not configured as Kerberos. And I don't want to require network admins to set up Kerberos authentication for just this small issue. Plus it worked in other places like I described above.
I thought SQL 2016 could fix this, but apparently not, Any other recommendations and suggestions?
Thanks
SQLFriend