| Previous | Next |
| NS_E_NETWORK_BUSY | NS_E_ALREADY_CONNECTED |
NS_E_TOO_MANY_SESS
NS_E_TOO_MANY_SESS — 0xC00D000F
What the server rejected
NS_E_TOO_MANY_SESS means the server session limit has been reached. The useful evidence is the session count and the limit at the instant a new session is rejected; bandwidth measurements alone do not explain this result.
Capture the admission state
- Configured session limit and the scope that owns it.
- Count of active sessions immediately before the rejected request.
- Client/session identifiers, start times and last activity for sessions near the limit.
- Whether disconnected clients remain accounted for until timeout or cleanup.
Evidence to collect
| Field | What to preserve |
|---|---|
| Ceiling | Exact configured limit, its unit and the server/publishing-point object that owns it. |
| Current use | Measured count/rate/size immediately before the rejected request. |
| New demand | Amount the new operation would add to the same resource. |
| Owners | Sessions, titles, streams or reservations contributing to the measured usage. |
Decision rule
The result is proved only when recorded usage plus the new demand crosses the recorded ceiling; otherwise investigate stale accounting or the object that owns the limit.
Focused test
Close one known session cleanly, verify the server removes it from the counted set, and retry one new session with the same content and protocol. If the count remains unchanged, investigate session cleanup rather than raising the limit.
Verification
At normal load, new sessions should be admitted below the configured count. A deliberate boundary test should still reject the next session when the same limit is reached, proving that the fix did not merely disable enforcement.
Technical references
- Windows Media Services system control protocol plug-ins
- Microsoft Media Server protocol
- Windows Media HTTP proxy interaction
- Windows Media HRESULT values
Looking for a different code? Search another status or error code.