Event: 115; Source: W3Svc

We are receiving upon the following error when our server
is starting W2k server. This error only occurs at boot
up time.

Event ID: 115
Source: W3Svc

The service could not bind instance 1.


I've looked for a solution and performed the corrective
action, but none of our websites have SSL port
definitions and the input field for the SSL port are
greyed out.

Does this error come from just the local machine website
definitions or can it come from other servers trying to
use the SSL port.

HELP.

Gary Huehnerfuss
Co-ordinated Management Systems
707-778-6800 ext 32

Dan
Wed Jul 30 12:20:05 CDT 2003

Hi Gary,

How many different webs are on this system. As you
probably already know each requires a unique IP/port
assignment.

Consider the following:

This issue can occur because the Transmission Control
Protocol/Internet Protocol (TCP/IP) suite of utilities,
which includes the SMTP, POP3, and IMAP4 protocols,
requires a unique socket for each instance. A TCP/IP
socket is composed of an Internet Protocol (IP) address
and Transmission Control Protocol (TCP) port pair. To
generate a unique socket, either the TCP port or IP
address of each instance must be unique to the given
virtual server.

This may be verified by:

1. Provide a unique IP address for each virtual server. To
do this,
either add multiple network interface cards, each with
a unique IP
address, or add multiple IP addresses to a single
network interface
card.

2. Configure the virtual server to use a specific IP
address, rather than using the "all unassigned" setting:

a. Start the Microsoft Management Console
(MMC) for the Microsoft Internet Information Service
(IIS), or the Microsoft Exchange 2000 System Manager.


b. Select the virtual server and open the
properties of the server.

c. Click the General tab, and select a
specific IP address in the "IP address" box.

Let me know if this has helped,

Dan
>-----Original Message-----
>We are receiving upon the following error when our server
>is starting W2k server. This error only occurs at boot
>up time.
>
>Event ID: 115
>Source: W3Svc
>
>The service could not bind instance 1.
>
>
>I've looked for a solution and performed the corrective
>action, but none of our websites have SSL port
>definitions and the input field for the SSL port are
>greyed out.
>
>Does this error come from just the local machine website
>definitions or can it come from other servers trying to
>use the SSL port.
>
>HELP.
>
>Gary Huehnerfuss
>Co-ordinated Management Systems
>707-778-6800 ext 32
>.
>

glh
Wed Jul 30 12:59:16 CDT 2003

Dan - there are multiple web servers on our network but
the BDC server experiencing the error only has 2 defined
sites - the default and administrative web sites. And
both have different port assignments.

Reading information about this error it made reference to
SSL and headers but I looked at both sites on this server
and they do not have SSL ports assigned.

Gary


>-----Original Message-----
>Hi Gary,
>
>How many different webs are on this system. As you
>probably already know each requires a unique IP/port
>assignment.
>
>Consider the following:
>
>This issue can occur because the Transmission Control
>Protocol/Internet Protocol (TCP/IP) suite of utilities,
>which includes the SMTP, POP3, and IMAP4 protocols,
>requires a unique socket for each instance. A TCP/IP
>socket is composed of an Internet Protocol (IP) address
>and Transmission Control Protocol (TCP) port pair. To
>generate a unique socket, either the TCP port or IP
>address of each instance must be unique to the given
>virtual server.
>
>This may be verified by:
>
>1. Provide a unique IP address for each virtual server.
To
>do this,
> either add multiple network interface cards, each
with
>a unique IP
> address, or add multiple IP addresses to a single
>network interface
> card.
>
>2. Configure the virtual server to use a specific IP
>address, rather than using the "all unassigned" setting:
>
> a. Start the Microsoft Management Console
>(MMC) for the Microsoft Internet Information Service
>(IIS), or the Microsoft Exchange 2000 System Manager.
>
>
> b. Select the virtual server and open the
>properties of the server.
>
> c. Click the General tab, and select a
>specific IP address in the "IP address" box.
>
>Let me know if this has helped,
>
>Dan
>>-----Original Message-----
>>We are receiving upon the following error when our
server
>>is starting W2k server. This error only occurs at boot
>>up time.
>>
>>Event ID: 115
>>Source: W3Svc
>>
>>The service could not bind instance 1.
>>
>>
>>I've looked for a solution and performed the corrective
>>action, but none of our websites have SSL port
>>definitions and the input field for the SSL port are
>>greyed out.
>>
>>Does this error come from just the local machine
website
>>definitions or can it come from other servers trying to
>>use the SSL port.
>>
>>HELP.
>>
>>Gary Huehnerfuss
>>Co-ordinated Management Systems
>>707-778-6800 ext 32
>>.
>>
>.
>

