| Previous | Next |
| STATUS_CORRUPT_LOG_UPLEVEL_RECORDS | STATUS_CHECKOUT_REQUIRED |
STATUS_FILE_CHECKED_OUT
An authoring lock already owns the document
STATUS_FILE_CHECKED_OUT is associated with document-authoring storage rather than an ordinary NTFS share-mode failure. The status text says the file is checked out or locked for editing by another user. SharePoint checkout, for example, locks a document for exclusive editing until it is checked in, while WebDAV defines write locks to prevent conflicting modifications.
Identify the server-side owner and lock or checkout token. A local process-handle search is not enough for a remote library: the blocking state can live in SharePoint or another WebDAV-capable service. Also distinguish checkout from co-authoring. A library configured to require checkout intentionally disables the normal concurrent editing model.
Do not delete local caches or forcibly overwrite the remote path before confirming ownership. An administrator can resolve abandoned checkouts through the repository's supported controls, but breaking an active author's lock can discard or fork edits.
What to inspect
- The document library, server-side checkout owner and time the lock was acquired.
- Whether the library requires checkout or supports co-authoring.
- WebDAV LOCK state or repository-specific editing-session metadata when applicable.
References
- Microsoft: Plan document versioning, content approval, and check-out
- IETF: RFC 4918 WebDAV locking
- Microsoft: Configure versioning for co-authoring
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.