| Previous | Next |
| NS_E_METADATA_LANGUAGE_NOT_SUPORTED | NS_E_METADATA_NOT_AVAILABLE |
NS_E_METADATA_NO_RFC1766_NAME_FOR_LOCALE
What the metadata conversion failed to do
NS_E_METADATA_NO_RFC1766_NAME_FOR_LOCALE (0xC00D32D9) means Windows Media metadata handling could not translate the supplied locale identifier into an RFC 1766 language name. The failure concerns locale-to-language-tag mapping; it does not by itself mean the media metadata container is corrupt.
Evidence to capture
- The numeric locale ID/LCID supplied by the caller and how it was obtained.
- The metadata attribute or language list being read or written.
- The exact API that performs the conversion and the Windows/SDK version used by the process.
- A known supported locale ID processed by the same code path for comparison.
Focused test
Run the same metadata operation with one known locale that has a defined language tag. If that succeeds, validate the failing LCID against the target platform's locale mapping instead of rewriting the media file. If the LCID came from stored metadata, preserve the raw value before substituting a fallback language.
Correction and fallback
Use a locale ID that the target platform can map, or explicitly apply the application's documented fallback language when the metadata contract permits it. Do not invent a tag from the numeric value: different locale namespaces and custom locales can make such conversion ambiguous.
Verification
Read the attribute back and confirm the intended locale/tag pair survives a fresh metadata object. Keep one unsupported-locale test so fallback behavior remains deliberate rather than silently dependent on the machine configuration.
Technical references
- Windows Media metadata features
- Retrieving metadata attributes
- Setting metadata attributes
- Metadata editor object
- Microsoft HRESULT registry
Looking for a different code? Search another status or error code.