| Previous | Next |
| NS_E_WMPCORE_WMX_LIST_ATTRIBUTE_NAME_EMPTY | NS_E_WMPCORE_WMX_LIST_ATTRIBUTE_VALUE_EMPTY |
NS_E_WMPCORE_WMX_LIST_ATTRIBUTE_NAME_ILLEGAL
How to classify this WMP result
NS_E_WMPCORE_WMX_LIST_ATTRIBUTE_NAME_ILLEGAL is HRESULT 0xC00D1092. At the playback core WMX list attribute name illegal checkpoint it means the WMX list contains an attribute name that is not legal for the list object; the result belongs to Windows Media playlist attribute-name validation, not to an unspecified Player failure.
An additional test is to record the exact attribute spelling, list element, source position and accepted names; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
How to prove the condition
- Find the first component that returned this result and label that event as the playback core WMX list attribute name illegal boundary.
- Freeze the input and object identity associated with the failing operation before WMP fallback or cleanup changes it.
- Reconstruct the immediately preceding successful state, then identify the call or event that crossed into failure.
- Perform the code-specific test: record the exact attribute spelling, list element, source position and accepted names.
- Make the targeted change—remove or rename the property to a documented list-level attribute while preserving its intended data separately—and repeat the same producing operation.
Minimum useful incident record
Capture state before Player cleanup:
- What to verify: record the exact attribute spelling, list element, source position and accepted names.
- Artifact: neighboring accepted attribute names on the same object.
- State: serializer or producer version that emitted the name.
- Object identity: original list element and byte/line position.
- Underlying evidence: exact attribute spelling, case and namespace text.
- Correlation: list-level schema or property set used by the Player build.
Why the producing component matters
Before changing state, remember that attribute-name validation answers whether the property is recognized and legal on the current list object; it is separate from validating the property value. A second platform rule is that exact spelling, scope and source XML position are decisive because a similarly named item-level attribute can still be illegal at list level.
Representative case: A playlist exporter writes an item-only or misspelled property on the top-level list.
Targeted fix
Resolve this result where the relevant state is produced: remove or rename the property to a documented list-level attribute while preserving its intended data separately. After correction, reload or recreate the owning object so cached failure state is not mistaken for a successful repair.
- Avoid changing the value while leaving the illegal attribute name untouched; it can destroy the artifact or state needed to explain this result.
- Avoid silently dropping unknown names before preserving the producer and source XML; that can replace the original HRESULT with a secondary failure from another layer.
Completion criteria
Technical references
- Windows Media metafile reference — normative or platform material relevant to this HRESULT.
- Metafile elements reference — API or format context.
- Playlists and media items — documentation for this HRESULT.
- XML 1.0 specification
Looking for a different code? Search another status or error code.