| Previous | Next |
| NS_E_NAMESPACE_TOO_MANY_CALLBACKS | NS_E_NAMESPACE_CALLBACK_NOT_FOUND |
NS_E_NAMESPACE_DUPLICATE_CALLBACK
Where the condition occurs
This result (0xC00D1390) marks the same callback identity is being registered twice on one node. The code identifies a narrow server contract, so diagnosis should preserve the object instance and the first native return.
Code-specific failure anatomy
A representative occurrence is when the same callback identity is being registered twice on one node. Capture node path, callback COM identity, registration stack, plug-in instance and enable/disable sequence together with the object instance and the exact administrative or protocol request.
For a useful negative control, make registration idempotent or unregister the original callback before replacing it.
The tempting but misleading response is adding another wrapper object around the same callback without fixing lifecycle ownership. That action does not test the distinction that matters here: too many callbacks is capacity exhaustion; duplicate callback is an identity/lifecycle error even when capacity remains.
Evidence that separates this code
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “the same callback identity is being registered twice on one node”. |
Test the owning precondition
- Capture
0xC00D1390, the symbolic name, the exact API/administrative action and the first failure timestamp. - Preserve node path, callback COM identity, registration stack, plug-in instance and enable/disable sequence.
- Perform one isolated experiment: make registration idempotent or unregister the original callback before replacing it.
Repeat the test with a newly resolved server object; a stale COM pointer can make a correct configuration appear unchanged.
Comparison with adjacent states
Primary distinction: too many callbacks is capacity exhaustion; duplicate callback is an identity/lifecycle error even when capacity remains.
| Nearby result | Different condition |
|---|---|
NS_E_NAMESPACE_CALLBACK_NOT_FOUND | an unregister operation names a callback that is not attached to the node. |
NS_E_NAMESPACE_TOO_MANY_CALLBACKS | the callback collection attached to one namespace node has reached its implementation limit. |
NS_E_NAMESPACE_NAME_TOO_LONG | a node name exceeds the namespace component length accepted by the server. |
Changes that do not establish the cause
- adding another wrapper object around the same callback without fixing lifecycle ownership.
- a successful ping or local file open is not sufficient proof: the failing service account and Windows Media Services object must perform the same operation.
Technical references
Looking for a different code? Search another status or error code.