What does HRESULT 0x80548220 (E_MBN_SMS_ENCODING_NOT_SUPPORTED) mean?

 
Previous Next
E_MBN_DEFAULT_PROFILE_EXIST E_MBN_SMS_FILTER_NOT_SUPPORTED

E_MBN_SMS_ENCODING_NOT_SUPPORTED

E_MBN_SMS_ENCODING_NOT_SUPPORTED is a Windows Mobile Broadband (MBN) HRESULT. It indicates that the modem does not support the SMS text encoding requested by the sending operation.

What to check for E_MBN_SMS_ENCODING_NOT_SUPPORTED

  • Query SMS capabilities and choose an encoding that the active device and network support.
  • Check whether the message content requires characters outside the selected encoding before composing the send request.
  • Do not silently alter security-sensitive or user-visible text merely to force it into an unsupported encoding.

Microsoft: IMbnSmsEvents::OnSmsSendComplete

Diagnostic interpretation of E_MBN_SMS_ENCODING_NOT_SUPPORTED

E_MBN_SMS_ENCODING_NOT_SUPPORTED has the HRESULT value 0x80548220. AllStat records the condition as “SMS encoding is not supported.”. For E_MBN_SMS_ENCODING_NOT_SUPPORTED, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.

Evidence to capture for E_MBN_SMS_ENCODING_NOT_SUPPORTED

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80548220 value before a wrapper converts it to an exception or Boolean result.
  • Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions E_MBN_SMS_ENCODING_NOT_SUPPORTED or the mbn / sms / encoding / supported operation.
  • Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original mbn / sms / encoding / supported condition.

Retry and recovery for E_MBN_SMS_ENCODING_NOT_SUPPORTED

Retry E_MBN_SMS_ENCODING_NOT_SUPPORTED only when the owning API documents a transient state or after the condition described as “SMS encoding is not supported.” has changed. For E_MBN_SMS_ENCODING_NOT_SUPPORTED, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.

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