| Previous | Next |
| STATUS_BTH_ATT_INVALID_ATTRIBUTE_VALUE_LENGTH | STATUS_BTH_ATT_INSUFFICIENT_ENCRYPTION |
STATUS_BTH_ATT_UNLIKELY
This is a protocol-level catch-all, not a diagnosis by itself
STATUS_BTH_ATT_UNLIKELY is ATT error 0x0E. The ATT server uses it when the request cannot be completed and no more precise ATT error describes the reason.
Unlike Invalid PDU, permission failures, and resource errors, this code does not identify a client-visible category of fault. It is therefore especially important to correlate it with server-side application logs, connection transitions, and earlier ATT operations instead of treating it as proof that the request bytes are malformed.
What to check
- Keep the raw ATT request and response, device firmware version, server logs, connection state, negotiated MTU, and concurrent operations.
- Retry only an operation that is demonstrably safe to repeat; a generic server failure does not tell the client whether an application action was partially processed.
- Look first for a more specific event around the same time, such as a disconnect, security transition, database change, or application exception.
References
- Bluetooth SIG: Attribute Protocol (ATT)
- Bluetooth SIG: Generic Attribute Profile (GATT)
- Microsoft: Bluetooth GATT client
Looking for a different code? Search another status or error code.