| Event Id | 601 |
| Source | WDSMC |
| Description | The Content Provider %1 returned an error while trying to open content %2. Error Information: %3 |
| Event Information | According to Microsoft : Cause : This event is logged when the content provider returned an error while trying to open a new instance. Resolution : Ensure that the content provider configuration settings are correct The content provider must be able to locate and open the specified content. If you are using a custom or non-Microsoft content provider, contact the vendor for troubleshooting information. Otherwise, to ensure that the content provider configuration settings are correct, do the following in the specified order: 1)Ensure that Res.rwm exists. 2)Ensure that the required registry permissions are set. 3)Ensure that there is enough memory. Ensure that Res.rwm exists Ensure that the Res.rwm exists for the image you want to transfer over a multicast transmission. The Res.rwm file should be located at RemoteInstall\Images\ If the Res.rwm file exists, use the procedure in the following section to ensure that the necessary registry permissions on the server are set. Ensure that the required registry permissions are set 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 correct registry permissions are set: 1.Open Registry Editor. (ClickStart, typeregedit in theStart Search box, and then press ENTER.) 2.Make sure that the failed content provider has correct permissions to read the registry keys at the following location:HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Providers\ If this does not fix the issue, use the procedure in the following section to ensure that there is enough memory on the server. Ensure that there is enough memory To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority. To free up memory on the server: 1.On the Windows Deployment Services server, right-click an empty area of the taskbar, and then clickTask Manager. 2.Click the Processes tab. 3.Make sure that theUser Name and Memory (Private Working Set) columns appear. If they do not appear, click Select Columns on theView menu, select theUser Name andMemory (Private Working Set) check boxes, and then clickOK. 4.At the bottom of the tab, select theShow processes from all users check box. 5.If theUser Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. 6.To sort the processes by memory usage, click the Memory (Private Working Set) column heading. 7.Determine whether it is safe to end any of the memory-intensive processes. 8.To end a process, click the process name, and then clickEnd Process. 9. When prompted, clickEnd Process again to confirm that you want to end the process. Verify : To verify that all of your content providers are running properly: 1.Open the Command Prompt window. 2.At the command prompt, type sc control wdsserver 130. 3.Confirm that the output includes entries for all of your content providers. Note that the default content provider is WDScp.dll. |
| Reference Links | Event ID 601 from Source WDSMC |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.