Event ID 772 — Auto-Add Devices Database

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

red

The Auto-Add Devices database enables you to add computer accounts to Active Directory Domain Services automatically. You will find this database in the \RemoteInstall\Mgmt folder (by default, the RemoteInstall folder is located on drive C). The database is created by the Pre-Boot Execution Environment (PXE) provider the first time you enable the Auto-Add functionality (using either the MMC snap-in or the /AutoAddPolicy command-line option). All computers in the pending queue are represented as an entry in the database on the Windows Deployment Services server.

Event Details

Product: Windows Operating System
ID: 772
Source: BINLSVC
Version: 6.1
Symbolic Name: E_BINL_AUTOADD_QUERY_BY_REQID_FAILED
Message: An error occurred while trying to query the Auto Add database using Request Id %1.

Error Information: %2

Resolve

Free up memory or recreate the database

If the server is low on memory or the Auto-Add Devices database is corrupt, a query to the Auto-Add device database will fail. To resolve this issue, first use Task Manager to ensure that the server is not low on memory. One way to increase the amount of available memory is to determine whether there are any programs or processes running on the server that can be closed. Use Task Manager to determine which processes are using the most memory, and to end those processes.

To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

Free up memory

To free up memory on the server:

  1. On the Windows Deployment Services server, right-click an empty area of the taskbar, and then click Task Manager.
  2. Click the Processes tab.
  3. Make sure that the User Name and Memory (Private Working Set) columns appear. If they do not appear, click Select Columns on the View menu, select the User Name and Memory (Private Working Set) check boxes, and then click OK.
  4. At the bottom of the tab, select the Show processes from all users check box.
  5. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  6. To sort the processes by memory usage, click the Memory (Private Working Set) column heading.
  7. Determine whether you can end any of the memory-intensive processes.
  8. To end a process, click the process name, and then click End Process.
  9. When prompted, click End Process again to confirm that you want to end the process.

If the server is not low on memory and you continue to encounter this error, the database may be corrupt. To resolve this issue, you will need to recreate the database by using the procedure in the following section.

Recreate the database

To recreate the database:

  1. Delete the contents of the RemoteInstall\Mgmt folder. By default, the RemoteInstall folder is located on drive C.
  2. Open the Command Prompt window.
  3. At the command prompt, run net stop wdsserver.
  4. At the command prompt, run net start wdsserver.

Verify

To perform this procedure, you must either be a member of the local Domain Admins group or have been delegated the appropriate authority.

To verify that the Auto-Add policy is active:

  1. Restart the WDSServer service. To do this, open the Command Prompt window, run net stop wdsserver, and then run net start wdsserver.
  2. Open Event Viewer. (Click Start, type Event Viewer in the Start Search box, and then press ENTER).
  3. In the left pane, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
  4. Click the Date and Time column heading to sort the events based on date and time.
  5. Look for BINLSVC event 769. The presence of this event indicates that the Auto-Add settings were applied correctly.

Related Management Information

Auto-Add Devices Database

Windows Deployment Services

Community Additions

ADD
Show: