Exception e0010002 has occurred with parameters 9 and 0 in Exchange Server 5.0 and in Exchange Server 5.5 (194951)
The information in this article applies to:
- Microsoft Exchange Server 5.0
- Microsoft Exchange Server 5.5
This article was previously published under Q194951 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.
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:
- In the Exchange Server Administrator program, double-click the Directory Service object, set Replication diagnostic logging to Maximum, and Internal Processing to Minimum.
- 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.
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:
- Stop the Microsoft Exchange Directory Service.
- Copy chkds to the Exchsrvr\Bin directory.
- 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.
Modification Type: | Minor | Last Reviewed: | 8/14/2006 |
---|
Keywords: | kbprb KB194951 |
---|
|