| Previous | Next |
| NS_I_START_DISK | NS_I_STOP_CUB |
NS_I_STOP_DISK
NS_I_STOP_DISK — 0x400D005B
This result belongs to administrator-requested disk stop not to a generic restart checklist, because an administrator explicitly requested that a content disk stop participating in the server.
What the status actually records
Administrative information messages record who requested a transition and which object was targeted. In the context of administrator-requested disk stop, they do not guarantee that the requested start, stop, rebuild, or removal completed, so the follow-up object-state event is essential. Locate the first component that changes state and distinguish later summary errors.
Important distinction. A stop command can be expected maintenance; it is not by itself a disk failure or proof that the volume was safely drained.
Evidence before intervention
- Administrator location, disk identifier, request time, and active sessions or rebuild operations
- Whether graceful drain, immediate stop, or maintenance workflow was intended
- Follow-up disk-offline and session migration events
- Automation, cluster, or operator record that issued the command
A controlled diagnostic path
- Stop an idle test disk and capture the normal event order.
- Repeat with a controlled active stream to verify drain or interruption policy. Keep media bytes, server identity, and unrelated publishing-point settings fixed.
- Ensure the request targets the expected server and disk UID. Use a disposable publishing point or maintenance window when the test can alter server or storage state.
Do not use repeated reconnects as the main test; a later success can belong to a new session, publishing-point generation, server owner, completed background operation, or different media path.
How to distinguish nearby outcomes
| Observed comparison | Interpretation |
|---|---|
| A known-good object succeeds through the same component | The platform path exists; concentrate on the production object, identity, metadata, or state captured above. |
| The control fails at the same first operation | Preserve server, storage, plug-in, topology, and network evidence before modifying media or publishing-point data. |
| The status changes after one deliberate adjustment | The failure point changed; the replacement status now describes the next contract to investigate. |
Correction and acceptance criteria
Correction: Correct unintended automation or targeting, and use the supported drain sequence before stopping disks that host active content.
Accept the repair only when the intended disk leaves service once, sessions behave according to policy, and no unrelated disk is affected.
Technical references
Use these Microsoft references for the formal contract and combine them with the exact server or catalog evidence from the incident: Check version-specific behavior against the Windows Media Services and SDK generation that produced the event.
- Microsoft Open Specifications: HRESULT values — defines the formal status.
- Microsoft: Windows Media Services 9 Series SDK — documents the relevant API or lifecycle.
- Microsoft: Windows Media Services SDK architecture — provides the architecture, format, or protocol context.
- Microsoft: programming the Windows Media server object model — supports the controlled verification criteria.
Looking for a different code? Search another status or error code.