What does Windows error code 8428 (ERROR_DS_COUNTING_AB_INDICES_FAILED) mean?

Previous	Next
ERROR_DS_CONFIG_PARAM_MISSING	ERROR_DS_HIERARCHY_TABLE_MALLOC_FAILED

ERROR_DS_COUNTING_AB_INDICES_FAILED

The attempt to count the address book indices failed.

ERROR_DS_COUNTING_AB_INDICES_FAILED is Win32 error 8428 (0x000020EC) in Active Directory Domain Services (AD DS). Interpret this result at the call that produced it and use the system message above as the immediate condition rather than as a complete root cause.

Windows assigns decimal 8428 and hexadecimal 0x000020EC to this result. The decisive subject is counting Active Directory address-book indices; the value alone does not reveal which object, server, file, session, or transition failed.

Where the result appears

• processing counting Active Directory address-book indices.
• executing an LDAP, RPC, deployment, replication, or directory-management operation.
• working against a specific domain controller whose replica and schema state affect the result.
• translating extended directory diagnostics into a Win32 error for an application or administration tool.

State boundary to prove

This result applies to counting Active Directory address-book indices and does not by itself prove that the entire server, directory, disk, session, or application is unavailable. The state boundary to prove for it is whether the directory can enumerate and count all relevant address-book indices consistently. Use address-book configuration and index identifiers, count reached before failure, and Directory Service and database events as independent evidence. When evidence for it disagrees, preserve timestamps and investigate the transition instead of selecting the most convenient value.

Likely causes

• index metadata is corrupt or incomplete.
• enumeration fails partway.
• schema or address-book configuration is inconsistent.
• resource failure interrupts the count.

Diagnostic sequence

1. capture error 8428 immediately at the API boundary and record the operation that was attempted.
2. identify the exact owner of counting Active Directory address-book indices, including object generation, server, path, session, replica, or client context.
3. collect address-book configuration and index identifiers before restarting a service or changing configuration.
4. compare count reached before failure with the documented or observed precondition.
5. correlate Directory Service and database events with the Directory Service event log, LDAP extended diagnostics, replication metadata, dcdiag and repadmin output, and the calling application’s request trace.
6. determine whether side effects occurred and verify recovery after changing one responsible condition.

Evidence to collect

• address-book configuration and index identifiers.
• count reached before failure.
• Directory Service and database events.
• schema version and recent changes.

Correlate it with the Directory Service event log, LDAP extended diagnostics, replication metadata, dcdiag and repadmin output, and the calling application’s request trace. Keep the first detailed status even when a later wrapper translates it to error 8428; the first status often distinguishes transport, authorization, storage, schema, state, and application-integrity causes that share the same final Win32 result.

Handling, retry, and recovery

The recovery objective is to repair the detailed index or database condition, then repeat the count and compare it with authoritative configuration.

Retry it only after the recorded condition changes and completion state is known. Idempotent queries may be repeated after recovery, but mutations require a state check first; backoff cannot repair malformed input, corruption, missing structure, or policy rejection.

Telemetry and support fields

• record ds_counting_ab_indices_failed_api for the producing function or management operation.
• record ds_counting_ab_indices_failed_target for the file, log, session, replica, object, or server identity.
• record ds_counting_ab_indices_failed_state_before and ds_counting_ab_indices_failed_requested_transition.
• record ds_counting_ab_indices_failed_first_status for the earliest lower-level diagnostic.

For support escalation involving it, retain decimal 8428, hexadecimal 0x000020EC, the API, UTC time, target identity, and first subsystem-specific status. Include the smallest reproducible request and evidence that distinguishes this condition from nearby codes. In the context of it, many ds codes are internal or management-facing and are not tied to one public function. the producing ldap, rpc, deployment, or management api must therefore be recorded with the code.

Difference from nearby results

ERROR_DS_BUILD_HIERARCHY_TABLE_FAILED concerns hierarchy construction; this code is specific to counting address-book indices

Practical validation scenario

A schema update leaves one address-book index definition unreadable. The count fails at that identifier, allowing the administrator to correct the definition before rebuilding. The negative test should preserve the responsible condition and reproduce it; the recovery test should change only the identified cause, repeat the same operation, and verify both success and the absence of an unintended partial side effect.

Developer and administrator guidance

Administrators handling it should preserve Directory Service events, replication metadata, and the contacted domain controller before changing objects or forcing role transitions. Developers should retain LDAP extended diagnostics and object identities across wrappers so the Win32 code does not erase the actionable directory result. Code that exposes it through RPC, JSON, REST, PowerShell, or another protocol should preserve the Win32 domain, decimal 8428, hexadecimal 0x000020EC, and original component diagnostic.

References

• Microsoft: Win32 system error range containing this code — official context relevant to it.
• Microsoft: AD DS troubleshooting — official context relevant to it.
• Microsoft: repadmin — official context relevant to it.
• Microsoft: dcdiag — official context relevant to it.
• Microsoft: AD and LDS diagnostic event logging — official context relevant to it.

---

Looking for a different code? Search another status or error code.