Access Violation in MMC with Empty NetBIOS Name (296887)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Professional SP1
This article was previously published under Q296887 SYMPTOMS
When the first domain controller of a new child domain is finished with Dcpromo.exe but has not rebooted yet, attempts to start Active Directory-related MMC snap-ins may generate an access violation.
This can also occur if the NetBIOS domain name property in the cross-reference object at
CN=newdomainname,CN=Partitions,CN=Configuration,DC=rootdomainname
is empty.
CAUSE
When you install a new child domain in a forest, the cross-reference object in the configuration container is not fully populated yet. MMC snap-ins do not expect the NetBIOS domain name to be empty.
RESOLUTIONTo resolve this problem, obtain the latest service pack for 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
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
-----------------------------------------------------------
6/6/2001 03:02p 5.0.2195.3697 207,632 Objsel.dll
WORKAROUND
To work around this behavior, reboot new domain controllers soon after Dcpromo has finished. However, this leaves a small window open during which MMC may not work.
STATUSMicrosoft 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 Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbDirServices kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB296887 |
---|
|