SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,004 questions
SQL Agent SSIS job step fails with "The login is from an untrusted domain and cannot be used with Integrated authentication"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 59%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPB%3C/text%3E%3C/svg%3E)
Peter Bishop
161
Reputation points
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.
{count} votes
-
Greg Low 1,770 Reputation points Microsoft Regional Director2024-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?) -
Ruel G. Cabusas 210 Reputation points2024-05-24T02:12:27.6066667+00:00 Hi Peter Bishop,
Have you tried running the job manually in the Integration Service Catalog? If not, kindly try and provide feedback if it works or not so we can proceed to our diagnostics.
I also encountered this issue before, I tried running it manually in Integration Service Catalog and it works but if run using SQL Server Agent I got same error message. I solved it by changing the Integration Services login account and it worked.
But still, we will go into diagnostics first.
Sign in to comment
Sign in to answer