SQL Agent SSIS job step fails with "The login is from an untrusted domain and cannot be used with Integrated authentication"

Peter Bishop 161

A user raised an issue with me today where a SQL Agent SSIS job step was failing with:

Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication

The SSIS step was using an SSIS subsystem proxy rather than the SQL Server Agent account.

I tried recreating the job step and even abstracted the step into a standalone job, all without solving the problem

After some investigation (and Google) I found a reference that this could be caused by using a DNS alias in the SSIS catalog connection string rather than the actual hostname. Changing this to use the instance's hostname fixed the problem.

However I have several other equivalent job steps which do use the same DNS alias without issue and I'm pretty sure that this job step hasn't been changed and was previously working without issue.

Can anyone advise why:

DNS alias fails in this way but hostname works?
Why this works in some job steps but not in others?

The actual SSIS package doesn't even try to start so I don't think it's related to differences in the SSIS packages.

Thanks.

Greg Low 1,495 Reputation points Microsoft Regional Director

2024-02-12T11:05:58.85+00:00

Easiest way to test is to just create a simple package that shows the identity that it's running as, and puts it as an output into the logs.
Are all the job steps configured to use the same proxy?
Are they all the same types of job steps? (And has the proxy been enabled for the types of job steps?)

Share via

SQL Agent SSIS job step fails with "The login is from an untrusted domain and cannot be used with Integrated authentication"