| Previous | Next |
| STATUS_BTH_ATT_READ_NOT_PERMITTED | STATUS_BTH_ATT_INVALID_PDU |
STATUS_BTH_ATT_WRITE_NOT_PERMITTED
The server recognizes the attribute but does not accept writes to it
STATUS_BTH_ATT_WRITE_NOT_PERMITTED is the Windows NTSTATUS form of ATT error 0x03. The handle is valid, yet the attribute's permissions do not allow the write procedure that reached the ATT server.
It should not be collapsed into an invalid value error. Here the server rejects the operation before treating the supplied value as an acceptable candidate. A control point, descriptor, or characteristic may also require a different procedure, such as a write request instead of a write command, or profile-defined sequencing.
What to check
- Capture whether the client used Write Request, Write Command, Prepare Write, or Execute Write, along with the exact target handle and value length.
- Compare the selected procedure with the characteristic properties and the profile specification; changing payload bytes will not fix a disallowed write path.
- For an operation with side effects, avoid automatic retries until the client has established whether any earlier request could have reached the application layer.
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.