Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Logon failure: the user has not been granted the requested logon type at this computer (error 1385, 0x569)

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

"Logon failure: the user has not been granted the requested logon type at this computer" is Windows error 1385, hexadecimal 0x569, symbolic name ERROR_LOGON_TYPE_NOT_GRANTED. It means the machine the account tried to use does not give that account the right to sign in the way the request asked. The right that is missing depends on what was doing the signing in: a person joining a computer to a domain, a service starting under a service account, or a Hyper-V host.

Read the log that carries the message, name the right it points to, then find the policy that removed or denied it. Do not add accounts to a policy until you know which one.

What the error means

Microsoft's pages name separate rights, such as "Access this computer from the network" and "Log on as a service". Error 1385 is the refusal of the one that was requested.

Microsoft's system error code list shows the entry as ERROR_LOGON_TYPE_NOT_GRANTED, 1385 (0x569), "Logon failure: the user has not been granted the requested logon type at this computer." Three Microsoft pages tie it to a specific setting.

Domain join. Microsoft's page says: "This error occurs because the domain join user account lacks the Access this computer from the network user right at the domain controller (DC) servicing the domain join operation." The right is checked on the domain controller, not on the computer being joined.

A service that will not start. In Microsoft's SQL Server error 1069 page, event ID 7041 in the System log carries this wording, with the statement "This service account does not have the required user right "Log on as a service."" The page is written for SQL Server services, but the right it names is a general Windows user right, and Microsoft's page for that setting says it "determines which service accounts can register a process as a service."

Hyper-V. Microsoft's live migration troubleshooting page lists "Failed to create Planned Virtual Machine at migration destination: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569)". The page gives no steps of its own for it and points to another Microsoft article for Windows Server 2012 hosts. Microsoft's page gives no cause for this entry.

Microsoft's pages do not cover other uses of the same code, such as scheduled tasks or file shares.

Likely causes

Cause What you see How to confirm
The domain join account lacks "Access this computer from the network" on the DC that served the join Domain join fails with the error; NetSetup.log shows 0x569 Read NetSetup.log on the computer being joined; check the policy that applies to the DCs
The service account lacks "Log on as a service" Service will not start; System event 7041 with the error text Read event 7041; check User Rights Assignment on that server
The service account is listed under "Deny log on as a service" Same event 7041, although the Allow list looks correct Check the Deny entry; Microsoft's page says it can negate the Allow setting
A domain policy overwrites the local setting A local fix works until the next Group Policy update Check which Group Policy objects apply to the server
Hyper-V host, worker process or live migration Event text names 0x80070569 and the virtual machine Microsoft's page gives the symptom only

Prove the cause before changing anything

All of these only read.

For a domain join, open NetSetup.log on the computer that failed to join. Microsoft's page shows the lines that identify this fault:

NetpDsGetDcName: found DC '\\<dc name>' in the specified domain
NetUseAdd to \\<dc name>\IPC$ returned 1385
NetpJoinDomain: status of connecting to dc '\\<dc name>': 0x569
NetpDoDomainJoin: status: 0x569

Note the DC name. That is the controller whose policy you need to inspect.

For a service, open the System event log on the server and find event ID 7041 from Service Control Manager. Microsoft's page shows the description as two lines. The first reads "The MSSQLSERVER service was unable to log on as NT Service\MSSQLSERVER with the currently configured password due to the following error:" and the second reads "Logon failure: the user has not been granted the requested logon type at this computer." Note the service name and the account after "log on as".

Microsoft's page separates that from event 7038, whose descriptions say the account is disabled, the password must be changed, the user name or password is incorrect, the account is locked out, or the domain cannot be contacted. Those are different faults with different fixes.

Then see which policy objects applied to the server. Microsoft's gpresult page says /r "Displays RSoP summary data":

gpresult /r

Run it in an elevated command prompt on the server. It reads policy results and changes nothing.

Example (illustrative): at contoso.com.au the service ErpSync on app01 runs as CONTOSO\svc-erp. After a new policy is linked to the server OU, the service stops starting. The System log on app01 holds event 7041 for ErpSync with the 1385 text. In the local policy console, CONTOSO\svc-erp is not under "Log on as a service". gpresult /r shows the new policy among the applied objects, so a local edit would be overwritten at the next Group Policy update.

