July 12, 2018 at 9:14 pm
I upgraded a SQL 2014 to 2017 server.
Today I see SQL log filled up with error below :
Login failed for user 'mydomain\myservername$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
I know we don't use this login, not sure which causes this.
During upgrade, I did once use local system as service account then I change it to a domain account.
The server runs OK other than this login error.
How can I fix this?
Thanks
July 16, 2018 at 6:01 pm
sqlfriends - Thursday, July 12, 2018 9:14 PMI upgraded a SQL 2014 to 2017 server.
Today I see SQL log filled up with error below :
Login failed for user 'mydomain\myservername$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]I know we don't use this login, not sure which causes this.
During upgrade, I did once use local system as service account then I change it to a domain account.
The server runs OK other than this login error.
How can I fix this?
Thanks
The change with local system could be it - is the myservername the name of the server that has the error? It could be a local account trying to log into SQL Server.
Did you use SQL Server Configuration manager to make the change to the domain account? Did you check in Configuration Manager if any of the other services are using local system, network service?
There are plenty of posts where they tell you to just add the machine account as a login for SQL Server but that doesn't really address the issue.
Sue
July 20, 2018 at 1:40 pm
I came across this situation many times, you will have login name and client IP in the error message, ask your application team to check whether a job or process still trying to access your db server,
alternatively you can run the profile trace only for the audit login, audit logout failed and audit logout events, which will surely tells you why its logging
sunny
July 24, 2018 at 9:34 am
i think someone tried logging in from Management studio that do not have the permission and SQL server is setup to capture fail login in the its setting.
what is the problem?
July 24, 2018 at 10:53 am
Nassan - Tuesday, July 24, 2018 9:34 AMi think someone tried logging in from Management studio that do not have the permission and SQL server is setup to capture fail login in the its setting.
what is the problem?
Not if you have the same error as:
Login failed for user 'mydomain\myservername$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
That is local to the server and it is a computer account. Look at the user and the client in the error.
Sue
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply