A family of System Center products that enable enterprise-wide management of virtual machines.
Grant the SQL Server Database Engine service identity—not the VMM service account—AD authorization-read access by adding its effective domain principal to Windows Authorization Access Group, then restart SQL Server and VMM.
Apply the fix
The report shows that VMM successfully opened VirtualManagerDB, but SQL Server failed while resolving the Windows principal domain\SCVMM-DB:
- SQL error 15404, state 19
- Windows error 0x5 (Access denied)
- VMM error SQLInsufficientPermissions (2607)
VMM 2025 requires the SQL Server service to run under an identity that can access AD DS. A local user account is not supported for this purpose.^1^
- On the SQL Server, open SQL Server Configuration Manager.
- Select SQL Server Services.
- Open the properties of SQL Server (
<instance>) and note the Log On As identity. - Determine the AD principal that must receive access:
- Domain account or gMSA: use that account, such as
DOMAIN\SqlService. - Local System, Network Service, or a virtual account such as
NT SERVICE\MSSQLSERVER: use the SQL Server computer account,DOMAIN\SQLSERVER$. Virtual accounts access network resources as the computer account.^2^ - Local user: change it to an appropriate domain account, managed service account, or Local System because VMM specifically says not to use a local user.^1^
- Domain account or gMSA: use that account, such as
- In Active Directory Users and Computers:
- Enable View → Advanced Features if needed.
- Open the Builtin container.
- Open Windows Authorization Access Group.
- Add the effective SQL identity identified above.
This group grants the account permission to read the dynamically calculated tokenGroupsGlobalAndUniversal authorization information used when resolving Windows users and groups.^3^
- During a maintenance window, restart:
- The SQL Server Database Engine service.
- The System Center Virtual Machine Manager service.
Restarting SQL makes databases on that instance temporarily unavailable.
Validate the referenced principal
SQL error 15404 also occurs when the named Windows principal is invalid, misspelled, locked out, or cannot be trusted by the SQL service account’s domain.^4^
Verify that:
-
domain\SCVMM-DBstill exists in AD and is the intended user or group. - The effective SQL service domain account is not locked out.
- If the SQL server, SQL service account, and
SCVMM-DBprincipal are in different domains, the required trust exists. VMM requires a two-way trust when the VMM and SQL computers are in different AD domains.^1^ - No explicit deny or hardened AD ACL prevents the SQL identity or Windows Authorization Access Group from reading authorization attributes.
If the Windows Authorization Access Group itself no longer has its default TGGAU permissions, an AD administrator must restore those permissions or grant equivalent narrowly scoped read access.^3^
If the SQL service identity must be changed
Change it through SQL Server Configuration Manager, not services.msc; Configuration Manager also updates SQL-related permissions and protected settings.^5^
After the change:
- Restart SQL Server.
- Confirm
VirtualManagerDBis online. - Start the VMM service.
- Confirm that no new SQL event 15404 is recorded.
SPN repair is not the first action here: the captured failure is an AD authorization lookup denied inside an already-open SQL connection, rather than a failure to establish the SQL connection.
References