| Previous | Next |
| STATUS_ADDRESS_NOT_ASSOCIATED | STATUS_CONNECTION_ACTIVE |
STATUS_CONNECTION_INVALID
There is no valid transport connection for the request
These statuses describe transport endpoint and connection state. For STATUS_CONNECTION_INVALID, they can appear below higher-level file sharing, DFS, redirector, RPC, or networking code before the error is translated to Win32 or Winsock form.
The connection reference is invalid because the connection was never created, has already been deleted, or belongs to a different state path.
For STATUS_CONNECTION_INVALID, for diagnostics, capture the endpoint address, address family, connection object, local and remote close/reset events, timeout, route, ICMP condition when available, and the higher-level component that issued the transport request.
What to inspect
- Check connection lookup keys.
- Avoid reusing connection context after teardown.
- Verify that async completion did not outlive the connection object.
References for STATUS_CONNECTION_INVALID
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Sockets error codes
- Microsoft Open Specifications: DFS client product behavior
Looking for a different code? Search another status or error code.