Symptoms
Task for creating virtual web server fails with the following error:
Task ID 2434048
Queue name domain_service7166
Task name Create virtual web server 4791 (domain_id=8079, hd_id=103072) on host 'WSH.provider.tld' (host_id=36).
Task description Create virtual web server 4791 (domain_id=8079, hd_id=103072) on host 'WSH.provider.tld' (host_id=36).
Belongs to groups subscription1000001_domain8079_11505413581939427, subscription1000001_domain8079_13188842691939431
Subscription ID 1000001
Queue status Failed
Start not earlier than Dec-02-2014 15:51
Method name taskCreateWebSite on OBJREF:iis:0:getDomainService:7166
Last execution output
Destination host 'WSH.provider.tld' (#36), IP '192.168.123.123' : Provisioning request failed. Cannot create a file when that file already exists. [<response><errorContext description="Failed trying to start the currently stopped server IIS://WSH.provider.tld/W3SVC/4791 ServerState 0x800700b7: Cannot create a file when that file already exists." code="0x800700b7" executeSeqNo="131"><errorSource namespace="IIS Provider" procedure="SetProperties"/></errorContext></response>]
The following error is shown in System Log of Event Viewer on the target host:
Description:
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix http://testsite.tld:80:192.168.123.123/ for site 4791. The necessary network binding may already be in use. The site has been disabled. The data field contains the error number.
Cause
Same binding already exists on some other site in IIS.
Resolution
- Open applicationHost.config file located in
C:\Windows\System32\inetsrv\config
(alternatively you can use theC:\Windows\System32\inetsrv\MetaBase.xml
file) - Search it for the record like
192.168.123.123:80:testsite.tld
or192.168.123.123:80:www.testsite.tld
- In the found section note the site name, it should be something like
webspace_00100001 - domain (1234)
- If this site is needed, then cancel the failed task and create site with another name instead of testsite.tld. If site is not needed, remove it from IIS Manager (or remove conflicting binding from it) and restart the task. It should be completed successfully.