DocImage TraceDOCX image relationship audit

Missing rId diagnosis

Trace “the image part with relationship ID was not found.”

Microsoft documents one version of this failure: the image relationship target is set to NULL. Other packages can contain a drawing rId with no matching row or a known internal target whose package entry is absent. The inspector names the source part, rId, target and entry state; it keeps unknown target existence separate from known absence.

Inspect one copy, locally

Select a user-owned .docx copy. The parser reads package names and relationship XML in this tab; it does not display document text, execute embedded content, upload or save anything.

No file selected. Work from a copy; this tool never modifies the original.

A package finding is not a repair guarantee. If image bytes are absent, this tool cannot recreate them. Keep the original and a backup before any manual change.

How to read the states

MISSING_RELATIONSHIPThe drawing references an rId absent from that part’s .rels file.
NULL_TARGETThe relationship exists, but its target cannot identify image bytes.
MISSING_TARGETThe relationship names an internal media path that is not present in the DOCX package.

Do not edit relationship XML in the only copy. The report gives evidence for a manual decision; it does not generate a replacement image or a repaired DOCX.

Optional usage measurement

The inspector works without analytics. If you allow it, Yandex Metrica receives a page view and event names for an audit start, a complete supported image-graph diagnosis, a partial result or a read error. Our events include no file name, package path, relationship ID, target or document content. The provider can receive technical data such as IP address, browser details and cookies. No session replay or click maps.

Off until you choose. This choice does not affect document inspection.

Measurement details