"Exception e0010002 has occurred with parameters 9 and 0 (internal ID 30809ec). Contact Microsoft Technical Support for assistance."

i get this evevnt on the exchange server (5.5 on Nt4 With the last SP $ HF)

evevt Id 1171 with the message above.

if some one have idea i'll be glad to knew.

Thank you
TM

quote:

---

Originally posted by TM:
Hello

"Exception e0010002 has occurred with parameters 9 and 0 (internal ID 30809ec). Contact Microsoft Technical Support for assistance."

i get this evevnt on the exchange server (5.5 on Nt4 With the last SP $ HF)

evevt Id 1171 with the message above.

if some one have idea i'll be glad to knew.

Thank you
TM

---

Hello,

There are two ways how to resolve the problem:

1.
Here is a brief explanation of whatÆs going on & what we will need to do to resolve this issue.

SYMPTOMS
=======

During Intersite replication the application log of the Event Viewer will log the following event:
Event ID: 1171
Source: MSExchangeDS
Type: Error
Category: Internal Processing
Description:
Exception e001002 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 installed, but the parameters will remain the same.
CAUSE
====

The error can be logged on an intersite directory replication bridgehead which is trying to apply updates received from another bridgehead. The directory bridgehead server which sent in the update being processed contains orphaned object(s) which 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, turn on Replication diagnostic logging (on the Directory Service object in the Exchange Administrator) to Maximum and IInternal Processing to Minimum.
Just before the 1171 error is logged you will 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 object(s). 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 will need to establish which object(s) have been orphaned, and what their parents should be. To do this, the CHKDS utility is needed. CHKDS will need to be performed against the site listed in the Event ID 1068, which occurs just before the 1171 event ID.
NOTE: Different versions of Chkds exist to run against Exchange 5 and 5.5. you will not be able to run the wrong version of Chkds against a directory.
Always make a copy of the Dsadata directory before running this utility.
(it might be a good idea to do a off-line backup of all the DSADATA)
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 the output of chkds will contain entries similar to the example below:
Checking reference counts
/(1)/rdn(4)=OrgName/rdn(5)=SiteName/rdn(615)=Recipients/rdn(7262)=RecipConta
iner/rdn(7287)=John Orphaned
has garbage collected parent
/(1)/rdn(4)=OrgName/rdn(5)=SiteName/rdn(615)=Recipients/rdn(7262)=RecipConta
iner
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 Administrator; (in this case, the container is named ôRecipContainerö).
Once each orphaned objectÆs parent has been re-added and replicated to the affected site(s), replication will complete successfully during the next cycles.
MORE INFORMATION
===============
In the site that has the orphaned object(s), the following symptoms may also be noted:
When trying the add a mailbox a pop up 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 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 trying to modify or update any object in the directory the pop up 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

This is in fact what solved the situation in several cases. For more information see Microsoft Konwledge Base Article XADM: Orphaned Objects and Exchange Server Directory [Q179573]

2.

Delete the concerned directory replication connector and reinstall it. This will cause deletion of all orphaned objects and a recreation of the directory information on the concerned sites. This should only be a last resort solution.

Hope this helps.

P.S:
For the checkds-utility you have to contact microsoft support.

Good luck