| Previous | Next |
| WINBIO_E_DATABASE_NO_RESULTS | WINBIO_E_DATABASE_EOF |
WINBIO_E_DATABASE_NO_MORE_RECORDS
WINBIO_E_DATABASE_NO_MORE_RECORDS indicates that enumeration reached the end of the result set. It is a terminal query condition, not database corruption.
What to check for WINBIO_E_DATABASE_NO_MORE_RECORDS
- Stop enumerating records and release any query or session resources as appropriate.
- Start a new query before expecting additional records after the database changes.
- Do not translate this result into a failed enrollment or failed sensor message for users.
Microsoft: Storage Adapter Functions
Microsoft: Windows Biometric Framework client error codes
Diagnostic interpretation of WINBIO_E_DATABASE_NO_MORE_RECORDS
WINBIO_E_DATABASE_NO_MORE_RECORDS has the HRESULT value 0x80098020. AllStat records the condition as “All records from the most recent database query have been viewed.”. For WINBIO_E_DATABASE_NO_MORE_RECORDS, in practice, interpret that wording at the boundary owned by Windows Biometric Framework, rather than treating the value as a generic Windows message.
Evidence to capture for WINBIO_E_DATABASE_NO_MORE_RECORDS
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80098020 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 WINBIO_E_DATABASE_NO_MORE_RECORDS or the winbio / database / more / records operation.
- For WINBIO_E_DATABASE_NO_MORE_RECORDS, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.
Retry and recovery for WINBIO_E_DATABASE_NO_MORE_RECORDS
Retry WINBIO_E_DATABASE_NO_MORE_RECORDS only when the owning API documents a transient state or after the condition described as “All records from the most recent database query have been viewed.” has changed. For WINBIO_E_DATABASE_NO_MORE_RECORDS, 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.