This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(76.8, 6%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERK%3C/text%3E%3C/svg%3E)
Hello, I have a few ssis jobs. I suddenly started getting the following error in these jobs. On the development side, the jobs are working and there are no problems, no changes have been made.
I need this problem solved urgently
ERROR:
The login is from an untrusted domain and cannot be used with Windows authentication”
Are you executing the packages via a SQL Server Agent job? Do you have a RunAs account specified?
Yes, jobs run on SQL server agent. Jobs ownership sql authentication. They have a sysadmin permission.
![](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(176, 24%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
Consider using SQL Server Authentication instead of Windows Authentication for your SSIS package connections. This involves providing a username and password explicitly in your SSIS package connection managers.
Is this a SSIS job step type? What is the RunAs account?
Hi @Mohammed Altamash Mohammed Suleman Khan ,
This happens with windows authentication in the steps in the ssis job. I can log in to SQL with the user connected to the ssis job. It does not appear to be expired.
Hi @Dan Guzman ,
Yes this is ssis step. When you say RunAs, do you mean executed as user: XX?
This happens with windows authentication in the steps in the ssis job. I can log in to SQL with the user connected to the ssis job. It does not appear to be expired.
Exactly how have you connected the user with the SSIS job? Can you show a screenshot?
@Erland Sommarskog Hi,
Normally, there was config information in this section. In an instant they were all gone. I can't believe I'm experiencing this.There was a sql authentication user here before.
I want to solve this problem
I solved this problem
Hi @Rabia Kurnaz, Glad to hear that, could you please share your solution so other user with similar problem could see this, really appreciate for your contribution.
Hi @ZoeHui-MSFT , I changed the server name. I used the hostname. I think it's a DNS Problem. The infrastructure team will examine the problem.
Hi @Rabia Kurnaz,
First check your Active Directory account is not locked out and the password has not expired.
Secondly, you may use proxy account to run the job, make sure the account has full permissions to your server and the source server.
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.
Hi @ZoeHui-MSFT ,
I checked AD and I don't see any problem.
Hi @ZoeHui-MSFT , We determined that the password was not expired via AD. Configurations have already been made with the SQL user.
Hi @Rabia Kurnaz, Have you tried to use proxy account to run the job?
Hi @ZoeHui-MSFT , When we first created the jobs, we set them up as proxy acc. I think the incident is not actually authorized. Can't trust the server.