| Previous | Next |
| STATUS_SYSTEM_PROCESS_TERMINATED | STATUS_NO_BROWSER_SERVERS_FOUND |
STATUS_DATA_NOT_ACCEPTED
The transport delivered an indication, but the TDI client declined the data
STATUS_DATA_NOT_ACCEPTED has a concrete meaning in the legacy TDI receive callback model. Microsoft documents ClientEventReceive as the handler for a TSDU received on an established endpoint-to-endpoint connection, and explicitly allows the client to return this status when it is not interested in the indicated TSDU.
That distinction matters during packet-loss investigations. The network transport can have received the data successfully and invoked the client before the client rejects the indication. The callback contract also accounts for how much indicated data the client accepted and whether more data is available. Capture the indicated byte count, accepted byte count, flags, and callback return value before blaming the remote peer.
Do not translate this status into a generic connection reset. Review the client's receive-state machine and any path that temporarily disables or changes the receive handler. If the design expects data to be consumed later, verify whether it issues the documented follow-up receive operation instead of repeatedly rejecting indications and losing application progress.
What to inspect
- The TDI receive callback, TSDU type, indication flags, bytes indicated, and bytes accepted by the client.
- The client state that caused it to reject the indication and whether that state was expected for the connection.
- Any follow-up receive request and the exact transition between callback-based indication and queued receive processing.
References
Looking for a different code? Search another status or error code.