Multiple Ports in IIS6

External Since: Sep 24, 2003 Posts: 6

I have over 200 sites to set up on my IIS6. I use host headers with one IP
address for all the sites, the difference in the sites are the port
numbers.(http://domain.com:5000) After setting them up only about half
start. When I try to start one of the stopped one I get the following error:

"No Memory is Available for Security Information Update"

When I check the event Log this is what I see:

Cannot register the URL prefix "Http://IP#:Port#" for site "Port# Too many
listening ports have been configured in HTTP.sys. The site has been
deactivated. The data field contains the error number.

Event ID: 1131

I use a Cisco Local director for load balanceing and it is configured by
ports. Each site has a different port number, so I need to know how to tell
http.sys how many ports to open or ignore. How do I do that?

External Since: Aug 22, 2003 Posts: 1637

"MS News" <nospam.DeleteThis@nowhere.com> wrote in message
news:%23fxMdc4gDHA.1700@TK2MSFTNGP10.phx.gbl...
> I have over 200 sites to set up on my IIS6. I use host headers with one IP
> address for all the sites, the difference in the sites are the port
> numbers.(http://domain.com:5000) After setting them up only about half
> start. When I try to start one of the stopped one I get the following
error:
>
> "No Memory is Available for Security Information Update"
>
> When I check the event Log this is what I see:
>
> Cannot register the URL prefix "Http://IP#:Port#" for site "Port# Too many
> listening ports have been configured in HTTP.sys. The site has been
> deactivated. The data field contains the error number.
>
> Event ID: 1131
>
> I use a Cisco Local director for load balanceing and it is configured by
> ports. Each site has a different port number, so I need to know how to
tell
> http.sys how many ports to open or ignore. How do I do that?

HTTP.sys looks for the presence of a reg key and if it exists, then it uses
the value set for that key. If it doesn't (default...or invalid value set),
then it will set a hard-coded limit for use of NPP (see below)...

Set the following key "MaxEndpoints" at the following ~

CCS\Services\HTTP\Parameters

The acceptable values are 0 - 1024. Hence, I would tinker with this value
until you are able to see the problem disappear. The root cause is the
missing key and hence HTTP.sys for a guideline ~

Use the physical memory to compute a default -
16 for a 64Mb
64 for a 256+ Mb

--
Tom Kaminski IIS MVP
<a style='text-decoration: underline;' href="http://www.iistoolshed.com/" target="_blank">http://www.iistoolshed.com/</a> - tools, scripts, and utilities for running IIS
<a style='text-decoration: underline;' href="http://mvp.support.microsoft.com/" target="_blank">http://mvp.support.microsoft.com/</a>
<a style='text-decoration: underline;' href="http://www.microsoft.com/windowsserver2003/community/centers/iis/" target="_blank">http://www.microsoft.com/windowsserver2003/community/centers/iis/</a>