glh
Wed Jul 30 13:02:42 CDT 2003

Dan - I even stopped both sites and rebooted but the
error still occurred.


>-----Original Message-----
>Hi Gary,
>
>How many different webs are on this system. As you
>probably already know each requires a unique IP/port
>assignment.
>
>Consider the following:
>
>This issue can occur because the Transmission Control
>Protocol/Internet Protocol (TCP/IP) suite of utilities,
>which includes the SMTP, POP3, and IMAP4 protocols,
>requires a unique socket for each instance. A TCP/IP
>socket is composed of an Internet Protocol (IP) address
>and Transmission Control Protocol (TCP) port pair. To
>generate a unique socket, either the TCP port or IP
>address of each instance must be unique to the given
>virtual server.
>
>This may be verified by:
>
>1. Provide a unique IP address for each virtual server.
To
>do this,
> either add multiple network interface cards, each
with
>a unique IP
> address, or add multiple IP addresses to a single
>network interface
> card.
>
>2. Configure the virtual server to use a specific IP
>address, rather than using the "all unassigned" setting:
>
> a. Start the Microsoft Management Console
>(MMC) for the Microsoft Internet Information Service
>(IIS), or the Microsoft Exchange 2000 System Manager.
>
>
> b. Select the virtual server and open the
>properties of the server.
>
> c. Click the General tab, and select a
>specific IP address in the "IP address" box.
>
>Let me know if this has helped,
>
>Dan
>>-----Original Message-----
>>We are receiving upon the following error when our
server
>>is starting W2k server. This error only occurs at boot
>>up time.
>>
>>Event ID: 115
>>Source: W3Svc
>>
>>The service could not bind instance 1.
>>
>>
>>I've looked for a solution and performed the corrective
>>action, but none of our websites have SSL port
>>definitions and the input field for the SSL port are
>>greyed out.
>>
>>Does this error come from just the local machine
website
>>definitions or can it come from other servers trying to
>>use the SSL port.
>>
>>HELP.
>>
>>Gary Huehnerfuss
>>Co-ordinated Management Systems
>>707-778-6800 ext 32
>>.
>>
>.
>

Dan
Wed Jul 30 13:28:57 CDT 2003

Hi Gary,

Can you run the following in the C:\inetpub\adminscripts
directory:

adsutil enum_all > C:\metadump.txt

Send the out put to me at meos1@excite.com

