| Previous | Next |
| RTC_E_PROFILE_SERVER_UNAUTHORIZED | RTC_E_POLICY_NOT_ALLOW |
RTC_E_DUPLICATE_REALM
What the RTC value marks: RTC_E_DUPLICATE_REALM
When RTC returns this result, the relevant contract is applying client policy, authorized domains, transport requirements, and negotiated media security levels, and it says that more than one enabled profile defines the same authentication realm in a conflicting way.
This result carries 0x80EE0043 in the RTC interface facility 0xEE; store the result value at the first RTC callback or method boundary, before retry logic replaces it with a broader timeout or connection message.
Start the result investigation by having the trace enumerate enabled profiles, realm strings after normalization, credential owners, and server roles; do not skip the distinction that duplicate realm is profile-selection ambiguity, not a repeated challenge from one server.
Protocol and object state
| RTC area | RTC policy and media-security |
|---|---|
| Objects to correlate | enabled profile, policy source, authorized domain, media type, local and remote security level |
| Condition to prove | more than one enabled profile defines the same authentication realm in a conflicting way |
| Safe corrective direction | consolidate or disambiguate profiles so one credential policy owns the realm |
Interpreting this result requires both of these facts: Policy refusal is distinct from transport failure: the requested operation may be technically possible but prohibited for the current profile or platform; also, the result branch assumes that Media security must be compatible for each participating endpoint and should not be silently downgraded after negotiation begins.
Evidence that separates the cause
- Code-specific proof: enumerate enabled profiles, realm strings after normalization, credential owners, and server roles.
- Identity and target: peer capability result.
- State at production: transport selected for signaling.
- Timing and ordering: policy name/source and effective value.
Related RTC results
RTC_E_SECURITY_LEVEL_NOT_COMPATIBLE | local and remote media security requirements have no compatible negotiated level |
|---|---|
RTC_E_SECURITY_LEVEL_ALREADY_SET | the media security level has already been fixed for this media type and cannot be changed in the current session state |
RTC_E_UDP_NOT_SUPPORTED | the requested feature or profile combination is incompatible with at least one server using UDP transport |
A safe diagnostic sequence
- Start from
0x80EE0043, then find the method/event pair that first exposed it. - To verify this, enumerate enabled profiles, realm strings after normalization, credential owners, and server roles.
- Keep the analysis at the right boundary: duplicate realm is profile-selection ambiguity, not a repeated challenge from one server.
- After you consolidate or disambiguate profiles so one credential policy owns the realm, repeat the smallest reproducer rather than restarting the entire application environment.
How to handle the result
Recovery should be narrow: consolidate or disambiguate profiles so one credential policy owns the realm; while handling this result, do not let a higher layer simultaneously recreate the same session, registration, listener, or profile.
Example: Personal and corporate profiles both claim the same realm with different credentials.
Actions that do not address this condition
- Do not bypass policy by editing generated profile XML in memory.
- Do not downgrade security without an explicit product policy and user-visible result.
Technical references
Looking for a different code? Search another status or error code.