| Previous | Next |
| VFW_E_ADVISE_ALREADY_SET | TPC_E_QUEUE_FULL |
TPC_E_OUT_OF_ORDER_CALL
Meaning
Windows documents TPC_E_OUT_OF_ORDER_CALL as “TabletPC inking error code. API calls were made in an incorrect order”. In practical terms, it is returned when Tablet PC APIs are invoked in a sequence that violates the component lifecycle or configuration contract.
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 relevant condition is that Tablet PC APIs are invoked in a sequence that violates the component lifecycle or configuration contract.
Diagnostic sequence
- Confirm that the observed path matches this condition: Tablet PC APIs are invoked in a sequence that violates the component lifecycle or configuration contract.
Likely causes
- Possible cause 1: configuration is changed after the RealTimeStylus object is enabled.
- Possible cause 2: packet or plug-in methods run before required initialization.
- Possible cause 3: shutdown calls occur before queued data and callbacks are drained.
Evidence to collect
- Capture 1: ordered call trace with thread IDs and object instance.
- Capture 2: enabled, connected and initialized state before every call.
- Capture 3: plug-in insertion and removal sequence.
Correct handling and retry
- Corrective action 1: model the component lifecycle explicitly and reject invalid transitions locally.
- Corrective action 2: perform configuration before enabling input.
- Corrective action 3: serialize teardown with callback and queue completion.
Retry guidance. Retry from a valid earlier lifecycle state; repeating only the final call preserves the ordering violation. When retrying, avoid replay stale strokes, reorder stylus packets or reuse an invalid recognizer context.
Practical scenario
An application calls a configuration method after enabling RealTimeStylus; disabling, configuring and re-enabling in the documented order removes it.
Developer and operational guidance
Difference from nearby HRESULTs
TPC_E_INVALID_CONFIGURATION identifies a conflicting configuration choice, while it identifies when otherwise meaningful calls occur in the wrong sequence.
Official Microsoft references
Looking for a different code? Search another status or error code.