Cluster Loses Track of Custom Resource DLL Registration After Resource Monitor Failure (242398)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Cluster Server
This article was previously published under Q242398

SYMPTOMS

If a resource monitor fails, and that resource monitor controls a resource that uses a dynamic-link library (DLL) resource other than Clusres.dll, the Cluster service may lose track of the resource DLL. When this occurs, the resource may not behave properly. Also, the CluAdmin tool displays a null resource type for the resource.

RESOLUTION

Windows NT Server, Cluster Server, or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp


Windows NT Server 4.0, Terminal Server Edition

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

152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 Cluster Server. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.
Modification Type:MajorLast Reviewed:10/28/2003
Keywords:kbbug kbfix KB242398 kbAudDeveloper
©2003 Microsoft Corporation. All rights reserved.