PMAdmin Add Dbserver /Maxconnection Does Not Work

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q188363

Expand all | Collapse all

SYMPTOMS

"PMAdmin add dbserver /maxconnection" always sets maxconnection to 0. This renders the partition unusable until the Maximum Connections can be reset.

Back to the top

RESOLUTION

To resolve this problem, apply the latest Site Server 3.0 service pack.

Back to the top

To work around this problem, use the Microsoft Management Console (MMC) to set the Maximum Connections. To modify the Maximum Connections in the MMC, in the left pane, right-click on the LDAP service of your Membership Instance and choose Properties. From the LDAP Properties page, select the Directory Properties tab. In the Container Partition drop-down box, select the partition you want to edit. From the list of databases, select the one you want to change, and click Edit. Edit the Maximum Connections in the Database Server Properties box.

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 about 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 Site Server 3.0 Standard Edition

Back to the top

kbbug kbfix kbsiteserv300sp1fix KB188363

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