What does HRESULT 0xC00D1096 (NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_NAME_ILLEGAL) mean?

 
Previous Next
NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_NAME_EMPTY NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_VALUE_EMPTY

NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_NAME_ILLEGAL

Meaning at the producing boundary

The symbolic result NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_NAME_ILLEGAL narrows 0xC00D1096 to the playback core WMX list item attribute name illegal condition: an item-level WMX attribute name is not legal for that media item scope. Keep the playback core WMX list item attribute name illegal boundary visible when a later dialog reduces it to a general media error.

An additional test is to record the exact spelling, namespace, item element and list-versus-item schema decision; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.

What succeeds before this failure

Two rules frame this diagnosis. First, windows Media metafiles are XML documents, but a well-formed document can still violate required ASX element and attribute rules. In this case, relative references are resolved against the containing metafile URL, and nested playlists introduce a stack and a new base URL rather than a simple flat list.

Representative case: A list-only property is copied onto each media item by a generic XML exporter. The example isolates only the producing component.

State worth preserving

Capture state before Player cleanup:

  • Decisive check: record the exact spelling, namespace, item element and list-versus-item schema decision.
  • Artifact: resolved base URL for REF or ENTRYREF targets.
  • State: current item index, alternate index and nested-playlist depth.
  • Object identity: repeat/event boundary and the media object expected at its start or end.
  • Underlying evidence: playlist URL, format, response content type and exact downloaded bytes.
  • Correlation: ASX version and element stack at the failure.

Log paths, hashes, IDs, offsets, and HRESULTs. Exclude secrets and unrelated content from logs.

Reproduce without destroying evidence

  1. Start with the symbolic value this result; do not diagnose the failure from the final dialog alone.
  2. Record the bytes or object state that produced this condition before automatic recovery mutates it.
  3. Exclude a stale callback or superseded object generation as the source of this event.
  4. Use this deciding observation for this condition: record the exact spelling, namespace, item element and list-versus-item schema decision.
  5. Apply the smallest supported remedy for this condition: replace the name with an attribute supported on the item or move it to its valid scope.

Related HRESULTs, different boundaries

ResultDifferent boundary
NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_NAME_EMPTYAn item-level WMX attribute is emitted without a name
NS_E_WMPCORE_WMX_LIST_ITEM_ATTRIBUTE_VALUE_EMPTYAn item-level WMX attribute has an empty or unusable lexical value
NS_E_WMPCORE_LIST_ENTRY_NO_REFA playlist entry object reaches list construction without an attached media reference

If this result is followed by a broader “cannot play,” “cannot load,” or “operation failed” result, preserve the earlier event. A later wrapper error may be secondary.

Recovery at the right layer

The targeted correction for this condition is to replace the name with an attribute supported on the item or move it to its valid scope. Keep the original failing input until the same operation succeeds after one controlled change.

  • Avoid flattening or rewriting a playlist before preserving the failing nesting and base-URL rules; it can destroy the artifact or state needed to explain this result.
  • Avoid assuming every unplayable item means the playlist parser itself failed; that can replace the original HRESULT with a secondary failure from another layer.

How to know the repair is real

After correction, create a fresh Player, control, parser or playlist object and rerun the smallest reproducer for this HRESULT. Verify the resulting resource, list membership, saved file, library object or play state.

Practical interpretation

Use this result, 0xC00D1096 and the symbolic phrase in traces. Correlate search keys with API and object.

Technical references


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