Article ID: 917485 - View products that this article applies to.
After you create or update a package that targets a newly-enabled distribution point on a remote server that uses the Background Intelligent Transfer Service (BITS), you may receive the following error message. This error message may be logged in the Microsoft Configuration Manager\Logs\distmgr.log on the site server.
ERROR CreateVirtualDirectory: Failed to bind to virtual directory root IIS://ServerName/W3svc/1/ROOT. error = Access is denied. ERROR CheckDPforDrizzle: Could not find the desired DP ["Display=\\ORL40513\"]MSWNET:["SMS_SITE=SiteCode"]\\ORL40513\ in the SCF Cannot set the current Drizzle Role status for the DP. Performing error cleanup prior to returning.
This problem occurs because the virtual directory for SMSPKGVolume$ was not created or cannot be accessed on the distribution point in Internet Information Service (IIS) Manager. This behavior can occur when certain conditions are true. These conditions include, but are not limited to, the following examples:
Follow the steps that apply to the problem that you are experiencing based on the conditions from the "Cause" section.
Important After you resolve the problem, you must remove the distribution point and then install it again to create the virtual directory.
Required services are not started on the remote distribution pointThe following services must be running on the distribution point server for the distribution point installation to complete successfully. You must manually start these services if they are not running.
(https://support.microsoft.com/kb/909444/ )You may experience various problems after you install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC
Internet Information Services (IIS) is not installed on the remote distribution pointIIS must be installed on any remote server that hosts a distribution point. The following list shows the required IIS components:
Note You must stop and then start the SMS Executive service on the distribution point if the distribution point server is also a site server.
Incorrect IIS file and registry permissions on the remote distribution pointIn Microsoft Windows 2000, the IWAM_computername user account must have Read permissions to the
In Windows Server 2003, the IIS_WPG group must have Read permissions to the
For more information about IIS permissions, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/271071/ )How to set required NTFS permissions and user rights for an IIS 5.0 Web server
812614To troubleshoot IIS permissions problems, you can use the Regmon and the Filemon third-party products from Sysinternals.
(https://support.microsoft.com/kb/812614/ )Default permissions and user rights for IIS 6.0
Run the Regmon utility and the Filemon utility when you install the distribution point. Then, search for ACCDENIED in the Regmon utility and FAILURE in the Filemon utility for the Dllhost.exe process.
For more information about the Regmon utility and the Filemon utility, and to download the utilities, see the following Microsoft Web site:
http://technet.microsoft.com/en-us/sysinternals/default.aspxMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
There are various DNS problemsTo resolve problems that deal with DNS, take the following measures:
The Windows Server 2003 Security Configuration Wizard (SCW) has been run on the remote distribution pointWhen you run the Windows Server 2003 SCW on a BITS-enabled distribution point, you must select Remote administration for IIS and related components on the Installed Options page of the SCW. If you do not enable remote administration for IIS and related components, the Windows Server 2003 SCW prevents the Configuration Manager 2007 Distribution Manager from creating virtual directories on the BITS-enabled distribution point.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Article ID: 917485 - Last Review: September 11, 2011 - Revision: 8.0