Login failed for user 'DOMAIN\MACHINENAME$'. Reason: Could not find a login matching the name provided. RRS feed

  • Question

  • I am following this 2016 article to setup my DPM 2019 protection with SharePoint 2019. After I setup the first protection group (it only contain one SharePoint Web Front End server) and start the first consistency check. It failed immediately.

    Please note that our DPM server and SharePoint sever are installed under 2 domains. But 2 domains have established two-way trust.

    After some troubleshooting in SQL server log here is the error message.

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

    By following the instruction "Remember that for DPM runs as Local System and to backup SQL Server databases it needs sysadmin privileges on that account for the SQL server. On the SQL Server you want to back up set NT AUTHORITY\SYSTEM to sysadmin." , we have add "NT AUTHORITY\SYSTEM" to SQL server's sysadmin group.

    According to some SQL forum, I also need to grant "DOMAIN\MACHINE$" sysadmin permission. Is it true?

    Please advise. Thanks.

    • Edited by Mark Lui Monday, October 19, 2020 7:29 AM
    Monday, October 19, 2020 7:26 AM

All replies

  • Hi,

    You just need to provide NT AUTHORITY\SYSTEM as sysadmin permission to the SQL server so that DPM can take a backup for the SQL DBs. You don't need to add the DOMAIN\MACHINE$ to the sysadmin, its not mandatory.

    Also, don't forget to enable the SharePoint writer so that backup can be taken. By default it is not enabled, we need to enable to manually. Follow below steps:

    On the WFE server at a command prompt navigate to <DPM installation location>\bin\ and run ConfigureSharePoint [-EnableSharePointProtection] [-EnableSPSearchProtection] [-ResolveAllSQLAliases] [-SetTempPath ]

    Refer below link for more details:


    Aayoosh Moitro

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, October 19, 2020 7:42 AM
  • Hi,

    There should be no need to add the DOMAIN\MACHINE$ to the sysadmin group.

    You can also refer to the following article:

    Best regards,

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 19, 2020 7:43 AM
  • Dear all,

    Thanks for your help. It is suddenly working now. I think it takes some hour for DPM complete the scanning of SQL server?

    hmmmm, really non-sense but it is working now.

    Monday, October 19, 2020 9:07 AM