Low Memory Conditions Cause Server to Fail New Connections

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q188284

Expand all | Collapse all

SYMPTOMS

If a low memory condition occurs during a replication, Content Deployment may fail to accept new connections.

Back to the top

Under low-memory situations, the _beginthread call can fail as the thread pool is expanded. The internal counter tracking the number of threads in the thread pool is increased even though the call fails. When the thread pool is later decreased to 1 (using the internal counter, which no longer reselects the actual number of active threads), there will be no active threads, and all incoming connections will fail.

Back to the top

RESOLUTION

In this condition, the thread pool will never grow. Therefore, the only way to recover is to stop and restart the service.

To resolve this problem, apply the next Site Server 3.0 service pack when it becomes available.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Site Server version 3.0. This problem was corrected in the latest Microsoft Site Server version 3.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Back to the top

APPLIES TO

Microsoft Content Deployment, when used with:

Microsoft Site Server 3.0 Standard Edition

Back to the top

kbbug kbfix kbsiteserv300sp1fix KB188284

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top