Server May Leak Samr Handles If an Error Path Is Hit in a Client Function Call

Operations on domain controllers that require using the samr named pipe may not work if the 2,048 samr limit is reached. If this occurs, you must reboot the domain controller to resume normal operation.

This situation may be caused by a specific samr leak on the server that occurs only with some client programs that call an unpublished SAM function if a problem occurs in the function call. The unpublished function works if no error path is hit.

Windows 2000

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:

Windows NT 4.0

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

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 3.