Microsoft KB Archive/940262

= The Active Directory database size increases unexpectedly because a Windows Server 2003-based DNS server inappropriately creates several SerialNo objects =

Article ID: 940262

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition

-



SYMPTOMS
A Windows Server 2003 Server-based DNS server may create several SerialNo objects. The high number of SerialNo objects may cause the Active Directory database file (Ntds.dit) size to grow. Additionally, the high number of SerialNo objects may increase Active Directory replication.

Note This problem occurs if the Windows Server 2003-based DNS server uses Active Directory directory service-integrated zones.



CAUSE
This problem occurs because the DNS server service inappropriately creates the SerialNo objects in Active Directory for the zones that are not marked as transferable.



RESOLUTION
To resolve this problem, a hotfix is available. After you apply this hotfix, the DNS server first checks if the zone is marked as transferable before the DNS server creates a SerialNo object for the zone. Therefore, the DNS server will only create SerialNo objects for the zones that are marked as transferable.

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites
To apply the hotfix, one of the following service packs must be installed on the DNS server:
 * Windows Server 2003 Service Pack 1 (SP1)
 * Windows Server 2003 Service Pack 2 (SP2)

Restart requirement
You have to restart the DNS server after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.

Registry information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Windows Server 2003 with SP2, x64-based versions


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



The SerialNo object
The DNS server maintains a serial number that is associated with the primary zones of the DNS server. When a primary zone changes, the corresponding serial number of the zone increases. The DNS server uses this serial number as a quick check to decide whether the secondary copy of the zone is synchronized with the primary zone. This serial number is stored in a SerialNo object that is named as follows:

SerialNo-

Active Directory implements the SerialNo object as a child object of the zone object.

When the DNS service is stopped, the DNS service obtains the serial number of the primary zone that the DNS server owns. And then, the DNS server creates the SerialNo object in the Active Directory if this SerialNo object does not exist.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

