IIS dies on startup with Event ID 115

Something happened to my Exchange server over the weekend that caused
a crash (nothing logged) and upon startup my IIS is failing with Event
ID 115 (Service could not bind instance 1). This error is logged for
both MSFTPSVC and W3SVC. All services seem to be running but OWA
access to either port 80 or 443 gets a page cannot be displayed error.
The access attempt is responded to with an account login and the logs
show the access attempt. I am running a certificate, and a port
redirection from port 80. Most docs I have found on this refer to
running multiple instances which I do not have. My securebindings in
metabase is correct. I have no other instances of either FTP or
W3SVC. This behaves exactly the same either on reboot or IIS Admin
restart. I have tried disabling SSL by removing port listener in
default web site properties and service behaves exactly the same so it
doesn't seem to be an SSL related problem.

Any suggestions greatly appreciated.

thanks

Hal

David
Tue Jun 29 19:10:55 CDT 2004

These two statements contradict each other:
1. "Service could not bind instance 1"
2. "... the [web service] logs show the access attempt"

If W3SVC could not bind instance 1, IIS is not going to respond to any
requests and is certainly not going to log any attempts.

So, either #1 is true and something ELSE is writing to the IIS log files, or
#2 is true and #1 is a red-herring.

I also wonder if you have been hacked and something is simply trying to
harvest username/password.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
<hal@nospam.com> wrote in message
news:78l3e016k9a97phgbbhf0ctg29njk91jss@4ax.com...
Something happened to my Exchange server over the weekend that caused
a crash (nothing logged) and upon startup my IIS is failing with Event
ID 115 (Service could not bind instance 1). This error is logged for
both MSFTPSVC and W3SVC. All services seem to be running but OWA
access to either port 80 or 443 gets a page cannot be displayed error.
The access attempt is responded to with an account login and the logs
show the access attempt. I am running a certificate, and a port
redirection from port 80. Most docs I have found on this refer to
running multiple instances which I do not have. My securebindings in
metabase is correct. I have no other instances of either FTP or
W3SVC. This behaves exactly the same either on reboot or IIS Admin
restart. I have tried disabling SSL by removing port listener in
default web site properties and service behaves exactly the same so it
doesn't seem to be an SSL related problem.

Any suggestions greatly appreciated.

thanks

Hal

Ken
Wed Jun 30 02:32:22 CDT 2004

I agree with David's analysis.

The most common cause of this error is because you have something *else*
listening on one of the ports IIS wants to use. See:
http://support.microsoft.com/?id=261194
You Receive an Error Message When You Try to Start the Web Service

You can use TCPView from www.sysinternals.com to work out what that other
process is:
http://www.sysinternals.com/ntw2k/source/tcpview.shtml

Cheers
Ken


<hal@nospam.com> wrote in message
news:78l3e016k9a97phgbbhf0ctg29njk91jss@4ax.com...
: Something happened to my Exchange server over the weekend that caused
: a crash (nothing logged) and upon startup my IIS is failing with Event
: ID 115 (Service could not bind instance 1). This error is logged for
: both MSFTPSVC and W3SVC. All services seem to be running but OWA
: access to either port 80 or 443 gets a page cannot be displayed error.
: The access attempt is responded to with an account login and the logs
: show the access attempt. I am running a certificate, and a port
: redirection from port 80. Most docs I have found on this refer to
: running multiple instances which I do not have. My securebindings in
: metabase is correct. I have no other instances of either FTP or
: W3SVC. This behaves exactly the same either on reboot or IIS Admin
: restart. I have tried disabling SSL by removing port listener in
: default web site properties and service behaves exactly the same so it
: doesn't seem to be an SSL related problem.
:
: Any suggestions greatly appreciated.
:
: thanks
:
: Hal

AndrewSwordMVP
Wed Jun 30 02:38:01 CDT 2004

Hi,

Try this article

http://support.microsoft.com/default.aspx?scid=kb;en-us;322023



"hal@nospam.com" wrote:

> Something happened to my Exchange server over the weekend that caused
> a crash (nothing logged) and upon startup my IIS is failing with Event
> ID 115 (Service could not bind instance 1). This error is logged for
> both MSFTPSVC and W3SVC. All services seem to be running but OWA
> access to either port 80 or 443 gets a page cannot be displayed error.
> The access attempt is responded to with an account login and the logs
> show the access attempt. I am running a certificate, and a port
> redirection from port 80. Most docs I have found on this refer to
> running multiple instances which I do not have. My securebindings in
> metabase is correct. I have no other instances of either FTP or
> W3SVC. This behaves exactly the same either on reboot or IIS Admin
> restart. I have tried disabling SSL by removing port listener in
> default web site properties and service behaves exactly the same so it
> doesn't seem to be an SSL related problem.
>
> Any suggestions greatly appreciated.
>
> thanks
>
> Hal
>