| Previous | Next |
| STATUS_FILE_CHECKED_OUT | STATUS_BAD_FILE_TYPE |
STATUS_CHECKOUT_REQUIRED
The library policy requires an explicit checkout before editing
STATUS_CHECKOUT_REQUIRED is a policy/state failure: the file exists and may be readable, but the repository will not accept the save until the caller obtains the required checkout. This is different from STATUS_FILE_CHECKED_OUT, where another user or session already owns the editing lock.
SharePoint document libraries can be configured to require documents to be checked out before editing. In that mode, checkout establishes exclusive editing state and changes become visible through the check-in/versioning workflow. A desktop application that opens the file as though it were an ordinary writable network file can therefore read successfully and still fail on save.
Preserve the server response and repository URL, then use the supported checkout operation for that service. Changing local NTFS permissions or taking ownership of a synchronized cache does not satisfy remote library policy.
What to inspect
- Whether the target library has “Require Check Out” enabled.
- The identity used by the Office/WebDAV client and whether it can check out the document.
- Application logs showing whether checkout discovery or protocol negotiation was skipped before save.
References
- Microsoft: Plan document versioning, content approval, and check-out
- Microsoft: Configure Require Check Out
- Microsoft: SharePoint files open as read-only
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.