| Event Id | 771 |
| Source | WDSMC |
| Description | The namespace %1 using content provider %2 could not be registered due to an unknown error. Error Information: %3 |
| Event Information | According to Microsoft : Cause : This event is logged when the namespace using content provider could not be registered as namespace by that name already exists. Resolution : Recreate the namespace 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 finds invalid namespaces (for example, those from a time that has past or with a name is already in use) it will delete them. If you want to transfer the failed content using multicast, you will need to recreate the namespace. To create a transmission (for the Deployment Server role service): 1)Open theCommand Prompt window. 2. Do one of the following at the command prompt: a)To create an Auto-Cast transmission, run WDSUTIL /New-MulticastTransmission /Image: b)To create a Scheduled-Cast transmission, run WDSUTIL /New-MulticastTransmission /Image: To create a transmission (for the Transport Server role service): 1.Open theCommand Prompt window. 2.Do one of the following at the command prompt: a) To create a Scheduled-Cast namespace, run WDSUTIL /New-Namespace [/Server: b)To create an Auto-Cast namespace, run WDSUTIL /New-Namespace [/Server: Verify : To verify that the multicast server initialized successfully: 1)Open Event Viewer. (ClickStart, typeEvent Viewer in theStart Search box, and then press ENTER.) 2.In the left pane, expandCustom Views, expandServer 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. |
| Reference Links | Event ID 771 from Source WDSMC |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.