KnowledgeBase - Webtrends fails to start when running with Microsoft IIS 5.0 on a machine that has socket pooling enabled

Webtrends fails to start when running with Microsoft IIS 5.0 on a machine that has socket pooling enabled

« Go Back
Webtrends Legacy Products
For products:
Webtrends Log Analyzer Advanced 8.0x
Webtrends Log Analyzer 8.0x
Webtrends Reporting Center 6.x
Webtrends Reporting Center 5.x
Webtrends Reporting Center 4.x

Last modified: 6/1/2011

There is a major change in functionality introduced in IIS 5.0 that may affect your ability to specify a different IP address for Webtrends to use. IIS 5.0 has a new feature named socket pooling which is used on machines that have multiple IP addresses. When socket pooling is enabled, IIS will grab every IP address on the machine, even if it is explicitly configured to not use one or more of those addresses. According to Microsoft, in IIS 4.0, each web site was bound to a different IP address. This meant that each site had its own socket which was not shared with sites bound to other IP addresses.

These sockets are created when each site starts and they can consume significant amounts of non-paged memory (RAM). This memory consumption limits the number of sites bound to IP addresses that can be created on a machine, because, after a certain number of sites are started, the machine is out of RAM. For IIS 5.0, this process has been modified so that sites bound to different IP addresses, but sharing the same port number, and they also share the same set of sockets. The end result is that more sites can be bound to an IP address on the same machine than with IIS 4.0. In IIS 5.0, these shared sockets are used flexibly among all of the started sites, thus reducing resource consumption.

This is now the default behavior for IIS 5.0. In general, this behavior should not be modified. However, if for situations that require a dedicated socket, change the DisableSocketPooling option to TRUE to revert back to the IIS 4.0 behavior. What Socket Pooling does is allow a particular service to listen on all IP addresses on a particular computer. For example, if you have one internal IP address bound to the internal interface and two IP addresses bound to the external interface, then socket pooling will allow the service, such as the IIS 5.0 FTP Service, to listen on all three IP addresses.

If you intend to configure your IIS 5.0 machine with two or more IP addresses, and bind IIS to one of the IP addresses while putting Reporting Center on a specific port on the remaining one, then socket pooling can prevent Reporting Center from being able to bind to that last IP address - IIS will still be bound to it. In order to allow Reporting Center to bind to that IP address, socket pooling must be turned off. To test if socket pooling is preventing Webtrends from using the designated IP address, first stop all IIS services on the machine. If you are then able to start the Webtrends engine and the Webtrends user interface services, consider either not running IIS on this machine or disabling socket pooling.
Was this article helpful?

Please tell us how we can make this article more useful.

Characters Remaining: 255