Random 1168 Event Messages Are Logged After You Install Windows 2000 Service Pack 4

This article has been archived. It is offered "as is" and will no longer be updated.
After you install Microsoft Windows 2000 Service Pack 4 (SP4) on your domain controller, random 1168 errors that are similar to the following may be logged in the Directory Services event log:

Event ID: 1168
Source: NTDS Database
Description: Error 8430 (20ee) has occurred (internal ID 20612ee). Please contact Microsoft product support services for assistance.


Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


No prerequisites are required.

Restart Requirement

You must restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix 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   ----------------------------------------------------------   21-Aug-2003  18:37  5.0.2195.6748    124,688  Adsldp.dll          21-Aug-2003  18:37  5.0.2195.6748    132,368  Adsldpc.dll         21-Aug-2003  18:37  5.0.2195.6748     63,760  Adsmsext.dll        21-Aug-2003  18:37  5.0.2195.6800    381,712  Advapi32.dll        21-Aug-2003  18:37  5.0.2195.6753     69,392  Browser.dll         21-Aug-2003  18:37  5.0.2195.6680    134,928  Dnsapi.dll          21-Aug-2003  18:37  5.0.2195.6780     96,528  Dnsrslvr.dll        21-Aug-2003  18:37  5.0.2195.6753     47,376  Eventlog.dll        21-Aug-2003  18:37  5.0.2195.6759    148,240  Kdcsvc.dll          18-Jun-2003  15:43  5.0.2195.6758    205,072  Kerberos.dll        01-Aug-2003  15:40  5.0.2195.6797    509,712  Lsasrv.dll          17-Jul-2003  21:13  5.0.2195.6786    109,840  Msv1_0.dll          21-Aug-2003  18:37  5.0.2195.6601    311,568  Netapi32.dll        21-Aug-2003  18:37  5.0.2195.6791    361,232  Netlogon.dll        21-Aug-2003  18:37  5.0.2195.6810    931,600  Ntdsa.dll           21-Aug-2003  18:37  5.0.2195.6742    392,464  Samsrv.dll          21-Aug-2003  18:37  5.0.2195.6737    131,344  Scecli.dll          21-Aug-2003  18:37  5.0.2195.6737    306,448  Scesrv.dll          14-Aug-2003  16:58  5.0.2195.6801  5,232,128  Sp3res.dll          21-Aug-2003  18:37  5.0.2195.6601     51,472  W32time.dll         21-Aug-2003  18:37  5.0.2195.6741    126,224  Wldap32.dll         01-Aug-2003  15:40  5.0.2195.6797     33,552  Lsass.exe           16-Aug-2002  11:32  5.0.2195.6601     57,104  W32tm.exe           26-Mar-2003  19:37  5.0.2195.6695     71,888  Ksecdd.sys
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages
This problem occurs because Active Directory database object validation code is misfiring on some valid objects. This code was added in Windows 2000 SP4 to detect and to fix parentless objects.

Article ID: 827531 - Last Review: 02/27/2014 21:19:52 - Revision: 2.5

  • Microsoft Windows 2000 Advanced Server SP4
  • Microsoft Windows 2000 Service Pack 4
  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB827531