| Previous | Next |
| NS_E_FILE_NOT_FOUND | NS_E_INVALID_NAME |
NS_E_FILE_EXISTS
NS_E_FILE_EXISTS — 0xC00D001B
Diagnosing NS_E_FILE_EXISTS
NS_E_FILE_EXISTS identifies this Windows Media Services boundary: the file already exists.
Why this boundary matters
This HRESULT is tied to one concrete file operation. Preserve the canonical path, service identity, access and sharing mode, requested offset or allocation, and the first native filesystem/storage result; a later server HRESULT can hide the original failure.
Evidence to collect
| Field | What to preserve |
|---|---|
| Object | Canonical path or server-side file identity plus the exact open/read/write/allocate operation. |
| Security | Service account, desired access and sharing mode used by that operation. |
| Extent | Offset or allocation size, requested byte count and completed byte count where applicable. |
| Native result | The first filesystem/storage error returned before Windows Media maps it to this HRESULT. |
Decision rule
A path that exists is not enough: success requires the same service identity to complete the same file operation with the expected size and sharing semantics.
Focused test
Enumerate the existing object or connection, decide whether it should be reused or removed, and avoid creating a second object with the same identity.
Verification
Repeat the same file operation under the same service identity and against the same object. Require the requested open/read/write/allocation to complete with the expected byte count or state; a different native result is a new diagnostic boundary.
Technical references
- Expanded use of publishing points
- Sending ASF data to a publishing point
- Receiving a live stream
- Microsoft HRESULT values for the Windows Media namespace
Looking for a different code? Search another status or error code.