| Previous | Next |
| NS_E_PDA_TOO_MANY_FILES_IN_DIRECTORY | NS_E_PDA_TRANSCODE_NOT_PERMITTED |
NS_E_PROCESSINGSHOWSYNCWIZARD
Failure boundary 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
At the checkpoint, 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 generation is active. The page-specific boundary is serializing the synchronization wizard while another wizard request 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 for processingshowsyncwizard |
|---|---|
| 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 |
| Decisive observation | wizard state, initiating window/thread, selected device and pending callback |
| Generation identity | Record the same disc, device, job or Player operation generation that returned this result; a reconnect or media change creates a different test. |
| Underlying result | Keep the first device, filesystem, COM, codec, DirectShow, IMAPI or BITS result seen before the Player mapped it to this result. |
| Controlled comparison | Repeat the producing call after changing only this condition: finish or close the current wizard before opening another for the same device. |
What the comparison proves
| Observation | Interpretation |
|---|---|
| The recorded values match the boundary | The result is consistent with serializing the synchronization wizard while another wizard request is active; correct that state before changing unrelated codecs, drivers or playlists. |
| A lower layer failed before this result | Preserve that earlier HRESULT or device result because this result may be only the Player-level mapping. |
| The same call passes after one isolated change | The comparison supports the processingshowsyncwizard diagnosis rather than a broad installation failure. |
| The code changes after retesting it | The boundary was passed; diagnose the new HRESULT as the next independent stage. |
It scopes the failure to serializing the synchronization wizard while another wizard request is active.
Decision path
- Capture
0xC00D118B, it, 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.
- Create a fresh operation generation and verify that the original call advances beyond the processingshowsyncwizard boundary.
Close alternatives
| Related result | Different diagnostic boundary |
|---|---|
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.
When verifying it, do not delete and recreate the partnership before exporting the selected playlists and recording the first failing item; otherwise the state needed to distinguish queue, account and device failures is lost.
Source material
- About Device Synchronization.
- Working with Portable Devices.
- Enabling synchronization with Windows Media Player.
- Sending a file to a portable device.
Looking for a different code? Search another status or error code.