XADM: DS_E_BUSY After Directory Service Restore

This article was previously published under Q160850
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When a directory is restored from backup it attempts to get back copies ofall the objects that it last modified or added and that it replicated outto other computers since it was backed up; this is called backsync. Duringbacksync, you can get into a situation where it is not possible to makedirectory changes for up to 16 hours. When you attempt to modify thedirectory while it is in this state, the Microsoft Exchange ServerAdministrator program will display the following message:
The directory is busy. Wait a few minutes and try again.

Microsoft Exchange Directory
ID no: DS_E_BUSY
The following event ID will also be logged:
Event ID: 1173. A privileged operation (rights required = 0x4) on object failed because a non-security related error occurred.
CAUSE
This will most often occur after the restoration of a directory on a serverthat has the schedule on its connectors set to Never. The directory serviceagent (DSA) is hardcoded to try to backsync for up to 16 hours even if itis unable to do so.
WORKAROUND
To work around this problem, do one of the following:
  • Make sure that the schedule on the connector of the remote Directory Replication Bridgehead is not set to Never. If it is, either set it to Always to allow for the proper delivery of directory replication messages, or wait for 16 or 4 hours respectively for this to time out.

    -OR-

  • In Microsoft Exchange Server 5.0 SP1, it is possible to add a value to theregistry that will control this timeout:

    Under the HKEY_LOCAL_MACHINE subtree, add the value in minutes to the following subkey:
          Key: System\CurrentControlSet\Services\MSExchangeDS\Parameters\       Value: Replicator inter site backsync timeout      Data Type: REG_DWORD      Value data: <number-of-minutes-in-hex>						

    The hex value of "f" equals 15 minutes in the line above.

    This value is case-sensitive and must be entered as shown above.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Serverversion 4.0. This problem has been corrected in the latest U.S. ServicePack for Microsoft Exchange Server version 4.0. For information onobtaining the Service Pack, query on the following word in the MicrosoftKnowledge Base (without the spaces):
S E R V P A C K
Microsoft has confirmed this to be a problem in Microsoft Exchange Serverversion 5.0. This problem has been corrected in the latest U.S. ServicePack for Microsoft Exchange Server version 5.0. For information onobtaining the Service Pack, query on the following word in the MicrosoftKnowledge Base (without the spaces):
S E R V P A C K
MORE INFORMATION
When a directory is restored from backup it attempts to get back --backsync -- copies of all the objects which it last modifed or added whichit replicated out to other computers since it was backed up. Thesecomputers can be in the same site or another site. Backsync is necessarybecuase normally changes made at a DSA do not replicate back to thatDSA, and also the Update Sequence Number (USN) for a restored computerwill be lower than the USN it had before being restored. This means thatif any changes are made at the restored computer before it hasbacksync'ed, they will not replicate out until the USN climbs to thevalue it was before the server was restored.

If the backsync is overridden by reducing the timeout, there is a riskof this replication loss. Therefore the backsync timeout should only bereduced or eliminated when you are sure that no changes were made at therestored computer since the computer was backed up."
Properties

Article ID: 160850 - Last Review: 10/04/2013 18:06:01 - Revision: 3.3

Microsoft Exchange Server 4.0 Standard Edition, Microsoft Exchange Server 5.0 Standard Edition, Microsoft Exchange Server 5.5 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB160850
Feedback