How to fix NT AUTHORITY\ANONYMOUS LOGON login failure during MS SQL Server installation

Lemons, Terry 1 Reputation point

Hi - I'm trying to install MS SQL Server on Microsoft Windows Server 2022 Standard 10.0.20348 Build 20348. I've tried installing both MS SQL Server 2019 and 2022. The installation fails with:

Detailed results:

Feature: Database Engine Services

Status: Failed

Reason for failure: An error occurred during the setup process of the feature.

Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

Component name: SQL Server Database Engine Services Instance Features

Component error code: 0x84BB0001

Error description: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Error help link:

I've been searching but can't find an article describing what I need to change in order to solve this error. Thanks!

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,850 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Erland Sommarskog 102.2K Reputation points

    The errors occurs at the very end of the installation. Setup has started SQL Server which has performed adaption of the system database, including setting the collation. All that went fine.

    Then Setup wants to connect to make the final configuration, but this is where it fails. Since SQL Server has started SQL Server in single-user mode, it expects that it can connect as sysadmin. That is, it assumes that it is running as local administrator. But if you have locked down the service account for MSI, this may not be the case.

    Or for some other reason, the admin token is missing, and therefore the connection is not as sysadmin, and at this point sysadmin is the only one that can connect, because no logins have been created.

    I don't know if this information is enough to understand what is going on - but I would be surprised if it is. Nevertheless, this is about as much I can say. If you can open a support case, I think that would be the best way out.