| Previous | Next |
| ERROR_EFS_NOT_ALLOWED_IN_TRANSACTION | ERROR_LOG_GROWTH_FAILED |
ERROR_TRANSACTIONAL_OPEN_NOT_ALLOWED
The object cannot be opened through the transactional file API contract
ERROR_TRANSACTIONAL_OPEN_NOT_ALLOWED is a Transactional NTFS (TxF) file-system status. CreateFileTransacted is for files, file streams, and directories that can participate in TxF. Microsoft directs callers to ordinary CreateFile for other object types such as named pipes, physical devices, and mailslots. This status indicates that the requested object itself is not eligible for a transactional open, rather than saying the transaction handle is invalid.
Log the resolved object type and final path after reparse-point processing. Generic filesystem wrappers can route devices, special namespaces, or unsupported filesystem objects through CreateFileTransacted simply because a transaction handle is available. Split transactional and nontransactional open paths based on the resource contract. Do not retry with broader access or FILE_ALL_ACCESS; access masks cannot make an unsupported object transactional.
What to inspect
- Resolve the target object type and filesystem before choosing CreateFileTransacted.
- Check generic wrappers that apply a transaction handle to devices or special namespaces.
- Use the nontransacted API for objects outside the TxF file, stream, and directory model.
References
- Microsoft: CreateFileTransacted and miniversion views
- Microsoft: Transactional NTFS overview
- Microsoft: TxF programming considerations and error range
Looking for a different code? Search another status or error code.