| Previous | Next |
| E_IMAPI_RECORDER_MEDIA_SPEED_MISMATCH | E_IMAPI_RECORDER_CLIENT_NAME_IS_NOT_VALID |
E_IMAPI_RECORDER_LOCKED
IMAPI exposes explicit recorder locking through AcquireExclusiveAccess. Each acquisition increments a lock count, and ReleaseExclusiveAccess decrements it; the device is available to other clients only after the count reaches zero. Microsoft recommends querying ExclusiveAccessOwner when this HRESULT occurs.
Identify the lock owner and balance acquisition/release calls
- Read
ExclusiveAccessOwnerat the time of failure and log it. - Audit every successful
AcquireExclusiveAccesspath for a corresponding release, including exceptions and cancellations. - Do not assume another process owns the lock; nested acquisitions by the same application can leave a nonzero lock count.
This is distinct from E_IMAPI_ERASE_RECORDER_IN_USE, which concerns changing the recorder property while the erase object uses it. Here the recorder device itself is exclusively locked. Killing unrelated applications or changing the disc is not a precise fix until the reported owner and lock lifecycle are known.
AcquireExclusiveAccess · ExclusiveAccessOwner · ReleaseExclusiveAccess
Looking for a different code? Search another status or error code.
