Event ID 519 — WDSServer Provider Availability

  • Article

Applies To: Windows Server 2008

The Windows Deployment Services server service (WDSServer) provides basic service functions to support its hosted subcomponents, known as providers (or plug-ins). The providers provide the true functionality associated with the service. There are five providers included with the default (Deployment Server) installation:

  • PXE server
  • PXE provider
  • Image server
  • Multicast server
  • TFTP server

Event Details

Product: Windows Operating System
ID: 519
Source: WDSServer
Version: 6.0
Symbolic Name: E_WDSSERVER_PROV_INIT_ENDPOINTS_NOT_CLOSED
Message: Provider %1 failed to initialize but still has %2 registered endpoints. Providers are required to close all endpoints and release all allocated resources if their initialization function fails.

Resolve

Fix other errors

Normal operation of the WDSServer service depends on various provider components. If one of these providers fails, the WDSServer service will also be affected. Note that you will need to resolve the root error before you can restart the service.

  • If this event was caused by a non-Microsoft provider, contact the vendor for troubleshooting information.
  • If you are using the default providers (WDSPXE, BINLSVC, WDSIMGSRV, WDSMC, and WDSTFTP), use the following procedure to find the root cause of this error.

Note: The failed provider is specified in the event log message. To find the message, search Event Viewer for WDSServer events 513, 514, and 519.

To find the root cause of the error:

  1. Open Event Viewer (Click Start, type Event Viewer in the Start Search box, and then press ENTER.)
  2. In the left pane, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
  3. Click the Date and Time column heading to sort the events based on date and time.
  4. Review the events that have a similar date and date as this event (WDSServer event 512).
  5. Click the related event, and then click Event Log Online Help at the bottom of the General tab.
  6. Follow the instructions to resolve the error (WDSServer event 512).
  7. After you have resolved the root error, restart the WDSServer service. (In the Command Prompt window, run net stop wdsserver and then run net start wdsserver.)

Any of the events in the following three lists may be the root cause of the error:

  • WDSPXE: 513, 768, 774, 770, 772, 776, 256, 257, 258, 259, 260, 261, 263, 265, 266, 268
  • BINLSVC: 512, 513, 515, 516, 517, 518, 1800, 1794, 1809, 1795, 1797, 1799, 1281, 1283, 1287, 1302, 1303, 1304, 1284, 1285, 1286, 1295, 1296, 1297, 1299, 1300
  • WDSIMGSRV: 258

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 providers are working correctly:

  1. Open the Command Prompt window (Click Start, point to All Programs, click Accessories, and then click Command Prompt.)
  2. At the command prompt, run net stop wdsserver and then run net start wdsserver.
  3. Open Event Viewer (Click Start, type Event Viewer in the Start Search box**,** and then press ENTER.)
  4. In the left pane, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
  5. Click the Date and Time column heading to sort the events based on date and time.
  6. Ensure that you receive WDSServer event 517 for each of your providers (look in the event log message for each event, and make sure that each provider initializes.) Note: There are five providers included with the default installation of Deployment Server: WDSPXE, BINLSVC, WDSIMGSRV, WDSMC, and WDSTFTP.

WDSServer Provider Availability

Windows Deployment Services