Event ID 2089 Logged in ADAM Event Log on Windows Server 2003 SP1 and SP2

Symptom 1: ADAM replication Event ID 2089 is logged in the ADAM event log even after ADAM partitions are successfully backed up

Windows Server 2003 SP1 and SP2 computers running Active Directory Application Mode (ADAM) Service Pack 1 may log ADAM Replication Event ID 2089 in the ADAM event log even though Windows Backup (NTBACKUP) has successfully backed up the ADAM partition within "Backup Latency Threshold" number of days.


Symptom 2: Vssadmin tool shows multiple writers waiting for completion following a successful backup

Running the command vssadmin list writers, you see ADAM Writer, System Writer, WMI Writer and Removable Storage Manager are in state [5]: waiting for completion, after ADAM backup using NTBackup.

There are two possible causes for Event ID 2089: The ADAM partition has not been backed up in �Backup Latency Threshold (days)". In this case Symptom 1 can be seen.

1. The ADAM partition has not been backed up in �Backup Latency Threshold (days)". In this case you will see the first symptom.
2. A backup was performed using NTBackup in the last �Backup Latency Threshold (days)" and a bug prevents the DsaSignature attribute in ADAM from being properly updated by NTBackup. In this case you will see both symptoms.

1. Follow the instructions in the description text in Event ID 2089 and perform a backup of the partition as soon as possible.
2. In this case the event can be ignored. Microsoft is aware of this problem and it is corrected in Windows Server 2008 ADLDS and later versions.
   As a workaround you can manually clear the DSASignature attribute so that it shows <NOT SET>. To do this follow these steps:
   1. Open the ADAM version of LDP.exe�and connect and bind to ADAM instance listed in the Event ID 2089.
   2. From the top menu select View and then Tree.
   3. Type the DN of the partition listed in Event 2089 into the DN field and press OK. For example DC=ADAMPartition.
   4. In the left pane, select the partition so that it is highlighted.
   5. From the top menu select Browse�and then�"Modify.
   6. In the Modify field type the following:
      1. Ensure the DN field is set to the DN of the partition.
      2. In the attribute field type DsaSignature.
      3. In the value field type <not set>.
      4. In the Operation field select Replace and press ENTER.
      5. Press Run to execute the Modify operation. If successful, the result displayed in the right pane will be similar to the following:
         
         ***Call Modify...
         ldap_modify_ext_s(ld,'DC=ADAMpartition',[1]attrs,svrctrls,clntctrls);
         Modified "DC=ADAMpartition".

�

It has been found that the problem in Resolution section 2 above begins if non-Microsoft backup software which correctly updates the DSASignature has been previously used to backup ADAM and the administrator has recently switched to using NTBackup which does not update the DSASignature attribute. This means that the attribute has a value from before when the non-Microsoft backup software was used and it goes out of date which causes Event ID 2089 to be logged. Manually clearing the DsaSignature attribute resolves the problem in this case.

For more information about Event ID 2089 please view the following article in the Microsoft Knowledge Base:

914034 NTDS Replication Event 2089 is logged if Windows Server 2003 SP1 and later domain controllers are not backed up in a given time period

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.