| Previous | Next |
| SEC_E_INCOMPLETE_CREDENTIALS | SEC_E_WRONG_PRINCIPAL |
SEC_E_BUFFER_TOO_SMALL
SEC_E_BUFFER_TOO_SMALL means that the caller supplied a buffer too small for the SSPI operation. The required size is package- and operation-specific, so a fixed retry size can make the failure intermittent.
How to size buffers
Query the security context for the relevant size attributes where the package exposes them, allocate according to the documented structure, and keep input and output buffers separate when the API requires it. For Digest message processing, this status is documented by DecryptMessage.
What to log
- Buffer type, capacity and actual token or record length.
- The SSPI function and selected security package.
- Whether the buffer is caller-allocated or package-allocated.
Microsoft: DecryptMessage · QueryContextAttributes (Schannel)
Looking for a different code? Search another status or error code.