| Previous | Next |
| NS_E_PDA_TOO_MANY_FILES_IN_DIRECTORY | NS_E_PDA_TRANSCODE_NOT_PERMITTED |
NS_E_PROCESSINGSHOWSYNCWIZARD
Failure point and ownership
NS_E_PROCESSINGSHOWSYNCWIZARD with value 0xC00D118B records serializing the synchronization wizard while another wizard request is active. The producing call and its state are more diagnostic than a later aggregate Player failure.
Underlying mechanism
Automatic synchronization uses a Player-to-device partnership, a snapshot of selected playlists and a queue of per-item copy, delete or retrieval operations. The sync engine owns its own running state and can reject changes while a previous operation is active.
A working manual file copy does not prove that the Player’s partnership, playlist snapshot and synchronization queue are valid. The condition can be reproduced when two UI commands attempt to configure sync at the same time.
Trace fields worth keeping
| Evidence | Why it matters |
|---|---|
| Producing object and operation | device and partnership IDs, sync generation and state, selected playlist identity/version, queued item ID and direction, subscription account, target storage, progress callback and first item-specific HRESULT |
| Key observation | wizard state, initiating window/thread, selected device and pending callback |
| Controlled comparison | Repeat the producing call after changing only this condition: finish or close the current wizard before opening another for the same device. |
Decision path
- Capture
0xC00D118B, the exact Player/API operation and the first timestamp at which it appears. - Save wizard state, initiating window/thread, selected device and pending callback; do this before ejecting media, reconnecting a device, canceling a job or rebuilding the Player object.
- Correlate the result with device and partnership IDs, sync generation and state, selected playlist identity/version, queued item ID and direction, subscription account, target storage, progress callback and first item-specific HRESULT.
- Reproduce once with the original source and destination, then apply only this change: finish or close the current wizard before opening another for the same device.
- Start a fresh operation and verify that the original call advances without returning
NS_E_PROCESSINGSHOWSYNCWIZARD.
Close alternatives
| Related result | Different condition |
|---|---|
NS_E_PDA_CANNOT_CREATE_ADDITIONAL_SYNC_RELATIONSHIP | enforcing the device or Player limit on automatic-sync partnerships |
NS_E_PDA_PARTNERSHIPNOTEXIST | locating the Player-device partnership required for automatic synchronization |
NS_E_PDA_CANNOT_SYNC_FROM_LOCATION | resolving a source location that the sync engine cannot materialize or access |
Safe correction
Correct this boundary by making sure you finish or close the current wizard before opening another for the same device. Then reacquire the interface or media state that produced it and repeat that call.
Discriminating evidence: Record the synchronization wizard phase and whether the UI is still processing the device or selection state. This code represents wizard work in progress; target-device capacity exhaustion is a later resource constraint and should be verified with free-space data instead.
Source material
Looking for a different code? Search another status or error code.