| Previous | Next |
| STATUS_VOLMGR_NO_REGISTERED_USERS | STATUS_VOLMGR_NOTIFICATION_RESET |
STATUS_VOLMGR_NO_SUCH_USER
The client is trying to unregister an unknown notification identity
STATUS_VOLMGR_NO_SUCH_USER means the notification user named by the unregister request is not present. The failure occurs in notification bookkeeping; it does not describe a missing Windows account or a storage-security principal.
This commonly indicates a lifecycle mismatch between client state and Volume Manager state. The registration may already have been removed, a reset may have invalidated it, or code may be using an identifier from an earlier connection.
Compare the user identifier sent to the unregister operation with the identifier returned or stored during the current registration. Make unregistration idempotent in the client workflow where possible, and do not reuse an old notification identity after reconnecting.
What to inspect
- Log the notification-user identifier at registration and at every unregister attempt.
- Check whether reset or shutdown logic already removed the user before a second cleanup path ran.
- Keep notification identities scoped to one initialized client session rather than persisting them across service restarts.
References
- Microsoft VOLMGR definition of STATUS_VOLMGR_NO_SUCH_USER.
- MS-DMRP notification callback lifetime across initialize and uninitialize.
- MS-DMRP terminology for management protocol participants.
Looking for a different code? Search another status or error code.