Microsoft KB Archive/169230

Dnsadmin.exe Hangs with Very Large Zone Files Last reviewed: August 21, 1997 Article ID: Q169230

The information in this article applies to: Microsoft Windows NT Server version 4.0 SYMPTOMS When you attempt to manage very large zone files with Dnsadmin.exe, it may cause the Domain Name Service (DNS) Manager tool to hang. If you select a zone name, and then click Properties from the Context menu you may notice that the Properties dialog box does not open and the cursor remains an hourglass. You may also notice that the available system memory steadily decreases. A Performance Monitor log of your system shows that the private bytes counter, associated with the Dnsadmin.exe process, is increasing dramatically as available system memory is dramatically decreasing. CAUSE This problem can occur if you have over 10,000 records in the zone file you tried to open. By attempting to read this zone file through DNS Manager, you exposed a memory leak in Dnsadmin.exe. WORKAROUND To work around this problem, use one of the following methods: Ensure that none of your zone files contain more than 10,000 records. -or- Edit your record entries in the zone file directly using a plain text editor rather than using the DNS Manager graphical user interface. STATUS Microsoft has confirmed this to be a problem in Windows NT Sever version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: ntdns lock spin freeze loss loose lose resources Keywords : kbbug4.00 NTSrv nttcp kbnetwork Version : WinNT:4.0 Platform : winnt Issue type : kbprb THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Last reviewed: August 21, 1997 © 1998 Microsoft Corporation. All rights reserved. Terms of Use.