Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 770 Source: BINLSVC
An error occurred while updating the Auto Add Policy settings. The Windows Deployment Services server will not process incoming client requests.
Error Information: 0x3A
|English: Request a translation of the event description in plain English.|
The ME960489 article provides a workaround and a hotfix. Apparently, the Windows Deployment Services (WDS) server in Windows Server 2008 stops working after the authenticating domain controller becomes unavailable.
T726520 suggests that this might be related to a permissions issue and is providing a list of things to check:
- Ensure that the registry data and permissions are correct
- Ensure that the WDSServer service has permissions to the RemoteInstall folder
- Ensure that the WDServer service has access to the registry
- Ensure that the configuration data in the registry is correct
If all these look fine, the article provides information on how to recreate the Auto-Add Devices database.
Error 0x3A is Error code 58 in decimal system.
In my case, this error followed event ids 266 from WDSIMGSRV and 513 from BINLSVC. Happened while upgrading a DC (it was offline) but other DCs in the same site were available.
|Private comment: Subscribers only. See example of private comment|
|Links: T726520, Event id 513 from BINLSVC, ME960489|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated