| Event Id | 1007 |
| Source | Microsoft-Windows-IIS-W3SVC |
| Description | The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The necessary network binding may already be in use. The site has been disabled. The data field contains the error number. |
| Event Information | According to Microsoft : Cause : This event is logged when the world wide web publishing service did not register the url. Resolution : Remove a duplicate binding Web sites that have duplicate URL bindings will cause one of the Web sites to be disabled. Make sure that you do not try to register duplicate application URLs in the ApplicationHost.config or Web.config files. To resolve the duplication, determine which sites are using the same bindings. Then, modify the bindings as needed, and restart the site. A. Determine which sites are using the same bindingsTo determine which sites are using the same bindings: 1.Click Start, click Control Panel, and then click Administrative Tools. 2.Right-click Internet Information Services (IIS) Manager and select Run as administrator. 3.In the IIS Manager Connections pane, expand the computer name. 4.Left-click the Sites folder. A list of the Web sites on the server appears on the right in Features View. The binding for each site is listed in the Binding column. 5.Review the list of bindings and look for sites that have the same binding properties set. For example, look for two sites that both have a binding of *:80 (http). B. Remove the duplicate binding To remove the duplicate binding: 1.In IIS Manager, in the Connections pane, select the Web site that you have to configure. 2.In the Actions pane, click Bindings... 3.To modify an existing binding, select the binding and click Edit. 4.To add a new binding, click Add... 5.After you have set the unique bindings for the site, click OK, then click Close. C. Restart the Web site To restart the Web site: 1.In IIS Manager, in the Connections pane, select the Web site that you have to start. 2.In the Actions pane, click Stop to stop the site. 3.In the Actions pane, click Start to start the site. Verify : To verify that a Web site is started, you can use either IIS Manager or the appcmd command line utility. To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority. To verify that the Web site is started by using the appcmd command line utility: 1.Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. 2.Change the directory to %SystemDrive%\Windows\System32\inetsrv. 3.Run the following command: appcmd.exe list site -site.name:"Site Name". If the Web site is started, the output will resemble the following: SITE "Default Web Site" (id:1,bindings:http/*:80:,state:Started) To verify that the Web site is started by using IIS Manager: 1.Click Start, click Control Panel, and then click Administrative Tools. 2.Right-click Internet Information Services (IIS) Manager and select Run as administrator. 3.In the Connections pane, expand the computer name. 4.In the Connections pane, click the Sites node. 5.In Features View, look for the Web site name. The Web site status will be indicated under the Status column. If the Web site is started and is using the HTTP protocol, Started(http) will appear. |
| Reference Links | Event ID 1007 from Source Microsoft-Windows-IIS-W3SVC |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.