Dan
>-----Original Message-----
>Dan - I even stopped both sites and rebooted but the
>error still occurred.
>
>
>>-----Original Message-----
>>Hi Gary,
>>
>>How many different webs are on this system. As you
>>probably already know each requires a unique IP/port
>>assignment.
>>
>>Consider the following:
>>
>>This issue can occur because the Transmission Control
>>Protocol/Internet Protocol (TCP/IP) suite of utilities,
>>which includes the SMTP, POP3, and IMAP4 protocols,
>>requires a unique socket for each instance. A TCP/IP
>>socket is composed of an Internet Protocol (IP) address
>>and Transmission Control Protocol (TCP) port pair. To
>>generate a unique socket, either the TCP port or IP
>>address of each instance must be unique to the given
>>virtual server.
>>
>>This may be verified by:
>>
>>1. Provide a unique IP address for each virtual server.
>To
>>do this,
>> either add multiple network interface cards, each
>with
>>a unique IP
>> address, or add multiple IP addresses to a single
>>network interface
>> card.
>>
>>2. Configure the virtual server to use a specific IP
>>address, rather than using the "all unassigned" setting:
>>
>> a. Start the Microsoft Management Console
>>(MMC) for the Microsoft Internet Information Service
>>(IIS), or the Microsoft Exchange 2000 System Manager.
>>
>>
>> b. Select the virtual server and open the
>>properties of the server.
>>
>> c. Click the General tab, and select a
>>specific IP address in the "IP address" box.
>>
>>Let me know if this has helped,
>>
>>Dan
>>>-----Original Message-----
>>>We are receiving upon the following error when our
>server
>>>is starting W2k server. This error only occurs at boot
>>>up time.
>>>
>>>Event ID: 115
>>>Source: W3Svc
>>>
>>>The service could not bind instance 1.
>>>
>>>
>>>I've looked for a solution and performed the corrective
>>>action, but none of our websites have SSL port
>>>definitions and the input field for the SSL port are
>>>greyed out.
>>>
>>>Does this error come from just the local machine
>website
>>>definitions or can it come from other servers trying to
>>>use the SSL port.
>>>
>>>HELP.
>>>
>>>Gary Huehnerfuss
>>>Co-ordinated Management Systems
>>>707-778-6800 ext 32
>>>.
>>>
>>.
>>
>.
>

Dan
Wed Jul 30 14:42:20 CDT 2003

Hi Gary,

I received your metabase and examined it..Do you run Front
page Server extensions??

I saw this in your MB. You might try going into the Front
Page Administrator and running "Check and Fix". Then try
and start the IIs service again.

Let me know how this works out,

Dan
>-----Original Message-----
>Hi Gary,
>
>Can you run the following in the C:\inetpub\adminscripts
>directory:
>
>adsutil enum_all > C:\metadump.txt
>
>Send the out put to me at meos1@excite.com
>
>Dan
>>-----Original Message-----
>>Dan - I even stopped both sites and rebooted but the
>>error still occurred.
>>
>>
>>>-----Original Message-----
>>>Hi Gary,
>>>
>>>How many different webs are on this system. As you
>>>probably already know each requires a unique IP/port
>>>assignment.
>>>
>>>Consider the following:
>>>
>>>This issue can occur because the Transmission Control
>>>Protocol/Internet Protocol (TCP/IP) suite of utilities,
>>>which includes the SMTP, POP3, and IMAP4 protocols,
>>>requires a unique socket for each instance. A TCP/IP
>>>socket is composed of an Internet Protocol (IP) address
>>>and Transmission Control Protocol (TCP) port pair. To
>>>generate a unique socket, either the TCP port or IP
>>>address of each instance must be unique to the given
>>>virtual server.
>>>
>>>This may be verified by:
>>>
>>>1. Provide a unique IP address for each virtual server.
>>To
>>>do this,
>>> either add multiple network interface cards, each
>>with
>>>a unique IP
>>> address, or add multiple IP addresses to a single
>>>network interface
>>> card.
>>>
>>>2. Configure the virtual server to use a specific IP
>>>address, rather than using the "all unassigned" setting:
>>>
>>> a. Start the Microsoft Management Console
>>>(MMC) for the Microsoft Internet Information Service
>>>(IIS), or the Microsoft Exchange 2000 System Manager.
>>>
>>>
>>> b. Select the virtual server and open the
>>>properties of the server.
>>>
>>> c. Click the General tab, and select a
>>>specific IP address in the "IP address" box.
>>>
>>>Let me know if this has helped,
>>>
>>>Dan
>>>>-----Original Message-----
>>>>We are receiving upon the following error when our
>>server
>>>>is starting W2k server. This error only occurs at
boot
>>>>up time.
>>>>
>>>>Event ID: 115
>>>>Source: W3Svc
>>>>
>>>>The service could not bind instance 1.
>>>>
>>>>
>>>>I've looked for a solution and performed the
corrective
>>>>action, but none of our websites have SSL port
>>>>definitions and the input field for the SSL port are
>>>>greyed out.
>>>>
>>>>Does this error come from just the local machine
>>website
>>>>definitions or can it come from other servers trying
to
>>>>use the SSL port.
>>>>
>>>>HELP.
>>>>
>>>>Gary Huehnerfuss
>>>>Co-ordinated Management Systems
>>>>707-778-6800 ext 32
>>>>.
>>>>
>>>.
>>>
>>.
>>
>.
>

