What does HRESULT 0x80548228 (E_MBN_SMS_OPERATION_NOT_ALLOWED) mean?

 
Previous Next
E_MBN_SMS_FORMAT_NOT_SUPPORTED E_MBN_SMS_MEMORY_FULL

E_MBN_SMS_OPERATION_NOT_ALLOWED

E_MBN_SMS_OPERATION_NOT_ALLOWED is a Windows Mobile Broadband (MBN) HRESULT. It indicates that the SIM or device policy does not permit the requested SMS operation.

What to check for E_MBN_SMS_OPERATION_NOT_ALLOWED

  • Check SIM policy, carrier restrictions, and whether the operation is allowed for the active subscription.
  • Do not retry the identical operation until the authorization or service restriction has changed.
  • Use the carrier or managed-device workflow when permissions must be changed outside the application.

Microsoft: IMbnSmsEvents::OnSmsSendComplete

Diagnostic interpretation of E_MBN_SMS_OPERATION_NOT_ALLOWED

E_MBN_SMS_OPERATION_NOT_ALLOWED has the HRESULT value 0x80548228. AllStat records the condition as “SMS operation is not allowed.”. For E_MBN_SMS_OPERATION_NOT_ALLOWED, 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_OPERATION_NOT_ALLOWED

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80548228 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_OPERATION_NOT_ALLOWED or the mbn / sms / operation / allowed operation.
  • For E_MBN_SMS_OPERATION_NOT_ALLOWED, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.

Retry and recovery for E_MBN_SMS_OPERATION_NOT_ALLOWED

Retry E_MBN_SMS_OPERATION_NOT_ALLOWED only when the owning API documents a transient state or after the condition described as “SMS operation is not allowed.” has changed. For E_MBN_SMS_OPERATION_NOT_ALLOWED, 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.