WDS Service won't start
- Everytime I try and start the WDS service I get an error code of 0x54B. Any suggestions?
Answers
The error 0x54b indicates that there was an issue in either contacting or connecting to Active Directory. Depending upon what build you are running, you may or may not have debug tracing turned on. First, check that it is indeed enabled. This is done via the 'EnableFileTracing' key at HKLM\Software\Microsoft\Tracing\WDSServer and \WDSMGMT. Set the key to '1'. Then, attempt to start the server service again. You should see debug logs in %windir%\tracing for each of the two components. They may give you more of an indication if it is a contacting problem or a connecting problem.
Some of the most common causes of this issue -
1. You specified values for the Domain Controller and / or Global Catalog server that the WDS Server should use (properties of the server in the WDS MMC -> Advanced tab) and the values are incorrect.
2. DNS configuration issues. Run 'netdiag.exe /v' (found in the Windows Server 2003 Resource Kit) and analyze the output for DNS problems. The most common configuration issue is pointing to external DNS servers from your (internally located) server - this is bad.
3. Kerberos issues. Since your server is a member of a domain, WDS expects to be able to use Kerberos when authenticating with and using a domain controller. The netdiag output can help you here as well as the system log. Ensure that the time on your server is in-synch with the domain controller.
Thanks -
--Scott
All Replies
The error 0x54b indicates that there was an issue in either contacting or connecting to Active Directory. Depending upon what build you are running, you may or may not have debug tracing turned on. First, check that it is indeed enabled. This is done via the 'EnableFileTracing' key at HKLM\Software\Microsoft\Tracing\WDSServer and \WDSMGMT. Set the key to '1'. Then, attempt to start the server service again. You should see debug logs in %windir%\tracing for each of the two components. They may give you more of an indication if it is a contacting problem or a connecting problem.
Some of the most common causes of this issue -
1. You specified values for the Domain Controller and / or Global Catalog server that the WDS Server should use (properties of the server in the WDS MMC -> Advanced tab) and the values are incorrect.
2. DNS configuration issues. Run 'netdiag.exe /v' (found in the Windows Server 2003 Resource Kit) and analyze the output for DNS problems. The most common configuration issue is pointing to external DNS servers from your (internally located) server - this is bad.
3. Kerberos issues. Since your server is a member of a domain, WDS expects to be able to use Kerberos when authenticating with and using a domain controller. The netdiag output can help you here as well as the system log. Ensure that the time on your server is in-synch with the domain controller.
Thanks -
--Scott
