| Previous | Next |
| VFW_E_CORRUPT_GRAPH_FILE | VFW_E_ADVISE_ALREADY_SET |
TPC_E_INVALID_RIGHTS
Meaning and numerical form
TPC_E_INVALID_RIGHTS is HRESULT 2147746358 (0x80040236; signed -2147220938). AllStat records its meaning as “TabletPC inking error code. User does not have the necessary rights to read recognizer information”. In practical terms, it is returned when the current user lacks the rights needed to read Tablet PC recognizer information.
The severity bit in 0x80040236 is set, so this result is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 566 (0x0236). Those fields classify the value but do not identify the component instance, call, object or input that produced it.
Where the failure belongs
This result belongs to Tablet PC ink, stylus and recognition. Tablet PC APIs span device enumeration, RealTimeStylus packet queues, ink-object lifetime and recognizer-specific capabilities. The numerical facility does not identify which Tablet PC layer produced the result. The decisive condition is this: the current user lacks the rights needed to read Tablet PC recognizer information. Record the first native producer instead of relying only on a framework exception translated several layers later.
Do not infer from this result alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because it can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.
Evidence to collect
A useful diagnostic record for this result includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing it, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.
- Capture 1 for this HRESULT: effective user and integrity level.
- Capture 2 for this HRESULT: recognizer registration location and ACL.
- Capture 3 for this HRESULT: access-check failure and package installation ownership.
Telemetry for this HRESULT should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. This makes repeated incidents comparable without exposing ink content, packet data, account details or recognizer input.
Likely causes
- Possible cause 1 for this HRESULT: recognizer metadata is protected by permissions the process token does not have.
- Possible cause 2 for this HRESULT: installation created incorrect ACLs.
- Possible cause 3 for this HRESULT: an application service accesses a user-scoped recognizer from another identity.
Diagnostic sequence
- Capture it at the first native return and identify the exact object and method.
- Confirm that the observed path matches this condition: the current user lacks the rights needed to read Tablet PC recognizer information.
- compare the live state with the method contract before changing configuration.
- collect the code-specific evidence listed above and preserve any more specific preceding error.
- change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
- Add a regression check that distinguishes it from the related outcomes described below.
Practical scenario
A service account reads recognizer metadata installed only for an interactive user; moving recognition to the user process resolves it. The result scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.
Correction and retry boundary
- Corrective action 1 for this HRESULT: repair permissions through the recognizer installer or supported package repair.
- Corrective action 2 for this HRESULT: run recognition in the intended user context.
- Corrective action 3 for this HRESULT: avoid broad elevation when only specific metadata access needs correction.
Retry guidance for this HRESULT. Retry after identity or ACL correction; repeated access under the same token is not useful. A retry must avoid this hazard: replay stale strokes, reorder stylus packets or reuse an invalid recognizer context. It must also preserve the evidence needed to locate the original producer of it.
Difference from nearby HRESULTs
TPC_E_RECOGNIZER_NOT_REGISTERED means no recognizer can be found, whereas it means recognizer information exists but is inaccessible. Keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.
Developer and operational guidance
Code handling it should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for this HRESULT should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.
Operational repair for this HRESULT should use supported device, Tablet PC component, recognizer and application lifecycle paths. Avoid unsupported configuration edits or component replacement unless evidence identifies that layer. Retain the original trace and a post-fix trace so the result can be attributed and the change reversed.
Official Microsoft references
Looking for a different code? Search another status or error code.