Technical FAQs

Ask a Question

Default Website will not start in Microsoft Internet Information Services (IIS) preventing ION Enterprise Webreach from working.

Goals and Symptoms

The default website is stopped which prevents ION Enterprise Webreach or another web client from working. When the default website is started it gives the error message "The process cannot access the file because it is being used by another process." The Windows System Event Log will give these 2 errors each time the default website attempts to start:
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1004
Date: 07/22/2008
Time: 4:18:50 PM
User: N/A
Computer: IONSRVR
Description:
The description for Event ID ( 1004 ) in Source ( W3SVC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: http://*:80/, 1.

Event Type: Error
Event Source: HTTP
Event Category: None
Event ID: 15005
Date: 07/22/2008
Time: 4:18:50 PM
User: N/A
Computer: IONSRVR
Description:
Unable to bind to the underlying transport for 0.0.0.0:80. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Changing the port from 80 to something else such as 8080 in IIS allows the default website to start, however this is not helpful for getting Webreach to work. The TCP Port field can be found by right clicking on default website and clicking on properties. The TCP Port field will be listed on the Web Site tab.

Causes and Fixes

Normally the default website will not start because there is another program on the same server that is preventing it from working. The Programmable Logic Controller Program from General Electric is known to cause this to happen. If no other program can be found to be using port 80 this knowledge base article from Microsoft may also be able to help resolve the issue http://support.microsoft.com/kb/890015

Was this helpful?
What can we do to improve the information ?