| Previous | Next |
| NS_E_INVALID_DATA | NS_E_OPEN_FILE_LIMIT |
NS_E_FILE_BANDWIDTH_LIMIT
What NS_E_FILE_BANDWIDTH_LIMIT means
NS_E_FILE_BANDWIDTH_LIMIT (0xC00D0030) is a Windows Media Services policy failure: the bandwidth required to stream the selected file is higher than the server's maximum allowed file bandwidth. The file can exist and be readable; the rejection is about the streaming bandwidth limit, not ordinary filesystem access.
What to compare
| Evidence | Why it matters |
|---|---|
| Selected content | Record the exact file or publishing resource and the stream/bitrate information the server uses when evaluating it. |
| Server policy | Record the configured maximum file-bandwidth limit and the server or publishing-point configuration generation that was active when the request failed. |
| Request path | Keep the publishing point, protocol, client request and first server HRESULT so a later reconnect does not hide the original policy rejection. |
| Controlled comparison | Use the same publishing path with content whose required bandwidth is below the configured ceiling, or adjust the documented limit without changing unrelated server settings. |
How to diagnose it
- Confirm that the failure is
NS_E_FILE_BANDWIDTH_LIMIT, not an open-file, network, or storage error returned earlier. - Compare the required streaming bandwidth for the selected content with the server's current per-file ceiling.
- If the file was recently replaced or re-encoded, make sure the server is evaluating the current content rather than a stale object or cached configuration.
- Change only the relevant variable: use a lower-bandwidth rendition or raise the supported server limit when policy allows it.
- Repeat the same request and verify that streaming starts without replacing this HRESULT with a different failure.
Nearby results are different
NS_E_OPEN_FILE_LIMIT concerns the number of simultaneously open files, while NS_E_FILE_BANDWIDTH_LIMIT concerns the bandwidth required by one file. A successful local file open therefore does not disprove this server-side bandwidth rejection.
Technical references
Looking for a different code? Search another status or error code.