FIX: Load Balancer Activator Does Not Check to See If Server Name Is Already Set

The implementation of the Load Balancer does not check to see if the server name is already set. As a result, the load may not be balanced correctly, and the server name may be set twice for the same activation. In addition, if the client calls the CoCreateInstanceEx function, the COM+ Component Load Balancing (CLB) activator ignores the remote server name that is set in the activation's properties.

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.