So,I've run into an issue that has been posted about quite a bit online, but in all the posts, I've yet to find an actual workaround/fix for the issue.
I have several SSIS packages I created in SSDT. These packages all run successfully in SSDT.
I then migrate these packages to my SSISDB catalog on our test server. All of the packages reference a source server which is NOT the server the packages are deployed to. When attempting to run any of the packages they fail with the following error:
Login failed for user NT AUTHORITY\ANONYMOUS LOGON. Reason: Token-based server access validation failed with an infrastructure error.
I know that when you run a package directly from the SSISDB catalog, it uses the credentials of the account you are logged into SSMS with. The account I am logged into SSMS with DOES have permissions to connect to and query the server and database being referenced in the packages.
When I create a SQL Server Agent job and run the packages, they connect and execute fine.
I've read where people have stated if the package references a different server, then you cannot access that server because of a "security issue" that doesn't allow packages to do that. Obviously, for some reason SSISDB is stripping the credentials from the connection attempt and passing in ANONYMOUS.
If that is the case, that makes executing from SSISSB essentially pointless if you are doing any kind of data flow task that requires access to another server/data source. I shouldn't have to create an individual job for every single package I've created in order to just test!
I would just like someone to definitively tell me whether or not one can actually execute a package from SSISDB that references another server/share location other than the server the packages are deployed to.
Thanks!!
A. M. Robinson