What does HRESULT 0x80040E62 (MD_E_BADCOORDINATE) mean?

 
Previous Next
MD_E_BADTUPLE MD_E_INVALIDAXIS

MD_E_BADCOORDINATE

Coordinate is invalid

Exact value and result class

MD_E_BADCOORDINATE has unsigned value 2147749474 (0x80040E62) and signed 32-bit value -2147217822. AllStat describes it as “Coordinate is invalid”. In this result, a cell or dataset operation receives a multidimensional coordinate that is invalid for the current axes.

The high bit is set, so MD_E_BADCOORDINATE is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3682 (0x0E62). For MD_E_BADCOORDINATE, these fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.

Contract boundary

For MD_E_BADCOORDINATE, OLE DB for OLAP models axes, tuples, coordinates and cells separately. For MD_E_BADCOORDINATE, a tuple identifies one member from each relevant hierarchy, a coordinate positions a cell across axes, and cell ordinals are valid only for the current dataset shape.

Investigation of MD_E_BADCOORDINATE should start with the dataset object, axis metadata, tuple construction and cellset generation used by the failing call. Capture MD_E_BADCOORDINATE before ADO, ATL, .NET or a database abstraction layer replaces the native HRESULT with a generic exception.

Diagnostic sequence

  1. Capture raw 0x80040E62 and symbolic MD_E_BADCOORDINATE at the native call boundary.
  2. Identify the exact failing stage for MD_E_BADCOORDINATE: a cell or dataset operation receives a multidimensional coordinate that is invalid for the current axes.
  3. Retrieve all OLE DB error records for MD_E_BADCOORDINATE before another COM call replaces thread error information.
  4. Compare the live object state and provider-granted capabilities with the input that produced MD_E_BADCOORDINATE.
  5. Reduce the MD_E_BADCOORDINATE operation to the smallest case that preserves the same olap contract.
  6. Apply one evidence-backed correction for MD_E_BADCOORDINATE and verify that the result is not merely replaced by a neighboring HRESULT.

Conditions that specifically lead to this result

  • Cause 1 for MD_E_BADCOORDINATE: the coordinate omits or adds an axis component.
  • Cause 2 for MD_E_BADCOORDINATE: one tuple in the coordinate is invalid.
  • Cause 3 for MD_E_BADCOORDINATE: coordinates were built for a prior dataset shape.

Evidence to collect

A useful MD_E_BADCOORDINATE event records provider CLSID and version, process architecture, interface IID and method, object correlation ID, transaction state and the immediately preceding HRESULT. When recording MD_E_BADCOORDINATE data involving member unique names, cube coordinates and calculated-measure expressions, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.

  • Evidence 1 for MD_E_BADCOORDINATE: axis count and cardinality.
  • Evidence 2 for MD_E_BADCOORDINATE: the tuple supplied for each axis.
  • Evidence 3 for MD_E_BADCOORDINATE: dataset generation and query that produced the axes.

Corrective actions

  • Action 1 for MD_E_BADCOORDINATE: derive coordinates from the current axis collection.
  • Action 2 for MD_E_BADCOORDINATE: validate every tuple before composing the coordinate.
  • Action 3 for MD_E_BADCOORDINATE: discard coordinate caches when the dataset is reexecuted.

Retry and recovery

Retry rule for MD_E_BADCOORDINATE: retry after reconstructing the coordinate against the current dataset axes. A MD_E_BADCOORDINATE retry is safe only when the relevant input, object generation, capability or external state has changed. Before replaying a modifying call that returned MD_E_BADCOORDINATE, determine whether rows, schema objects or URL resources were partially created or changed.

Do not turn MD_E_BADCOORDINATE into an unbounded retry loop. Preserve cancellation for MD_E_BADCOORDINATE and use a fresh provider object when the failed call may have left local state ambiguous.

Difference from nearby HRESULT values

MD_E_BADTUPLE concerns an invalid tuple, while MD_E_BADCOORDINATE concerns their combined placement across axes. Telemetry and remediation for MD_E_BADCOORDINATE should keep these outcomes distinct.

Practical scenario

A pivot UI reuses coordinates after a slicer changes axis shape; recalculation prevents MD_E_BADCOORDINATE. Keeping MD_E_BADCOORDINATE with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.

Developer and operations guidance

Code handling MD_E_BADCOORDINATE should release COM objects in ownership order, retain per-row, per-column or per-property statuses, and log granted capabilities rather than only requested options. While handling MD_E_BADCOORDINATE, opaque values such as HACCESSOR, HROW, HCHAPTER, DBID components and provider handles must remain scoped to the object that issued them.

Operational dashboards for MD_E_BADCOORDINATE should group by provider version, interface, method and normalized failure stage. A MD_E_BADCOORDINATE event must not expose passwords, tokens, full connection strings, unrestricted command text or raw row contents.

Official Microsoft references

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