Error Message: A Directory Service Operation Failed Because the Database Has Run Out of Version Storage (325705)



The information in this article applies to:

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

This article was previously published under Q325705

SYMPTOMS

You may receive the following error message on a domain controller:
Event ID 1519: A Directory Service Operation Failed Because the Database Has Run Out of Version Storage.
This event lasts about 30 minutes.

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 Microsoft 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 English version of this hotfix 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
   -----------------------------------------------------
   03-Sep-2002  08:07  6.1.3940.30  1,115,408  Esent.dll        
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product

How to Detect that your Attribute is not Actually Larger than the Version Store

The event ID 1479 NTDS Replication Error event message that accompanies the event ID 1519 NTDS General Warning event message indicates the object or objects that are having problems with replication. In the following example, the event description specifies the object GUID and the source server SPN:Event Type: Warning
Event Source: NTDS General
Event Category: (9)
Event ID: 1519
Description:
A Directory Service operation failed because the database has run out of version storage.Event Type: Error
Event Source: NTDS Replication
Event Category: (5)
Event ID: 1479
Description:
Replication error: The directory replication agent (DRA) couldn't update object CN=<ObjectDsa> (GUID <ObjectGuid>) on this system with changes which have been received from source server SourceDCsDsaGuid._msdcs.mydomain.com. The database system does not have enough temporary memory to apply the changes.

The error message is:
The specified object is too large. If you run the repadmin /getchanges naming context command, and then export the results of this command to a file, you can search for the object GUID.

Example Syntax

repadmin /getchanges DC=ad,DC=mydomain,DC=com > getchanges.txt

Example Output

(17) add CN=<ObjectDsa>
      1> parentGUID: <ParentGuid>
      1> objectGUID: <ObjectGuid>
      3> objectClass: top; leaf; 
      1> instanceType: 4
      1> whenCreated: <TimeStamp>
      1> showInAdvancedViewOnly: TRUE
      1> nTSecurityDescriptor: <992 byte item>
      1> name: <ObjectName>
      1> oMTIndxGuid: <1 byte item>
      1> currentLocation: <32 byte item>
      1> timeRefresh: 921
      1> objectCategory: <ObjectCategoryDsa>

The relevant data is in the Current Location attribute. The Current Location attribute indicates the size of the binary item that is attached to the object. If this size is not very large (the size is not very large in the previous example), it is likely you are experiencing this bug.

Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE kbWin2000preSP4Fix KB325705 kbAudITPRO