XADM: Directory Service Does Not Start and Event ID 1171 Error Message Is Logged (295658)
The information in this article applies to:
- Microsoft Exchange Server 5.5 SP4
This article was previously published under Q295658 SYMPTOMS
The Exchange Server directory service may not start, and the following error message may be logged in the Application event log:
Event ID: 1171
Source: MSExchangeDS
Type: Error
Category: Internal Processing
Description:
Exception e0010002 has occurred with parameters 9 and 2 (internal ID 30c043f).
Contact Microsoft Technical Support for assistance.
CAUSE
This problem can occur if the buffer length is miscalculated and used in a search for duplicate server names. If server names are sufficiently similar (for example, server1, server2, and server3), they may interpreted as the same name because the comparison may not use the entire string in the comparison.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server 5.5 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Component: Directory
NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.
| Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbExchange550preSP5fix kbfix kbQFE KB295658 |
|---|
|