Security Descriptor Has an Empty Owner Value (328422)


The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Server
This article was previously published under Q328422

SYMPTOMS

Your computer may log Event 1450 event messages several times per second in the Directory Service log. The event messages are similar to the following event message:Event ID: 1450
Source: NTDS SDPROP
Category: Internal Processing
Description: While processing security descriptor propagation, the directory service failed to calculate a new security descriptor for object CN=xyz,OU=abc,DC=domainname,DC=com (error 0x3f0)

CAUSE

This problem occurs because the object that the event message refers to has a security descriptor with an empty owner value. The security descriptor propagator cannot correct the problem and remove the object from its queue.

RESOLUTION

Service Pack Information

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

260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 typical 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 has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date         Time     Version        Size        File name
------------------------------------------------------------
13-Nov-2002  13:42   5.0.2195.6109    124,688   Adsldp.dll
13-Nov-2002  13:42   5.0.2195.5781    131,344   Adsldpc.dll
13-Nov-2002  13:42   5.0.2195.6109     62,736   Adsmsext.dll
13-Nov-2002  13:42   5.0.2195.6052    358,160   Advapi32.dll
13-Nov-2002  13:42   5.0.2195.6094     49,936   Browser.dll
13-Nov-2002  13:42   5.0.2195.6012    135,952   Dnsapi.dll
13-Nov-2002  13:42   5.0.2195.6076     96,016   Dnsrslvr.dll
13-Nov-2002  13:42   5.0.2195.6125     45,328   Eventlog.dll
13-Nov-2002  13:42   5.0.2195.6059    146,704   Kdcsvc.dll
01-Nov-2002  10:52   5.0.2195.6112    204,048   Kerberos.dll
21-Aug-2002  08:27   5.0.2195.6023     71,248   Ksecdd.sys
06-Nov-2002  18:02   5.0.2195.6118    507,664   Lsasrv.dll
06-Nov-2002  18:02   5.0.2195.6118     33,552   Lsass.exe
27-Aug-2002  14:53   5.0.2195.6034    108,816   Msv1_0.dll
13-Nov-2002  13:42   5.0.2195.5979    307,472   Netapi32.dll
13-Nov-2002  13:42   5.0.2195.6075    360,720   Netlogon.dll
13-Nov-2002  13:42   5.0.2195.6127    921,872   Ntdsa.dll
13-Nov-2002  13:42   5.0.2195.6100    389,392   Samsrv.dll
13-Nov-2002  13:42   5.0.2195.6120    130,320   Scecli.dll
13-Nov-2002  13:42   5.0.2195.6120    303,888   Scesrv.dll
13-Nov-2002  13:42   5.0.2195.5859     48,912   W32time.dll
04-Jun-2002  13:32   5.0.2195.5859     57,104   W32tm.exe
13-Nov-2002  13:42   5.0.2195.6100    126,224   Wldap32.dll

WORKAROUND

To work around this problem, delete the objects that the Directory Service events identify (frequently you may not have access because of the corrupted security descriptor) and wait for garbage collection (by default, this occurs in 60 days). The Directory Service continues to log Event 1450 event messages for the objects until the garbage collection occurs.

STATUS

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 Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product

A particular code path in the Directory Service permitted a security descriptor with an empty owner value to be written. Active Directory Connector (ADC) can, under certain conditions, use this code path.

The hotfix described in this article fixes the code path and stamps 'broken' objects with a default security descriptor. The new descriptor does not block inheritance and the repaired object acquires permissions that it inherits from its parent. Each time an object security descriptor is 'fixed', you receive the following event message:Event ID: 1214
Source: NTDS SDPROP
Category: Internal Processing
Description: While processing security descriptor propagation, the directory service found no security descriptor on CN=xyz,OU=abc,DC=domainname,DC=com (error 0x53a). A default security descriptor is being applied to the object. This will potentially result in the security on this object being different on this DC. Please write a new Security Descriptor on this object to correct the problem.Note: You must install this hotfix on all domain controllers that host the objects that have security descriptors that are not valid. The hofix does not replicate the security descriptor that it repairs. If the hotfix does not repair the objects, you may have to initiate full security descriptor propagation manually. For additional information about how to initiate full security descriptor propagation manually, click the following article number to view the article in the Microsoft Knowledge Base:

251343 Manually Initializing the SD Propagator Thread to Evaluate Inherited Permissions for Objects in Active Directory

Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbDirServices kbWin2kSP4fix kbhowto kbbug kbfix kbWin2000preSP4Fix KB328422 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.