| Previous | Next |
| SCARD_E_WRITE_TOO_MANY | SCARD_E_INVALID_CHV |
SCARD_E_BAD_SEEK
Positioning inside a card object failed
SCARD_E_BAD_SEEK is a smart-card file-object positioning error. It normally arises in a card profile or middleware layer that exposes file-like access, not from an ordinary Windows file seek. The requested offset may be outside the object, unsuitable for its record structure, unsupported by the selected card application, or invalid after the object was changed or reselected.
Do not assume that every card supports arbitrary byte offsets. Some objects are record-oriented, have fixed access conditions, or are available only through card-specific commands. A generic read loop that works on one card can therefore fail on another even when the reader and transport are healthy.
What to inspect
- Log the selected application, file identifier, requested offset, length, and any record number before the failing call.
- Check the documentation for the card profile or middleware instead of applying host-file assumptions.
- After card removal or reset, reselect the relevant application and object before resuming a read sequence.
References
Looking for a different code? Search another status or error code.