| Previous | Next |
| NS_E_ARCHIVE_GAP_DETECTED | NS_E_BAD_MARKIN |
NS_E_AUTHORIZATION_FILE_NOT_FOUND
Mechanism and scope
This result (0xC00D1590) marks an authorization plug-in cannot open the configured policy/ACL file. The most useful interpretation starts with the Windows Media Services object that returned the HRESULT.
Build a reproducible incident record
| First lower-level result | Preserve the earliest Win32, socket, COM, parser or plug-in event before the HRESULT; later wrappers can map several causes to this result. |
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “an authorization plug-in cannot open the configured policy/ACL file”. |
Do not merge nearby HRESULT values
Primary distinction: source file errors concern media/data sources; this file belongs to the authorization decision path.
| Nearby result | Different condition |
|---|---|
NS_E_WIZARD_RUNNING | a second administrative wizard is started while another wizard owns shared configuration state. |
NS_E_ARCHIVE_GAP_DETECTED | the archive writer observed a discontinuity in the incoming source. |
NS_E_INVALID_LOG_URL | the multicast logging URL does not match the HTTP endpoint form expected by the logging path. |
Code-specific failure anatomy
A representative occurrence is when an authorization plug-in cannot open the configured policy/ACL file. Capture configured path, service-account access, deployment package, current working/base directory and first Win32 file error together with the object instance and the exact administrative or protocol request.
For a useful negative control, deploy the intended authorization file at the configured absolute path and validate it under the WMServer identity.
The tempting but misleading response is disabling authentication or granting broad access to hide the missing policy. That action does not test the distinction that matters here: source file errors concern media/data sources; this file belongs to the authorization decision path.
Smallest useful experiment
- Capture
0xC00D1590, the symbolic name, the exact API/administrative action and the first failure timestamp. - Preserve configured path, service-account access, deployment package, current working/base directory and first Win32 file error.
- Perform one isolated experiment: deploy the intended authorization file at the configured absolute path and validate it under the WMServer identity.
Changes that do not establish the cause
- disabling authentication or granting broad access to hide the missing policy.
Technical references
Looking for a different code? Search another status or error code.