| Previous | Next |
| STATUS_STREAM_MINIVERSION_NOT_FOUND | STATUS_MINIVERSION_INACCESSIBLE_FROM_SPECIFIED_TRANSACTION |
STATUS_STREAM_MINIVERSION_NOT_VALID
The miniversion exists but no longer represents a valid view
STATUS_STREAM_MINIVERSION_NOT_VALID indicates that TxF recognized the requested stream miniversion, but the miniversion can no longer be opened as a valid file view. A rollback to savepoint is a common reason because it can remove the state that the miniversion described.
This is most useful when debugging applications that keep multiple transacted views of the same stream. The name may still exist and the transaction may still be active, while the particular miniversion is no longer usable.
What to check
- The sequence of miniversion creation, savepoint creation, rollback, and clear operations.
- Whether later writes or metadata changes made the earlier miniversion impossible to preserve.
- Whether the application revalidates miniversion handles after rollback.
- Whether the caller should reopen the current transacted stream instead of a saved version.
Useful distinction
STATUS_STREAM_MINIVERSION_NOT_FOUND points to an unknown miniversion. This status means TxF found enough metadata to reject the miniversion as no longer valid.
References
- Microsoft: Transactional NTFS overview
- Microsoft: How to use Transactional NTFS
- Microsoft: TXFS_SAVEPOINT_INFORMATION
- Microsoft: Kernel Transaction Manager
Looking for a different code? Search another status or error code.