MMC Hangs When You Access an OU (307284)
The information in this article applies to:
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q307284 SYMPTOMS
When you try to access an OU by using the MMC, the MMC may stop responding (hang), and it may generate an access violation error message.
CAUSE
The OU has ampersands (&) in the name, and when traversing the name, the ampersand falls on the 159th character of the string. In this case, the stack space that is being used to cache the string is damaged, and this can cause the access violation.
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
--------------------------------------------------------
06-Sep-2001 19:43 5.0.2195.39 234,768 Gdi32.dll
06-Sep-2001 19:43 5.0.2195.42 708,368 Kernel32.dll
25-Jun-2001 19:17 3.10.0.103 47,808 User.exe
06-Sep-2001 19:43 5.0.2195.43 379,664 User32.dll
06-Sep-2001 19:43 5.0.2195.42 371,984 Userenv.dll
29-Aug-2001 16:23 5.0.2195.42 1,731,024 Win32k.sys
29-Aug-2001 16:23 5.0.2195.42 178,448 Winlogon.exe
06-Sep-2001 19:43 5.0.2195.41 252,176 Winsrv.dll
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 kbenv kberrmsg kbfix kbshell kbWin2000sp3fix KB307284 |
|---|
|