Share via

Event ID 265 — PXE Provider Support

  • Article

Applies To: Windows Server 2008

The Pre-Boot Execution Environment (PXE) server is used by Windows Deployment Services to provide network boot programs to client computers. The PXE server receives and responds to PXE requests, and the providers contain the business logic that determines how and when the requests are answered. The PXE provider included with Windows Deployment Services is named Binlsvc.dll.

Event Details

Product: Windows Operating System
ID: 265
Source: WDSPXE
Version: 6.0
Symbolic Name: E_WDSPXE_CRITICAL_PROV_INIT_FAILED
Message: An error occurred while trying to initialize provider %1. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown.

Error Information: %2

Resolve

Fix other errors

Normal operation of the WDSServer service depends on various provider components. If one of the providers fails, WDSServer will also be affected. You will need to resolve the root cause of the error before the service will function correctly. 

To resolve this issue, first ensure the following:

  • Your server is running Windows Server 2008 in a domain that contains working DHCP and DNS servers.
  • You have an NTFS file system in your operating environment.

If the server meets these requirements, do one of the following:

  • 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.

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 on the General tab.
  6. Follow the instructions to resolve the error.
  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.)

Specifically, any of the following BINLSVC events may be the root cause of this error: 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, or 1300.

Verify

To verify that the providers are working correctly:

  1. Open the Command Prompt window.
  2. At the command prompt, run wdsutil /get-server /show:config, and ensure that the expected providers are listed in the output.
  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 time and date.
  6. Check for WDSPXE events 262 and 267, which verify that a provider was loaded (or unloaded) and initialized successfully.
  7. Ensure that you receive events 262 and 267 for each provider.

PXE Provider Support

Windows Deployment Services