What does HRESULT 0xC00D1185 (NS_E_PDA_CANNOT_CREATE_ADDITIONAL_SYNC_RELATIONSHIP) mean?

 
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. Keep this HRESULT attached to the producing operation even when the Player shows a broader message.

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. A representative way to reach this result is that all supported partnership slots are already assigned.

State snapshot

EvidenceWhy it matters for cannot create additional sync relationship
Producing object and operationdevice 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 observationexisting partnership count, device identity and relationship slots
Controlled comparisonRepeat the producing call after changing only this condition: remove an obsolete partnership or use manual transfer for the additional device.

Controlled diagnostic sequence

  1. Capture 0xC00D1185, the exact Player/API operation and the first timestamp at which it appears.
  2. 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.
  3. 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.
  4. 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.

Nearby codes with different owners

Related resultDifferent condition
NS_E_PDA_PARTNERSHIPNOTEXISTlocating the Player-device partnership required for automatic synchronization
NS_E_PROCESSINGSHOWSYNCWIZARDserializing the synchronization wizard while another wizard request is active
NS_E_PDA_CANNOT_SYNC_FROM_LOCATIONresolving 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.

Discriminating evidence: Enumerate the device's existing synchronization partnerships and identify the host relationship being added. This code is a relationship-capacity or ownership boundary, not a per-file synchronization failure and not a general device-discovery problem.

Technical references


Looking for a different code? Search another status or error code.