Troubleshooting Guide: Error 1357 – Domain Limit Exceeded on Server
Why This Error Happens
Error 1357 occurs when a server, typically running as a Domain Controller, attempts to host more domains than the Security Accounts Manager (SAM) database or the specific Windows Server edition license allows. This is often triggered by improper Active Directory Domain Services (AD DS) configuration or by attempting to promote a server in an environment that has already reached its architectural domain limit. In rare cases, this can also result from a corrupted or misconfigured registry entry related to the Netlogon service that manages domain trust relationships.
Step-by-Step Resolution Guide
Step 1: Verify Current Domain Configuration
- Open Windows Terminal as an Administrator.
- Run the command
netdom query fsmoto check the current Flexible Single Master Operation roles and domain structure. - Check the Windows Edition currently installed via Settings > System > About, as Standard editions have stricter domain limits than Datacenter editions.
Step 2: Check Active Directory Domains and Trusts
- Press
Win + R, typedomain.msc, and press Enter to open the Active Directory Domains and Trusts console. - Right-click on the root node and select Properties to view a list of currently registered trusts and child domains.
- Identify and remove any orphaned or duplicate domain entries that may be inflating the count against the license limit.
Step 3: Review the Windows Registry for Netlogon Parameters
- Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parametersusing the Registry Editor (regedit). - Look for a DWORD value that might be capping the maximum number of domains; ensure this value is not manually set below the required threshold.
- Warning: Back up the registry before making any changes here, as incorrect edits can destabilize the Netlogon service.
Step 4: Restart Core Directory Services
- Open the Services app (
services.msc). - Locate Active Directory Domain Services and Netlogon, right-click, and select Restart.
- This forces the server to re-read the domain configuration and license limits from the SAM database upon reboot.
Alternative or Verification Steps
- Verification: After restarting the services, run
dcdiag /test:servicesin an elevated command prompt to confirm that all domain controller services are running without generating Error 1357 again. - Alternative: If the error persists, consider upgrading the server’s license tier (e.g., moving from Standard to Datacenter) if you have a legitimate business need to host domains exceeding the current SKU’s built-in limitation.