Cluster Server Log Filling with Erroneous Security Descriptor Information

ID: Q216329

The information in this article applies to:

SYMPTOMS

After the installation of Windows NT Service Pack 4, Cluster Server logging will now capture much more information than is necessary. The unnecessary information is Security Descriptor information. For example,

279::21-23:46:51.543 [ClRtlCopySecurityDescriptor] psd = 0x0019a600
1a8::21-23:46:51.543 [API] Did not find Security Descriptor key in the cluster DB


CAUSE

While adding logging capabilities during Service Pack 4 timeframe, the code logged all the Security Descriptor logable events, instead of determining when they would be valid. In this situtation, they are only valid in a mixed Windows NT 4.0 and Windows 2000 cluster configuration.


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual fix. For information on obtaining the latest service pack, please go to:

For information on obtaining the individual fix, 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/support/supportnet/default.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0 Service Pack 4. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Additional query words: 4.00 sp4 


Keywords          : ntsp kbbug4.00 kbfix4.00 nt4sp5fix 
Version           : winnt:4.0 SP4
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: May 5, 1999