| Previous | Next |
| NS_E_PDA_PARTNERSHIPNOTEXIST | NS_E_PDA_NO_TRANSCODE_OF_DRM |
NS_E_PDA_CANNOT_CREATE_ADDITIONAL_SYNC_RELATIONSHIP
Where this result occurs in the Player workflow
NS_E_PDA_CANNOT_CREATE_ADDITIONAL_SYNC_RELATIONSHIP (0xC00D1185) marks enforcing the device or Player limit on automatic-sync partnerships. Preserve that boundary even when the visible Player message is broader than the producing operation.
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 enforcing the device or Player limit on automatic-sync partnerships.
A working manual file copy does not prove that the Player’s partnership, playlist snapshot and synchronization queue are valid. A representative way to reach this result is that all supported partnership slots are already assigned.
State snapshot
| Evidence | Why it matters for cannot create additional sync relationship |
|---|---|
| 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 | existing partnership count, device identity and relationship slots |
| 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: remove an obsolete partnership or use manual transfer for the additional device. |
How to interpret the next test
| Observation | Interpretation |
|---|---|
| The recorded values match the boundary | The result is consistent with enforcing the device or Player limit on automatic-sync partnerships; 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 it may be only the Player-level mapping. |
| The same call passes after one isolated change | The comparison supports the cannot create additional sync relationship 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 enforcing the device or Player limit on automatic-sync partnerships.
Controlled diagnostic sequence
- Capture
0xC00D1185, it, the exact Player/API operation and the first timestamp at which it appears. - Save existing partnership count, device identity and relationship slots; 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: remove an obsolete partnership or use manual transfer for the additional device.
- Create a fresh operation generation and verify that the original call advances beyond the cannot create additional sync relationship boundary.
Nearby codes with different owners
| Related result | Different diagnostic boundary |
|---|---|
NS_E_PDA_PARTNERSHIPNOTEXIST | locating the Player-device partnership required for automatic synchronization |
NS_E_PROCESSINGSHOWSYNCWIZARD | serializing the synchronization wizard while another wizard request is active |
NS_E_PDA_CANNOT_SYNC_FROM_LOCATION | resolving a source location that the sync engine cannot materialize or access |
Focused correction
For this occurrence, remove an obsolete partnership or use manual transfer for the additional device. Recreate only the object that produced it and repeat the original operation against the same controlled input.
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.
Technical references
- 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.