Windows 2000 Parent Domain May Crash After You Log On to a Child Domain Account (816887)



The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server SP3
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Server SP3
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Professional SP3
  • Microsoft Windows 2000 Professional SP2
  • Microsoft Windows 2000 Professional SP1

SYMPTOMS

When you restart a domain controller on a child domain, immediately after you log on to this domain controller, the primary domain controller (PDC) emulator of the parent domain may stop responding with a "Stop 0x244" error message.

CAUSE

This problem may occur when you have turned on the CrashOnAuditFail local policy on the parent domain.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend 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 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 Global 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
   --------------------------------------------------
   16-Feb-2003  16:30  5.0.2195.6613     124,176  Adsldp.dll
   16-Feb-2003  16:30  5.0.2195.6601     130,832  Adsldpc.dll
   14-Mar-2003  13:35  5.0.2195.6667      62,736  Adsmsext.dll
   14-Mar-2003  13:35  5.0.2195.6682     381,200  Advapi32.dll
   16-Feb-2003  16:30  5.0.2195.6611      49,936  Browser.dll
   14-Mar-2003  13:35  5.0.2195.6680     136,464  Dnsapi.dll
   16-Feb-2003  16:30  5.0.2195.6663      96,528  Dnsrslvr.dll
   14-Mar-2003  13:35  5.0.2195.6679      45,840  Eventlog.dll
   16-Feb-2003  16:30  5.0.2195.6627     148,240  Kdcsvc.dll
   20-Feb-2003  16:11  5.0.2195.6666     204,560  Kerberos.dll
   04-Mar-2003  08:00  5.0.2195.6678      71,888  Ksecdd.sys
   14-Mar-2003  13:33  5.0.2195.6685     509,712  Lsasrv.dll
   14-Mar-2003  13:33  5.0.2195.6685      33,552  Lsass.exe
   05-Mar-2003  13:12  5.0.2195.6680     109,328  Msv1_0.dll
   16-Feb-2003  16:30  5.0.2195.6601     312,592  Netapi32.dll
   16-Feb-2003  16:30  5.0.2195.6627     360,720  Netlogon.dll
   14-Mar-2003  13:35  5.0.2195.6672     929,552  Ntdsa.dll
   14-Mar-2003  13:35  5.0.2195.6680     392,464  Samsrv.dll
   14-Mar-2003  13:35  5.0.2195.6678     131,344  Scecli.dll
   14-Mar-2003  13:35  5.0.2195.6678     306,448  Scesrv.dll
   16-Feb-2003  16:30  5.0.2195.6601      51,472  W32time.dll
   16-Aug-2002  05:32  5.0.2195.6601      57,104  W32tm.exe
   14-Mar-2003  13:35  5.0.2195.6666     125,200  Wldap32.dll
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/10/2005
Keywords:kbHotfixServer kbQFE kbWin2000preSP4Fix kbfix kbbug KB816887