Login failed for user 'domain\machine$'. Reason: Could not find a login matching the name provided.


  • Hi Team,

    There is a sharepoint application trying to connect SQL server db and they are facing intermittent connectivity issue.While checking the SQL log it is flooded with below error message.Application is using the domain account and it has all required privileges.

    Login failed for user 'domain\machine$'. Reason: Could not find a login matching the name provided.

    SQL server 2012 Enterprise edition

    It was working fine for last 3 years and suddenly since last couple of days we are facing this issue.

    There was no changes or patch applied to wither to SQL or App server.

    Please suggest. 

    Jumat, 03 November 2017 15.45

Semua Balasan

  • Try looking in here, seems to be the same problems you are experiencing:

    TLDR: In the SQL Server Login Properties - New Login dialog box, in the Name box, enter NT AUTHORITY\NETWORK SERVICE.

    Jumat, 03 November 2017 15.56
  • Hi Chinmay Nayak,

    >> Login failed for user 'domain\machine$'. Reason: Could not find a login matching the name provided.

    When the error message above occurred, it means that a process running as NETWORK SERVICE or as LocalSystem has accessed a remote resource, has authenticated itself as the machine account and was denied authorization.

    When access is denied to a machine account, then access must be granted to the machine account. If the server refuses to login 'DOMAIN\MACHINE$', then you must grant login rights to 'DOMAIN\MACHINE$' not to NETWORK SERVICE. You may refer to this thread as reference.

    If you have any other questions, please let me know.



    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    • Disarankan sebagai Jawaban oleh Hannah Yu Senin, 20 November 2017 04.04
    Senin, 06 November 2017 09.14
  • Users are facing intermittent access issue.I don't think  domain\machine$ is the problem.I think this error message is misguiding.Users are using a different windows login id to access the database.

    SQL error log flooded with domain\machine$ error messages and its not possible to add each and every machine account.

    Rabu, 08 November 2017 04.35
  • As Hannah says, the error comes from something that runs under a local account. Could be a service, but it could also be local computer accounts. Hm, could it happen if users logs in with cached credentials, but are never authenticated by the AD, because the AD is unavailable?

    Erland Sommarskog, SQL Server MVP,

    Rabu, 08 November 2017 21.41
  • Run a Profiler trace for the event "Audit Login Failed" and see the Application Name that is trying to login.

    Might be the service "SQLServerCEIP" which is SQL Server 2016 Customer Experience Improvement Program, which comes enabled by default in SQL 2016 and hence causing this erratic behavior if the server is not connected to Internet.

    How to disable it:

    1) Set these Registry entries to 0

    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\130\CustomerFeedback=0
    \Software\Microsoft\Microsoft SQL Server\130\EnableErrorReporting=0
    \Software\Microsoft\Microsoft SQL Server\MSAS13.TESTINSTANCE\CPE\CustomerFeedback=0
    \Software\Microsoft\Microsoft SQL Server\MSAS13.TESTINSTANCE\CPE\EnableErrorReporting=0
    \Software\Microsoft\Microsoft SQL Server\MSRS13.TESTINSTANCE\CPE\CustomerFeedback=0
    \Software\Microsoft\Microsoft SQL Server\MSRS13.TESTINSTANCE\CPE\EnableErrorReporting=0
    \Software\Microsoft\Microsoft SQL Server\MSSQL13.TESTINSTANCE\CPE\CustomerFeedback=0
    \Software\Microsoft\Microsoft SQL Server\MSSQL13.TESTINSTANCE\CPE\EnableErrorReporting=0
    \Software\Wow6432Node\Microsoft\Microsoft SQL Server\130\CustomerFeedback=0
    \Software\Wow6432Node\Microsoft\Microsoft SQL Server\130\EnableErrorReporting=0

    Then stop and disable these services:

    SQL Analysis Services CEIP
    SQL Server CEIP service
    SQL Server Integration Services CEIP service

    Senin, 09 Juli 2018 15.21