Answered by:
WDS Won't Start Automatically (0x54B)

Question
-
On my Windows Server 2008 R2 Domain Controller (which was upgraded from Windows 2008 Server), my WDS service will not start automatically, even if I delay its startup. It will however work on a manual start. Also, when the server boots up, it sits at applying computer settings for a long time. I find these errors in the event log:
Error 7/15/2010 3:22:52 AM WDSServer 513 WDSServer
An error occurred while trying to initialize provider WdsImgSrv from C:\Windows\system32\WdsImgSrv.dll. Windows Deployment Services server will be shutdown.
Error Information: 0x54B
and
Error 7/15/2010 3:22:53 AM WDSServer 257 WDSServer
An error occurred while trying to start the Windows Deployment Services server.
Error Information: 0x54B
Any suggestions? I found one thread about this, http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/70743031-ba83-4758-9b3f-35574886b1b1?prof=required, but it is old and the issue was never resolved.
Thanks,
-JeffFriday, July 30, 2010 3:19 PM
Answers
-
Hi Jeff,
Please refer to the following articles:
http://technet.microsoft.com/en-us/library/cc726736(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc726644(WS.10).aspx
Tim Quan
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Marked as answer by Tim Quan Friday, August 6, 2010 1:56 AM
Tuesday, August 3, 2010 3:54 AM
All replies
-
Hi,Is the WDS server configured to use the IP addresses for the DC(s) thathost the DNS role as its own DNS servers that it contacts?# for hex 0x54b / decimal 1355 :ERROR_NO_SUCH_DOMAIN winerror.h# The specified domain either does not exist or could not be# contacted.# 1 matches found for "54b"On 7/30/2010 9:19 AM, jeff.field wrote:> On my Windows Server 2008 R2 Domain Controller (which was upgraded from> Windows 2008 Server), my WDS service will not start automatically, even> if I delay its startup. It will however work on a manual start. Also,> when the server boots up, it sits at applying computer settings for a> long time. I find these errors in the event log:>> Error 7/15/2010 3:22:52 AM WDSServer 513 WDSServer>> An error occurred while trying to initialize provider WdsImgSrv from> C:\Windows\system32\WdsImgSrv.dll. Windows Deployment Services server> will be shutdown.>> Error Information: 0x54B>> and>> Error 7/15/2010 3:22:53 AM WDSServer 257 WDSServer>> An error occurred while trying to start the Windows Deployment Services> server.>> Error Information: 0x54B>> Any suggestions? I found one thread about this,> but it is old and the issue was never resolved.>> Thanks,> -Jeff>
-- Mike BurrMonday, August 2, 2010 11:02 PM -
Hi Jeff,
Please refer to the following articles:
http://technet.microsoft.com/en-us/library/cc726736(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc726644(WS.10).aspx
Tim Quan
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Marked as answer by Tim Quan Friday, August 6, 2010 1:56 AM
Tuesday, August 3, 2010 3:54 AM -
Sorry for the late reply, but yes, it is - it is the DC with the DNS roll and it points to itself as primary DNS with secondary being a DC in another building.Monday, October 4, 2010 1:26 PM