Windows Server TechCenter >
Windows Server Forums
>
Setup Deployment
>
wdsserver service fails to start automatically - manual start works
wdsserver service fails to start automatically - manual start works
- wds running on a server 2008 domain controller. WDSServer service fails to start at boot but then if you manually start it everything seems fine. Below are event log entries from both *before* I applied sp2 to the server, and *after* I applied sp2 to the server. Still fails to start automatically but the error log entries changed post sp2.
PRE - SP2 events logged -----------------------------------------
From the application log:
Event 513, Source: wdsserver
An error occurred while trying to initialize provider BINLSVC from C:\Windows\system32\binlsvc.dll. Windows Deployment Services server will be shutdown.
Error Information: 0x200F
Event 257, Source: wdsserver
An error occurred while trying to start the Windows Deployment Services server.
Error Information: 0x200F
and from the system log:
Event 7024, Source: service control manager event log provider
The Windows Deployment Services Server service terminated with service-specific error 8207 (0x200F).
POST SP2 events logged ------------------------------------------------
From the application log:
Event 513, Source: 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
Event 257, Source: wdsserver
An error occurred while trying to start the Windows Deployment Services server.
Error Information: 0x54B
From the system log:
Event 7024, Source: service control manager event log provider
The Windows Deployment Services Server service terminated with service-specific error 1355 (0x54B).
1. is my server going to blow up?
2. how do I resolve this? I have 2 wds servers running in the same domain (2 different offices/locations). Both are exactly the same config as far as wds goes. Both are domain controllers and dns servers for the only domain (which is a domain used only for deploying servers - the servers being deployed don't actually join this domain). Only one of these servers is having this problem... the other one starts the service up fine at boot. The one with the problem was the first DC in the domain.
All Replies
Hi
I suggest referring to the following articles to troubleshoot the issue:
Event ID 513 — Configuration Settings Updates
http://technet.microsoft.com/en-us/library/cc726736(WS.10).aspx
Event ID 257 — PXE Provider Support
http://technet.microsoft.com/en-us/library/cc726644(WS.10).aspx
Event ID 7024 — Service Stop Operations
http://technet.microsoft.com/en-us/library/cc756369(WS.10).aspx
Hope it helps.
Tim Quan - MSFT
- hi, thanks for the reply. The info in those articles all check out... my problem is not that the service won't start at all, which is what the info in those article seems to be addressing more, it just fails to start automatically when the server boots... but then after logging in I can manually start the service without error?
I have seen elseware another fix for when the service won't start which is to temporarily run the service as a domain admin, restart so the service control points can be created, then change the service back to run as localsystem. But again, I believe that was for the case of the service failing to start altogether, and since I can succefully start the service manually, I was not sure if that fix would apply to me, and don't want to go introducing more problems.
anyone have any ideas? I may just try that other fix (run as domain admin then change back) - Try to set the service Startup type to Automatic (Delayed Start).
- Marked As Answer byTim Quan - MSFTMSFT, ModeratorFriday, September 25, 2009 1:28 AM
- Unmarked As Answer byc0pe Monday, September 28, 2009 5:29 PM
- thanks for the input Peter however I had already tried that with no luck. I think there is something wrong with either my AD or DNS. I think AD is unavailable for some time during and after boot, so wds cannot retrieve it's config info... then several minutes later when AD services are all functioning I can manually start the WDS service without a problem. AS of now I don't know the cause or how to fix.
I did try to config the service to run as domain admin so that the service point records get created as stated elseware but that did not help, as I don't think thats my problem. - I see. I had similar problems in my virtual environment. I linked it with slow performance of virtual machines, but it could be something completely different.
I did the following:
Launch WDS console
Choose Properties on WDS server
Choose Advanced tab
Choose Let WDS use only specific servers radio button and set up preffered DC and GC.
With this settings my environment started to work.
Regards,
Peter - I am having much the same problem. I'm leaning toward AD being the issue and no matter a Delayed start I am still not getting the service to automatically start. As c0pe I can manually start with no problem. However this defeats the purpose of automatically having services start.
- Hi Michael, I have not resolved this issue on my server... since it is still working and servicing clients I have just had other priorities to get done.. but, I also think this is AD related and one of these days I hope to get it straightened out. I'll be keeping an eye on this to see if anyone else comes up with something... and when I do get back to it, I'll post any updates here.
