What does HRESULT 0x80EE003C (RTC_E_PROFILE_INVALID_SESSION_PARTY) mean?

RTC_E_PROFILE_INVALID_SESSION_PARTY

What RTC_E_PROFILE_INVALID_SESSION_PARTY means in RTC

This result is useful only when preserved with its producing phase; in creating or enabling an XML profile that defines user identity, servers, transports, authentication, and supported session types, it denotes the profile contains an invalid session party value or combination.

The machine-readable identity of this result is 0x80EE003C 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 record the exact value, XML element, allowed enumeration, and related transport/role/session fields. The result must be separated from nearby conditions because the field is present, so adding another copy will not fix semantic validation.

Protocol and object state

How to prove the condition

1. Collect enough evidence to record the exact value, XML element, allowed enumeration, and related transport/role/session fields.
2. Test the competing explanation explicitly, because the field is present, so adding another copy will not fix semantic validation.
3. Apply the targeted fix — replace it with a documented value consistent with the rest of the profile and revalidate from source — and validate both protocol completion and object cleanup.

Minimum incident record

Do not wait for a generic failure notification to log it; preserve the API call or event producing it together with the RTC object and transaction state visible at that moment.

• Code-specific proof: record the exact value, XML element, allowed enumeration, and related transport/role/session fields.
• Owning object: redacted profile XML path/version.
• Wire evidence: user URI and profile key hash.
• Lifecycle state: server role/address/transport.

Actions that do not address this condition

• Do not log passwords or provisioning secrets from profile XML.
• Do not insert placeholder values solely to pass schema validation.

Correct application response

The owning RTC component should replace it with a documented value consistent with the rest of the profile and revalidate from source; it should also settle or cancel its previous operation before callers begin a replacement.

Example: An automated profile feed emits an unsupported session party value and CreateProfile rejects the document.

Nearby failure modes

Technical references

• IRTCClientProvisioning::CreateProfile.
• IRTCProfile server fields.
• Microsoft RTC return constants.
• SIP and TEL URLs.