| Previous | Next |
| VFW_E_NOT_ALLOWED_TO_SAVE | VFW_E_TIME_ALREADY_PASSED |
TPC_E_INVALID_PACKET_DESCRIPTION
Meaning
Windows documents TPC_E_INVALID_PACKET_DESCRIPTION as “TabletPC inking error code. Invalid packet description”. In practical terms, it is returned when a RealTimeStylus packet description is structurally invalid or inconsistent with packet data.
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 a RealTimeStylus packet description is structurally invalid or inconsistent with packet data.
Evidence to collect
- Capture 1: desired packet-property GUIDs in order.
- Capture 2: packet stride, value count and tablet context.
- Capture 3: the effective packet description returned after device negotiation.
Likely causes
- Possible cause 1: property count does not match the supplied GUID array.
- Possible cause 2: packet values use an order different from the declared properties.
- Possible cause 3: duplicate or unsupported packet-property definitions violate the API contract.
Diagnostic sequence
- Confirm that the observed path matches this condition: a RealTimeStylus packet description is structurally invalid or inconsistent with packet data.
Practical scenario
A plug-in assumes pressure is the third packet field even though the device omitted it; reading the negotiated description avoids it.
Correct handling and retry
- Corrective action 1: build packet descriptions from validated property arrays.
- Corrective action 2: read the effective device-supported description instead of assuming every requested property was accepted.
- Corrective action 3: version plug-in expectations when adding packet fields.
Retry guidance. Retry after correcting the description and reconnecting if the API requires configuration before enablement. When retrying, avoid replay stale strokes, reorder stylus packets or reuse an invalid recognizer context.
Difference from nearby HRESULTs
TPC_E_UNKNOWN_PROPERTY concerns an unrecognized property GUID, while it concerns the structure or ordering of the complete packet schema.
Developer and operational guidance
Official Microsoft references
Looking for a different code? Search another status or error code.