Event ID 592 — Multicast Content Provider Support
Applies To: Windows Server 2008
The multicast server uses a content provider to transmit the data from the server to the client. The Windows Deployment Services content provider can transfer any file over a multicast transmission; however, you can create or use a custom content provider if you want additional functionality. For example, you could create a content provider that transfers a .zip archive, a .vhd image, or a database and then extracts data out of it. The providers must be functioning properly to deploy content using multicast transmissions.
|Product:||Windows Operating System|
|Message:||An error occurred while trying to load the module %1 for Content Provider %2.
Error Information: %3
Ensure that the ProviderDLL registry key points to the correct file
To resolve this issue, do the following in the specified order:
- Ensure that the registry data is correct.
- Reinstall Windows Deployment Services.
To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.
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 ensure that the registry data is correct:
- Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER.)
- Ensure that the registry key for the provider that failed exists in the following location:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\<content provider>. Note: The failed content provider is specified in the event log message. To find this message, open Event Viewer, expand Custom Views, expand Server Roles, click Windows Deployment Services, and then find WDSMC event 592.
- If the registry key exists in the specified location, do the following:
- Ensure that the ProviderDll subkey exists and contains a path to the .dll file.
- Ensure that the .dll file exists at that same location. For example, the ProviderDll key for the Windows Deployment Services content provider (WDSCP) is %systemroot%\system32\wdscp.dll.
- Ensure that the content provider has the necessary permissions to read the registry keys at the following location: HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Providers\<content provider>. To do this, right-click the WDSServer node, click Permissions, click SYSTEM, and then make sure that Full Control is selected.
- If all of this information is correct, restart the WDSServer service (in the Command Prompt window,** run **net stop wdsserver and then run net start wdsserver).
- If the provider key, the ProviderDll subkey, or the file is missing, do one of the following:
- If the provider is the Windows Deployment Services content provider (WDSMC), you will need to reinstall Windows Deployment Services by using Server Manager (see the procedure in the following section).
- 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.
Reinstall Windows Deployment Services
To reinstall Windows Deployment Services:
- Open Server Manager (Click Start, point to Administrative Tools, and then click Server Manager.)
- Under Roles Summary, click Remove Roles.
- Click Windows Deployment Services, and then follow the instructions in the wizard.
- After the role removal is completed, click Add Roles in Server Manager to reinstall Windows Deployment Services.
For more information about installing Windows Deployment Services, see http://go.microsoft.com/fwlink/?LinkId=89222.
To verify that all of your content providers are running properly:
- Open the Command Prompt window.
- At the command prompt, type sc control wdsserver 130.
- Confirm that the output includes entries for all of your content providers. Note that the default content provider is WDScp.dll.