Fix

Domain join: the DC policy

Microsoft's page describes the fix as a policy on the domain controllers. It says there is no need to restrict Everyone from reaching DCs over the network, and that you can add a group named "domain joiners" to the policy. Its note says: "Don't add the user directly." It then says to verify that Everyone or the "domain joiners" group has been granted the Access this computer from the network right in the group policy applying to all DCs, which by default is the Default Domain Controllers Policy. The policy must be linked to the organizational unit that hosts the DCs, and the DCs servicing the join must have applied it. Microsoft's note adds: "Place all DC computer accounts in the Domain Controllers OU."

Microsoft's page for that setting warns that on Windows Server or Azure Stack HCI failover clustering, Authenticated Users must stay in it, because removing the group "may induce an unexpected production outage."

Microsoft's page gives these checks and no change steps, so no change is given here. Microsoft's pages give no console steps for editing the Default Domain Controllers Policy. The edit changes who may reach every domain controller over the network, so it needs its own written copy of the policy's current list and its own back-out, and a named group, not the individual join account.

Service account: "Log on as a service"

Microsoft's SQL Server page says to assign "Log on as a service" to the service account on that computer, using Local Security Settings (Secpol.msc). It also says: "Check if the service account is assigned any Deny user rights." Its example is a service account assigned both Deny log on as a service (SeDenyServiceLogonRight) and Log on as a service (SeServiceLogonRight), where the Deny entry is revoked for the account.

Before you change it, write down every account and group currently listed under "Log on as a service" and under "Deny log on as a service" on that server. The policy console gives no export step on Microsoft's pages, so the written list is your saved copy.

Risk: the next steps change which accounts may start services on this server. Microsoft's policy page advises: "Minimize the number of accounts that are granted this user right." It also says that the Deny setting "supersedes" the Allow setting for an account subject to both. Removing a Deny entry makes that account able to run services; adding an Allow entry grants the right to every account you add. If a domain policy sets these lists, the local change is overwritten at the next Group Policy update.

In the elevated console on the affected server:

secpol.msc
  1. Expand Local Policies, then select User Rights Assignment.
  2. Open "Log on as a service" and add the service account if it is missing.
  3. Open "Deny log on as a service" and remove the service account only if it is listed there and the service should be allowed to run.

Microsoft's policy pages say a restart is not required and that a change "becomes effective the next time the owner of the account logs on". Microsoft's policy pages do not say when a running service picks a change up. Start the service again and read the System log for event 7041.

To undo it: open the same console, return to the same two entries, and set each list back to the accounts you wrote down.

secpol.msc

A domain policy overwrites the setting

Microsoft's page says Group Policy settings "will overwrite settings on the local device at the next Group Policy update". If gpresult /r shows an applied object that sets these rights, a local edit does not last, and the change would be made in that object.

Before you change it, write down the object's name and the accounts and groups it lists under "Log on as a service" and "Deny log on as a service".

Risk: the next steps edit a Group Policy object, so every computer in its scope takes the change at its next Group Policy update, not only this server. A wrong entry stops services from starting on all of them.

In Group Policy Management, edit that object and go to Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment, the location Microsoft's policy pages give. Change the "Log on as a service" and "Deny log on as a service" entries as in the steps above.

To undo it, edit the same object and set both entries back to the lists you wrote down.

Confirm the fix

  • Domain join: run the join again and read the new NetSetup.log. The 0x569 lines should be absent.
  • Service: start the service, then check the System log. Event 7041 should not be logged for the new start.
  • Run gpresult /r again and confirm the policy that sets the right is still listed as applied.

What to watch afterwards

  • The group you added. "domain joiners" should hold only the accounts that join computers.
  • The next Group Policy update on the server, which can undo a local edit.
  • Any other service on the same policy scope that uses a different account.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's domain join page names "Supported versions of Windows Server" without listing them. The security policy pages are written for Windows 10 and Windows 11, and one names Windows Server 2022, 2019 and 2016. The SQL Server page covers SQL Server services only, and the Hyper-V page gives no resolution of its own. For a domain join, Microsoft's page says the right is checked on the domain controller servicing the join.

Sources