| Previous | Next |
| NS_E_DRM_MIGRATION_OPERATION_CANCELLED | NS_E_DRM_MALFORMED_CONTENT_HEADER |
NS_E_DRM_MIGRATION_OBJECT_IN_USE
The exact DRM condition
NS_E_DRM_MIGRATION_OBJECT_IN_USE is Windows Media DRM HRESULT 0xC00D279B. It identifies the migration object already owns an active operation. The useful scope is the controlled import/export path that packages legacy DRM state, validates the migration image and source identity, and commits eligible licenses to a supported target environment; it is not a generic statement that the media player, network or file system failed.
Identify current method, callback and completion state.
The surrounding protocol and store state
Migration is not equivalent to copying license-store files: the importer validates source state, target support and protected identities. A migration image, target-state corruption and an already imported license are independent outcomes and should not be collapsed into one generic restore failure.
Evidence worth preserving
- Protected identity: legacy V2 secure-store entry and supplied password.
- Operation state: importer plug-in availability and current operation state.
- Persistence or transport: per-license duplicate or import result.
- Security context: source and target OS versions and user SIDs.
- Correlation point: migration image identity, hash and creation time.
Related codes and the diagnostic split
| Result | Different condition |
|---|---|
NS_E_DRM_MIGRATION_OPERATION_CANCELLED | The migration workflow was canceled before completion. |
NS_E_DRM_UNABLE_TO_CREATE_MIGRATION_IMPORTER_OBJECT | The DRM runtime cannot create the migration-importer object required for this operation. |
NS_E_DRM_MIGRATION_NOT_SUPPORTED | The selected importer plug-in does not support this migration format or operation. |
Diagnostic sequence
- Prove the boundary by ensuring you can identify current method, callback and completion state.
- After you wait for or cancel the current operation before reusing the object, verify both the requested right and the final store/device state.
Correcting the producing condition
Resolve the underlying condition directly: wait for or cancel the current operation before reusing the object. A player reinstall, reboot or new license request is useful only when it changes the condition “migration object in use” and can be verified against the original evidence.
Representative case: Two threads call import on the same migration object.
Actions that do not prove a fix
- Avoid running concurrent playback or DRM operations against the source while migration owns it.
- Avoid editing migration images or combining data from different source machines.
Regression check
Repeat the operation that originally returned it. Assert the exact HRESULT at the producing API in the failing “migration object in use” fixture; then change only the relevant precondition and confirm that the corrected run completes without substituting a neighboring DRM result. After correcting it, verify the requested action and the final license-store, secure-clock, device or migration state relevant to “migration object in use”.
Code-specific operational note
The user-facing message “Migration object is already in use and cannot be called until the current operation completes.” describes the visible condition but does not identify the producing API, object instance, or protected identity by itself.
Technical references
Looking for a different code? Search another status or error code.