How to fix “No principal name registered. [RPC_S_NO_PRINC_NAME (0x71E)]” – Error Code 1822


Error Code 1822

Error code Error Code 1822 is a common Windows issue that typically arises from “No principal name registered. [RPC_S_NO_PRINC_NAME (0x71E)]”.


In this article, we will explore the issue denoted by Error Code 1822 in Windows: “No principal name registered. [RPC_S_NO_PRINC_NAME (0x71E)]”. This error can disrupt system performance, and understanding its causes and resolutions is crucial.

Identifying the Problem

Error Code 1822 typically arises when:
– A networked service requires a Security Principal Name (SPN) to operate, but no SPN has been registered.
– An SPN registration has been modified or deleted.
– A service account password is incorrect.

Common Fixes

1. Register the Service Principal Name (SPN)

  • Open PowerShell as an administrator.
  • Run the command: Setspn -s <SPN> <ServiceAccount>

    Example: Setspn -s HTTP/<MachineName> <ServiceAccount>

2. Verify Service Account Credentials

  • Ensure the service account has the correct password.
  • Restart the affected service to apply the changes.

3. Reset the Computer Account Password

  • Join the computer to the domain.
  • Open Command Prompt as an administrator.
  • Run the command: netdom resetpwd /s:<DomainName> /ud:<UserName> /pd:*

    Example: netdom resetpwd / /ud:Administrator /pd:Password123

Advanced Troubleshooting

1. Clear LDAP Cache

  • Open Registry Editor (regedit).
  • Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LdapSvc
  • Delete the “Configuration Cache” value in the right pane.

2. Check SPN Registration

  • Use the command: setspn -l <ServiceAccount> to list all SPNs registered for the service account.
  • Ensure the SPN for the affected service is present.

3. Enable Netlogon Logging

  • Open Registry Editor.
  • Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
  • Create or modify the DWORD value “LogLevel” to 2.
  • Restart the Netlogon service to apply the changes.


Error Code 1822 can be effectively resolved by following the outlined fixes. By understanding the root cause, applying common solutions, and implementing advanced troubleshooting techniques when necessary, you can restore your system’s optimal performance. To prevent future occurrences, ensure proper SPN registrations and maintain service account security.