WDS service fails. Event IDS 257,258 and 513

Hi,

I have added wds role in sccm 2012 site server.  WDS service fails and generates event ids 257,258 and 513.  

Kindly help me to fix wds service.  

Regards,
karekal
mkarekalAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dash AmrSenior Specialist(PM)Commented:
Windows Deployment Services depends and works directly with Active Directory and DHCP, meaning that if any of those two servers are significantly modified, then probably you will not be able to start the WDS service and get the events ID:

Event Viewer from WDS Server

Event 257: An error occurred trying to start the Windows Deployment Services server.

Event 258: An error occurred trying to start the Windows Deployment Services image server.

Event 266: An error occurred while to refreshing settings.

Event 513: An error occurred trying to initialize provider WDSImgSrv from C:\Windows\system32\WdsImgSrv.dll. Windows Deployment Services server will be shutdown.

Please Download the Document attached - Hope It will give a good direction on how to Fix your Problem.

Cheers
Dash
Windows-Deployment-Services-depe.pdf
1
violageekCommented:
I would start by looking that PXE and stuff are configured properly. After that go in to services and for WDS service logon account use the Domain Admin account to start the service. Try starting the service again. This should create an SCP in AD for wds and you can change it back to the local system account once its started.

Hope this helps!
0
mkarekalAuthor Commented:
Hello All,  Am able to fix this issue.  Did below steps,

wdsutil /uninitialize-server
wdsutil /initialize-server /reminst:<path to remoteinstall dir>.

This worked fine.

I have received previllage related errors when i executed from c:.

Should be executed from c:\windows\system32.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mkarekalAuthor Commented:
Initialize and uninitialize the wds service will revert the changes to original state.  Which will fix the issue most of the times.  I have received same issue on multiple hosts and fixed by following the above mentioned steps.  This solution is worth to check.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.