Select the product you need help with

ADAM service runs slowly or stops responding during garbage collection

Article ID: 973284 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You have a computer that is running Windows Server 2003.
You install Active Directory Application Mode (ADAM) on this computer.
You have configured multiple replicas of the application naming context for ADAM.

In this scenario, the server may periodically run slowly for several minutes or may periodically stop responding for several minutes. This issue occurs every several hours. Additionally, one or more of the following events are added to the ADAM log:

Event Type: Error
Event Source: ADAM [Instance Name]
Event Category: (14)
Event ID: 623
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description: < Instance Name1 ><PID>< Instance Name2 >The version store for this instance (0) has reached its maximum size of <number>. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
SessionId: <id>
Session-context: <context>
Session-context ThreadId: <id>
Cleanup: 1

Event Type: Error
Event Source: ADAM [Instance Name]
Event Category: Internal Processing
Event ID: 1519
Date: <date>
Time: <time>
User: NT AUTHORITY\LOCAL SERVICE
Computer: <computer name>
Description: Internal Error: Active Directory could not perform an operation because the database has run out of version storage. Additional Data Internal ID: <number>

Event Type: Error
Event Source: ADAM [Instance Name]
Event Category: Replication
Event ID: 1479
Description: Active Directory could not update the following object on the local domain controller with changes received from the following source domain controller. Active Directory does not have enough database version store to apply the changes.
Object: <object DN>
Object GUID: <object GUID>
Source domain controller: <DC GUID-based DNS name> User Action
Restart this domain controller. If this does not solve the problem, increase the size of the database version store. If you are populating the objects with a large number of values, or the size of the values is especially large, decrease the size of future changes.
Additional Data
Error value: 8573 The database is out of version store.

If you use Performance Monitor (Perfmon.exe) to monitor the computer, you find that the CPU usage and the disk I/O are very high when this issue occurs.

If you enable the garbage collection event logging according to Microsoft Knowledge Base (KB) article 314980, you find that the garbage collection process runs when this issue occurs. However, the tombstone objects are not deleted.

Back to the top | Give Feedback

CAUSE

Refer to the "Cause" section in KB article 974803.

974803

(http://support.microsoft.com/kb/974803/ )

The domain controller runs slower or stops responding when the garbage collection process runs

Back to the top | Give Feedback

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

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

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

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running Windows Server 2003 Service Pack 2 (SP2). Additionally, ADAM must be installed on the computer.

For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

889100

(http://support.microsoft.com/kb/889100/ )

How to obtain the latest service pack for Windows Server 2003

Installation instructions

To install this hotfix, follow these steps:

Log on as an administrator.
Stop the related ADAM instance.
Open an ADAM Tools Command Prompt window.
At a command prompt, type the following commands, and then press ENTER after each command:
dsdbutil
semantic database analysis
go fixup
Restart the related ADAM instance.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2003 file information notes

In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2003

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Dsdbutil.exe	1.1.3790.4663	231,424	11-Feb-2010	11:38	x86

For all supported x64-based versions of Windows Server 2003

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Dsdbutil.exe	1.1.3790.4663	336,384	12-Feb-2010	07:57	x64

Back to the top | Give Feedback

WORKAROUND

To work around this issue, increase the size of the version storage by changing the value of the following registry item:

Location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_<Instance-Name>\Parameters

Name:

EDB max ver pages

(increment over the minimum)
Type:

REG_DWORD

Value:

<value>

Note The value for this registry item represents the number of 16 KB memory chunks that are reserved. The following table contains some sample values for this registry item and the corresponding amount of memory that is reserved.

Collapse this tableExpand this table

Value	Reserved memory
9600	152 MB
12800	202 MB
16000	252 MB
19200	302 MB

Note We recommend that you do not set an arbitrary high value for this registry item because the computer may run out of memory in the Lsass.exe process space for other tasks. This recommendation is especially true on an x86-based version of Windows.

When testing for the required value, we recommend that you approach the required value in increments of 50 MB. The value that enables garbage collection to work is the value that we recommended you first try on any other affected computer. If the garbage collector does not run successfully when the value is 19200 (302 MB), we recommend that you contact Microsoft Customer Support Services for help.

Increasing the size of the version storage is only a temporary workaround for this issue. This workaround enables the garbage collection code to pass the inconsistent objects. However, this issue may occur again when the next tombstone lifetime interval occurs, or when the objects meet the requirements for the Garbage Collector scan again.

Note

A value change for the registry item is applied after you restart the ADAM instance.
You may experience the same issue if Active Directory Lightweight Directory Services (AD LDS) is enabled on a computer that is running Windows Server 2008 or Windows Server 2008 R2. To work around this issue in this scenario, use this same workaround.

Back to the top | Give Feedback