Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Exception e0010002 has occurred with parameters 9 and 0 in Exchange Server 5.0 and in Exchange Server 5.5


View products that this article applies to.

This article was previously published under Q194951

↑ Back to the top


Symptoms

During intersite replication, the Event Viewer application log logs the following event:
Event ID: 1171
Source: MSExchangeDS
Type: Error
Category: Internal Processing
Description: Exception e0010002 has occurred with parameters 9 and 0 (Internal ID 3080963). Please contact Microsoft Product Support Services for assistance.
Note The internal ID number will be different based on the Exchange Server version that is installed, but the parameters will remain the same. For example, if Exchange Server 5.5 Service Pack 3 is installed, the internal ID number is 308098a and if Exchange Server 5.5 Service Pack 4 is installed, the internal ID number is 30809ec, but the rest of the event remains the same.

↑ Back to the top


Cause

The error can be logged on an intersite directory replication bridgehead server that is trying to apply updates received from another bridgehead. The directory bridgehead server that sent in the update being processed contains one or more orphaned objects that are failing to be applied to the directory by the Directory Replication Agent (DRA).

To establish which directory replication bridgehead server is sending in the bad update:
  1. In the Exchange Server Administrator program, double-click the Directory Service object, set Replication diagnostic logging to Maximum, and Internal Processing to Minimum.
  2. Just before the 1171 error is logged, you see the following events:
    Event ID: 1099
    Source: MSExchangeDS
    Type: Information
    Category: Replication
    Description: During intersite replication, the directory replication agent (DRA) received a message with a length of size from the directory at EX:/o=Org/ou=Site/cn=Configuration/cn=Servers/cn=Remote Bridgehead Server/cn=Microsoft DSA.

    Event ID: 1068
    Source: MSExchangeDS
    Type: Information
    Category: Replication
    Description: Internal Event: The directory replication agent (DRA) was asked to synchronize replica of /o=Org/ou=Site/cn=Configuration from directory ID EX:/o=Org/ou=Site/cn=Configuration/cn=Servers/cn=Remote Bridgehead Server/cn=Microsoft DSA.
It is the directory on the Remote Bridgehead Server that has the orphaned objects. The error message is caused because the Directory Replication Agent is trying to add or modify an object whose parent no longer exists.

Typically, this might be caused when an object's parent is deleted on one server while simultaneously a child of that parent object has been added to another server in the organization.

↑ Back to the top


Workaround

To resolve this issue, you need to establish which object or objects have been orphaned, and what their parents should be. To do this, you need the Chkds utility. Chkds needs to be performed against the site listed in the Event ID 1068, which occurs just before the Event ID 1171.

Note Different versions of Chkds exist to run against Exchange Server 5.0 and 5.5. You cannot run the wrong version of Chkds against a directory.

Always make a copy of the Dsadata directory before running this utility. Chkds may be issued to customers who are experiencing the exact error message described.

To run Chkds:

  1. Stop the Microsoft Exchange Directory Service.
  2. Copy chkds to the Exchsrvr\Bin directory.
  3. At the command prompt run Chkds > chkds.txt.
If this directory has orphaned objects, Chkds output contains entries similar to the example below:
Checking reference counts  
/(1)/rdn(4)=OrgName/rdn(5)=SiteName/rdn(615)=Recipients/rdn(7262)=RecipContainer/rdn(7287)=John Orphaned
     has garbage collected parent  
/(1)/rdn(4)=OrgName/rdn(5)=SiteName/rdn(615)=Recipients/rdn(7262)=RecipContainer
					
In this case, the mailbox "John Orphaned" is orphaned because the Recipients container named "RecipContainer" no longer exists.

The above example indicates that the Recipients container needs to be re-added using the Exchange Server Administrator program (in this case, the container is named "RecipContainer").

After each orphaned object's parent has been re-added and replicated to the affected site or sites, replication can complete successfully during the next cycles.

↑ Back to the top


More information

Intrasite replication can also stop in the site that contains the directory with the orphaned objects. On various servers in the site that has the orphaned object or objects, you may also note the following symptoms:

When trying to add a mailbox, the following error message appears:
An error occurred while processing an e-mail address. To view details of the error, see the application event log in the Windows NT Event Viewer on the Microsoft Exchange Server computer.

Microsoft Exchange Administrator ID no: c1030b35
This error message indicates that more information can be found in the Event Viewer. However, the application log in Event Viewer reveals no information related to this error.

When you try to modify or update any object in the directory, the following error message appears:
This server is busy replicating and cannot be written to at this time. You can browse, but wait a few minutes before writing.

Microsoft Exchange Administrator ID no: c1030898

↑ Back to the top


Keywords: KB194951, kbprb

↑ Back to the top

Article Info
Article ID : 194951
Revision : 8
Created on : 10/28/2006
Published on : 10/28/2006
Exists online : False
Views : 299