Event ID 515 — WDSServer Provider Availability

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

red

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: 515
Source: WDSServer
Version: 6.1
Symbolic Name: E_WDSSERVER_PROV_PROVIDERDLL_KEY_MISSING
Message: An error occurred while trying to read a required registry key 'ProviderDll' for provider %1. This can happen if the provider was not properly registered with Windows Deployment Services.

Error Information: %2

Resolve

Replace the ProviderDll subkey

To resolve this issue, ensure that the registry data is correct.

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

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

To ensure that the registry data is corrupt:

  1. Open the Registry Editor (Click Start, type regedit in the Start Search box, and then press ENTER.)
  2. Ensure that the registry key for the provider that failed exists at the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\ProvidersNote: The failed provider is specified in the event log message. To find the message, search Event Viewer for WDSServer event 515.
  3. If you find the registry key at the location specified in step 2, make sure that the ProviderDll subkey exists and that it contains a path to the .dll file. Then make sure that the  dll file exists at that location. If it does, restart the server.
  4. If the provider key, the ProviderDll subkey, or the file is missing, do one of the following:
    • If the provider is one of the default providers (WDSPXE, BINLSVC, WDSIMGSRV, WDSMC, and WDSTFTP), reinstall Windows Deployment Services by using Server Manager (see the following procedure).
    • If the provider is a custom or non-Microsoft provider, reinstall it. If that does not fix the problem, contact the vendor for troubleshooting information.

To reinstall Windows Deployment Services:

  1. Open Server Manager.
  2. Under Roles Summary, click Remove Roles.
  3. Click Windows Deployment Services, and then follow the instructions in the wizard.
  4. After the role removal is completed, click Add Roles in Server Manager to reinstall Windows Deployment Services.

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.

Related Management Information

WDSServer Provider Availability

Windows Deployment Services

Community Additions

ADD
Show: