Share via

Event ID 769 — Multicast Initialization

  • Article

Applies To: Windows Server 2008

When the WDSServer service is started, the multicast server initializes. During initialization, the multicast server reads the configuration settings and determines whether any multicast transmissions or namespaces are still valid (and restarts them if they are). The multicast server must initialize successfully before it can function correctly.

Event Details

Product: Windows Operating System
ID: 769
Source: WDSMC
Version: 6.0
Symbolic Name: EVT_WDSMCS_E_NSREG_CONTENT_PROVIDER_NOT_REG
Message: The namespace %1 using content provider %2 could not be registered as the content provider is not registered. The namespace has been removed from the namespace store.

Error Information: %3

Resolve

Reinstall the custom content provider and ensure that the registry permissions are correct

When the multicast server initializes, it reads the configuration settings and determines whether any multicast transmissions or namespaces are still valid (and restarts them if they are). If the multicast server discovers a ScheduledCast namespace that is registered by an unregistered content provider, it will delete it.

To resolve this issue, first reinstall the custom provider to create a registry key at the following location: HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Providers\. Next, do the following in the specified order:

  • Ensure that the registry data is correct.
  • Recreate the namespace.

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 correct registry data and confirm the registry settings: 

  1. Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER.)
  2. Ensure that the following registry key exists at HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Providers\<custom content provider>.
  3. Confirm that the ProviderDll subkey of type REG_EXPAND_SZ has a value that matches the location of the file (for example, %systemroot%\system32\wdscp.dll is for the Windows Deployment Services content provider).

If you want to transfer the failed content by using a multicast transmission, you will need to use the procedure in the following section to recreate the namespace.

Recreate the namespace

To create a transmission (for the Transport Server role service):

  1. Open the Command Prompt window.
  2. Do one of the following at the command prompt:
    • To create a Scheduled-Cast namespace, run WDSUTIL /New-Namespace [/Server:<server name>] /Namespace:<namespace name> /FriendlyName:<friendly name> [/Description:<description>] /ContentProvider:<name> /ConfigString:<config string> /NamespaceType:ScheduledCast [/Time:<YYYY/MM/DD:hh:mm>] [/Clients:<number of clients>]
    • To create an Auto-Cast namespace, run WDSUTIL /New-Namespace [/Server:<server>] /Namespace:<namespace name> /FriendlyName:<friendly name> [/Description:<description>] /ContentProvider:<name> /ConfigString:<config string> /NamespaceType:AutoCastFor more information, see the Transport Server chapter at PLACEHOLDER FWLINK.

Verify

To verify that the multicast server initialized successfully:

  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 the date and time.
  4. Find WDSMC event 512.

Multicast Initialization

Windows Deployment Services