| Previous | Next |
| STATUS_DIRECTORY_NOT_RM | STATUS_LOG_RESIZE_INVALID_SIZE |
STATUS_TRANSACTIONS_UNSUPPORTED_REMOTE
STATUS_TRANSACTIONS_UNSUPPORTED_REMOTE is a location and capability restriction, not an SMB authentication or share-permission failure. The documented CreateFileTransacted API requires the target object to reside on the local computer; a remote path fails with the corresponding Win32 error.
This should be distinguished from STATUS_TRANSACTIONAL_OPEN_NOT_ALLOWED. That status concerns an object or operation that cannot be opened transactionally at all, whereas this one is specifically caused by using a remote server or share for a transacted file operation.
Transactional NTFS is being requested across a remote path
- Record the fully resolved path and verify whether it is local, UNC, mapped to a share, or redirected by a namespace provider.
- Use a local transactional workflow only where its platform support is required and available; design remote work with an application-level commit or compensation model instead.
- Do not try to solve this by changing SMB credentials or share ACLs when the same request already identifies a remote target.
References
- Microsoft: CreateFileTransacted
- Microsoft: Kernel Transaction Manager overview
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.