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(137.6, 40%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I have the following trigger database trigger 
and then there is a error in the errorlog
why is that ?
Hi @michaelchau,
Is the reply helpful?
If the reply helped, please “Accept Answer” and upvote it to close this case.
Otherwise it will always be open status.
BR,
Mia
The login failed message is not related to the trigger both are mutually exclusive events. The reason for login failure is that the login which you are using is not present in the SQL Server logins. May be it was removed. Please check
![](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(35.2, 30%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
These are most likely not related. The trigger should not generate such a message in the errorlog. Can you pose a full repro (T-SQL we can execute which reproduces the situation)?
Hi @ michaelchau,
Based on the error message, there is no login for the user, so you can try to Create a Login and then use the new log in to alter the trigger again. You can use SSMS to connect from a Windows machine and create a login or do it in T-SQL.
BR,
Mia
If the reply helped, please do “Accept Answer ” and upvote it.--Mia
Hi @michaelchau,
Is the reply helpful?
If the reply helped, please “Accept Answer” and upvote it to close this case.
Otherwise it will always be open status.
BR,
Mia
but there is no way I need to add this computer account to my sql server
And once the trigger is triggered, the error appear .
So you are absolutely 100% certain that it connects to the trigger? With no doubt, whatsoever?
If so, I'd open a case to file a bug with MS. I can't imagine how such a trigger can produce that error message, and if it truly does I suspect a bug in the product.