Dan
Wed Jul 30 15:02:36 CDT 2003

Hi Gary,

I just thought about something....WHile the W3svc service
is down go to a command prompt and run C:\netstat -an >
C:\stat.txt. Mail that output to me.

Dan
>-----Original Message-----
>Hi Gary,
>
>I received your metabase and examined it..Do you run
Front
>page Server extensions??
>
>I saw this in your MB. You might try going into the Front
>Page Administrator and running "Check and Fix". Then try
>and start the IIs service again.
>
>Let me know how this works out,
>
>Dan
>>-----Original Message-----
>>Hi Gary,
>>
>>Can you run the following in the C:\inetpub\adminscripts
>>directory:
>>
>>adsutil enum_all > C:\metadump.txt
>>
>>Send the out put to me at meos1@excite.com
>>
>>Dan
>>>-----Original Message-----
>>>Dan - I even stopped both sites and rebooted but the
>>>error still occurred.
>>>
>>>
>>>>-----Original Message-----
>>>>Hi Gary,
>>>>
>>>>How many different webs are on this system. As you
>>>>probably already know each requires a unique IP/port
>>>>assignment.
>>>>
>>>>Consider the following:
>>>>
>>>>This issue can occur because the Transmission Control
>>>>Protocol/Internet Protocol (TCP/IP) suite of
utilities,
>>>>which includes the SMTP, POP3, and IMAP4 protocols,
>>>>requires a unique socket for each instance. A TCP/IP
>>>>socket is composed of an Internet Protocol (IP)
address
>>>>and Transmission Control Protocol (TCP) port pair. To
>>>>generate a unique socket, either the TCP port or IP
>>>>address of each instance must be unique to the given
>>>>virtual server.
>>>>
>>>>This may be verified by:
>>>>
>>>>1. Provide a unique IP address for each virtual
server.
>>>To
>>>>do this,
>>>> either add multiple network interface cards, each
>>>with
>>>>a unique IP
>>>> address, or add multiple IP addresses to a single
>>>>network interface
>>>> card.
>>>>
>>>>2. Configure the virtual server to use a specific IP
>>>>address, rather than using the "all unassigned"
setting:
>>>>
>>>> a. Start the Microsoft Management Console
>>>>(MMC) for the Microsoft Internet Information Service
>>>>(IIS), or the Microsoft Exchange 2000 System Manager.
>>>>
>>>>
>>>> b. Select the virtual server and open the
>>>>properties of the server.
>>>>
>>>> c. Click the General tab, and select a
>>>>specific IP address in the "IP address" box.
>>>>
>>>>Let me know if this has helped,
>>>>
>>>>Dan
>>>>>-----Original Message-----
>>>>>We are receiving upon the following error when our
>>>server
>>>>>is starting W2k server. This error only occurs at
>boot
>>>>>up time.
>>>>>
>>>>>Event ID: 115
>>>>>Source: W3Svc
>>>>>
>>>>>The service could not bind instance 1.
>>>>>
>>>>>
>>>>>I've looked for a solution and performed the
>corrective
>>>>>action, but none of our websites have SSL port
>>>>>definitions and the input field for the SSL port are
>>>>>greyed out.
>>>>>
>>>>>Does this error come from just the local machine
>>>website
>>>>>definitions or can it come from other servers trying
>to
>>>>>use the SSL port.
>>>>>
>>>>>HELP.
>>>>>
>>>>>Gary Huehnerfuss
>>>>>Co-ordinated Management Systems
>>>>>707-778-6800 ext 32
>>>>>.
>>>>>
>>>>.
>>>>
>>>.
>>>
>>.
>>
>.
>

Dan
Wed Jul 30 15:41:28 CDT 2003

Hi Gary,

