What does HRESULT 0x80548226 (E_MBN_SMS_UNKNOWN_SMSC_ADDRESS) mean?

 
Previous Next
E_MBN_SMS_NETWORK_TIMEOUT E_MBN_SMS_FORMAT_NOT_SUPPORTED

E_MBN_SMS_UNKNOWN_SMSC_ADDRESS

E_MBN_SMS_UNKNOWN_SMSC_ADDRESS is a Windows Mobile Broadband (MBN) HRESULT. It indicates that the SMS operation uses an unknown or incomplete short-message service centre address.

What to check for E_MBN_SMS_UNKNOWN_SMSC_ADDRESS

  • Check carrier provisioning and the SMSC value exposed by the SIM or modem.
  • Do not hard-code a service-centre address unless the carrier explicitly requires and supplies it.
  • Refresh the device profile after a SIM or carrier change before retrying SMS delivery.

Microsoft: IMbnSmsEvents::OnSmsSendComplete

Diagnostic interpretation of E_MBN_SMS_UNKNOWN_SMSC_ADDRESS

E_MBN_SMS_UNKNOWN_SMSC_ADDRESS has the HRESULT value 0x80548226. AllStat records the condition as “Unknown SMSC address is used.”. For E_MBN_SMS_UNKNOWN_SMSC_ADDRESS, 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_UNKNOWN_SMSC_ADDRESS

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80548226 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_UNKNOWN_SMSC_ADDRESS or the mbn / sms / unknown / smsc / address operation.
  • Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original mbn / sms / unknown / smsc / address condition.

Retry and recovery for E_MBN_SMS_UNKNOWN_SMSC_ADDRESS

Retry E_MBN_SMS_UNKNOWN_SMSC_ADDRESS only when the owning API documents a transient state or after the condition described as “Unknown SMSC address is used.” has changed. For E_MBN_SMS_UNKNOWN_SMSC_ADDRESS, 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.