| Previous | Next |
| RTC_E_DUPLICATE_WATCHER | RTC_E_ROAMING_OPERATION_INTERRUPTED |
RTC_E_MALFORMED_XML
What the RTC value marks: RTC_E_MALFORMED_XML
The operational meaning of this result is tied to synchronizing profile, buddy, watcher, group, or ACL data with the server while preserving update ordering: RTC received or generated XML that cannot be parsed for the roaming or presence operation.
The machine-readable identity of this result is 0x80EE004C in the RTC interface facility 0xEE; the result identity matters because RTC uses separate facilities for API conditions, SIP final responses, and PINT service statuses.
The first useful check is to preserve document type, encoding, parse position, namespace declarations, and a redacted fixture. The result must be separated from nearby conditions because well-formedness failure occurs before list or ACL semantic validation.
Protocol and object state
| RTC area | RTC roaming synchronization |
|---|---|
| Objects to correlate | roaming event, server version, local cache, operation instance, list document and completion state |
| Condition to prove | RTC received or generated XML that cannot be parsed for the roaming or presence operation |
| Safe corrective direction | fix XML generation/transport and retry only after fetching authoritative version state |
An interrupted roaming operation has an uncertain outcome: the server may have committed data even when the client did not receive completion. A failed synchronization must be reconciled with fresh server state before replaying list mutations.
Evidence that separates the cause
- Code-specific proof: preserve document type, encoding, parse position, namespace declarations, and a redacted fixture.
- Identity and target: local/server version marker.
- State at production: last acknowledged mutation.
- Timing and ordering: fresh enumeration after failure.
Related RTC results
RTC_E_ROAMING_ENABLED | roaming is already enabled for the selected profile or data type |
|---|---|
RTC_E_ROAMING_FAILED | the server-side roaming transaction completed as a failure |
RTC_E_ROAMING_OPERATION_INTERRUPTED | a roaming operation ended without a trustworthy commit outcome |
A safe diagnostic sequence
- Start from
0x80EE004C, then find the method/event pair that first exposed it. - To verify this, preserve document type, encoding, parse position, namespace declarations, and a redacted fixture.
- Keep the analysis at the right boundary: well-formedness failure occurs before list or ACL semantic validation.
- After you fix
XMLgeneration/transport and retry only after fetching authoritative version state, repeat the smallest reproducer rather than restarting the entire application environment.
How to handle the result
The appropriate response to it is not a blanket reconnect. Instead, fix XML generation/transport and retry only after fetching authoritative version state, while preserving ownership of cleanup and any bounded retry.
Example: A truncated roaming document ends inside a buddy element.
Actions that do not address this condition
- Do not blindly replay non-idempotent list changes after a disconnect.
- Do not delete the local cache before preserving versions and pending operations.
Technical references
Looking for a different code? Search another status or error code.