| Previous | Next |
| COMADMIN_E_APPLID_MATCHES_CLSID | COMADMIN_E_START_APP_NEEDS_COMPONENTS |
COMADMIN_E_ROLE_DOES_NOT_EXIST
COM+ identity, role, and administration security: exact meaning of COMADMIN_E_ROLE_DOES_NOT_EXIST
A component, interface, or method references a role that is absent from the application. Role-assignment validation follows the secured item to the parent application Roles collection and finds no matching role.
Windows describes this condition as “A role assigned to a component, interface, or method did not exist in the application”.
Evidence to collect before repair
- Record AppID, secured component/interface/method key, and assigned role name.
- Preserve current application Roles collection with role keys; it anchors the failure to the real administration object.
- Evidence should include package or script order for role creation and role assignment, captured before a repair changes state.
- Collect recent role deletion, rename, or application reinstall events when diagnosing this result; without it the symbolic HRESULT is underdetermined.
Where the result occurs
This result concerns a concrete COM+ identity, role, credential, or call-authentication contract; successful interactive access does not prove that the COMAdmin or application identity can perform the operation. In the specific case of it, record application ID, secured item, assigned role key/name, inheritance level, and recent role renames or package imports.
Diagnostic sequence
- To isolate this result, populate Roles and the relevant RolesForComponent/Interface/Method collection.
- resolve the missing role by stable application scope.
- create the intended role before applying assignments or remove the stale assignment.
- The next diagnostic action is to save the role and assignment in dependency order.
- To isolate it, repopulate and test role-based access with an authorized and unauthorized identity.
Retry and recovery
Create the intended role first or remove the stale assignment, then save and test access checks.
Practical administration scenario
A package imports component security assignments but omits the application role they reference.
Difference from nearby COMADMIN results
COMADMIN_E_ROLEEXISTS concerns duplicate role creation; this value identifies a dangling role reference.
Official Microsoft references
Looking for a different code? Search another status or error code.