| Previous | Next |
| RTC_E_PROFILE_INVALID_SERVER_AUTHMETHOD | RTC_E_PROFILE_MULTIPLE_REGISTRARS |
RTC_E_PROFILE_INVALID_SERVER_ROLE
What the RTC value marks: RTC_E_PROFILE_INVALID_SERVER_ROLE
Read this result as an RTC state-machine result: at this point in creating or enabling an XML profile that defines user identity, servers, transports, authentication, and supported session types, the profile contains an invalid server role value or combination.
Log this result as 0x80EE0039 in the RTC interface facility 0xEE, not only as a signed decimal; the facility distinguishes local RTC validation from a response status mapped by the stack.
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.
A safe diagnostic sequence
- Start from
0x80EE0039and this result, then find the method/event pair that first exposed it. - To verify this, record the exact value,
XMLelement, allowed enumeration, and related transport/role/session fields. - Keep the analysis at the right boundary: the field is present, so adding another copy will not fix semantic validation.
- After you replace it with a documented value consistent with the rest of the profile and revalidate from source, repeat the smallest reproducer rather than restarting the entire application environment.
Evidence that separates the cause
- Code-specific proof: record the exact value,
XMLelement, allowed enumeration, and related transport/role/session fields. - Identity and target: server role/address/transport.
- State at production: authentication method.
- Timing and ordering: session type and party attributes.
Protocol and object state
| RTC area | RTC provisioning profile validation |
|---|---|
| Objects to correlate | profile XML, provision/user/server/session elements, registrar and proxy roles, transport and authentication method |
| Condition to prove | the profile contains an invalid server role value or combination |
| Safe corrective direction | replace it with a documented value consistent with the rest of the profile and revalidate from source |
Related RTC results
RTC_E_PROFILE_MULTIPLE_REGISTRARS | the profile defines more than one registrar server where RTC requires one unambiguous registrar |
|---|---|
RTC_E_NO_TRANSPORT | a server is specified in the profile without a transport protocol RTC can use |
RTC_E_NO_REALM | the profile or authentication context lacks a realm required to select credentials |
How to handle the result
Resolve it at its producing layer: replace it with a documented value consistent with the rest of the profile and revalidate from source; after it, a separate UI or watchdog retry must wait until that layer reports a final state.
Example: An automated profile feed emits an unsupported server role value and CreateProfile rejects the document.
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.
Technical references
Looking for a different code? Search another status or error code.