Sunday, July 29, 2018
WDS Service Crashes after Boot Image Update and cant start again
WDS Service Crashes after Boot Image Update and cant start again
I updated a boot image with new controller and network card drivers and found all WDS services has stopped on PXE points.
One of the events were popular Event ID 258 � Image Server Configuration
The description for Event ID 258 from source WDSIMGSRV cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
0xC1030104
Another event was 512 with same error information
An error occurred while trying to initialize provider WdsImgSrv from C:Windowssystem32WdsImgSrv.dll. Since this provider is not marked as critical, Windows Deployment Services server will continue.
Error Information: 0xC1030104
and 1000
Faulting application name: svchost.exe_WDSServer, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: wimgapi.dll, version: 6.1.7600.16385, time stamp: 0x4a5be09a
Exception code: 0xc0000005
Fault offset: 0x0000000000032a8e
Faulting process id: 0x9f0
Faulting application start time: 0x01ce820a679bb189
Faulting application path: C:Windowssystem32svchost.exe
Faulting module path: C:Windowssystem32wimgapi.dll
Report Id: aa4171a9-edfd-11e2-bd63-0050569b0082
and some other APPCRASH events about WDS.
So most of the resources recommends checking permissions, re-initialize the WDS or reinstall.
Your case might not be same as me but I recommend you to try something else before step in to recommended time consuming tasks.
Refresh!. Yes try to refresh your image first, Although SCCM says the boot image has updated successfully on PXE points try to refresh once. It worked for me, you can also copy image from refreshed source to test it. So I refreshed my PXE points and voila ! All WDS service problems have disappeared.
Currently I am not sure about the source of the problem but my feelings says it could be the binary difference replication.