Looks like the output of the netstat command shows a
listener on port 80. I ommitted your IP for security
reasons. Check out the config. Look in my mail for detail
instructions.

Best regards,

Dan
>-----Original Message-----
>Hi Gary,
>
>I just thought about something....WHile the W3svc service
>is down go to a command prompt and run C:\netstat -an >
>C:\stat.txt. Mail that output to me.
>
>Dan
>>-----Original Message-----
>>Hi Gary,
>>
>>I received your metabase and examined it..Do you run
>Front
>>page Server extensions??
>>
>>I saw this in your MB. You might try going into the
Front
>>Page Administrator and running "Check and Fix". Then try
>>and start the IIs service again.
>>
>>Let me know how this works out,
>>
>>Dan
>>>-----Original Message-----
>>>Hi Gary,
>>>
>>>Can you run the following in the
C:\inetpub\adminscripts
>>>directory:
>>>
>>>adsutil enum_all > C:\metadump.txt
>>>
>>>Send the out put to me at meos1@excite.com
>>>
>>>Dan
>>>>-----Original Message-----
>>>>Dan - I even stopped both sites and rebooted but the
>>>>error still occurred.
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>Hi Gary,
>>>>>
>>>>>How many different webs are on this system. As you
>>>>>probably already know each requires a unique IP/port
>>>>>assignment.
>>>>>
>>>>>Consider the following:
>>>>>
>>>>>This issue can occur because the Transmission Control
>>>>>Protocol/Internet Protocol (TCP/IP) suite of
>utilities,
>>>>>which includes the SMTP, POP3, and IMAP4 protocols,
>>>>>requires a unique socket for each instance. A TCP/IP
>>>>>socket is composed of an Internet Protocol (IP)
>address
>>>>>and Transmission Control Protocol (TCP) port pair. To
>>>>>generate a unique socket, either the TCP port or IP
>>>>>address of each instance must be unique to the given
>>>>>virtual server.
>>>>>
>>>>>This may be verified by:
>>>>>
>>>>>1. Provide a unique IP address for each virtual
>server.
>>>>To
>>>>>do this,
>>>>> either add multiple network interface cards, each
>>>>with
>>>>>a unique IP
>>>>> address, or add multiple IP addresses to a single
>>>>>network interface
>>>>> card.
>>>>>
>>>>>2. Configure the virtual server to use a specific IP
>>>>>address, rather than using the "all unassigned"
>setting:
>>>>>
>>>>> a. Start the Microsoft Management Console
>>>>>(MMC) for the Microsoft Internet Information Service
>>>>>(IIS), or the Microsoft Exchange 2000 System Manager.
>>>>>
>>>>>
>>>>> b. Select the virtual server and open the
>>>>>properties of the server.
>>>>>
>>>>> c. Click the General tab, and select a
>>>>>specific IP address in the "IP address" box.
>>>>>
>>>>>Let me know if this has helped,
>>>>>
>>>>>Dan
>>>>>>-----Original Message-----
>>>>>>We are receiving upon the following error when our
>>>>server
>>>>>>is starting W2k server. This error only occurs at
>>boot
>>>>>>up time.
>>>>>>
>>>>>>Event ID: 115
>>>>>>Source: W3Svc
>>>>>>
>>>>>>The service could not bind instance 1.
>>>>>>
>>>>>>
>>>>>>I've looked for a solution and performed the
>>corrective
>>>>>>action, but none of our websites have SSL port
>>>>>>definitions and the input field for the SSL port are
>>>>>>greyed out.
>>>>>>
>>>>>>Does this error come from just the local machine
>>>>website
>>>>>>definitions or can it come from other servers trying
>>to
>>>>>>use the SSL port.
>>>>>>
>>>>>>HELP.
>>>>>>
>>>>>>Gary Huehnerfuss
>>>>>>Co-ordinated Management Systems
>>>>>>707-778-6800 ext 32
>>>>>>.
>>>>>>
>>>>>.
>>>>>
>>>>.
>>>>
>>>.
>>>
>>.
>>
>.
>