| Previous | Next |
| ERROR_GRACEFUL_DISCONNECT | ERROR_ADDRESS_NOT_ASSOCIATED |
ERROR_ADDRESS_ALREADY_ASSOCIATED
ERROR_ADDRESS_ALREADY_ASSOCIATED describes a transport endpoint whose address association has already been established. Conceptually this is a local endpoint-state problem: code is trying to perform an address-association step on an endpoint that is no longer unbound.
Compare it with Winsock bind errors
For ordinary user-mode Winsock sockets, bind more commonly reports WSAEADDRINUSE when the requested local address/port conflicts with another socket. This Win32 code is phrased around the endpoint already owning an address, so tracing the endpoint object's lifecycle is more useful than assuming another process owns the port.
What to verify
- Whether initialization or reconnect logic calls the association/bind stage twice.
- Object reuse after a partially successful setup path.
- Concurrent threads racing to initialize the same endpoint.
- The local address before and after the first successful association.
Do not “fix” the condition by enabling address reuse without proving that the failure is an address conflict. SO_REUSEADDR changes bind behavior; it does not repair an application state machine that binds the same endpoint twice.
Microsoft: system error codes 1000-1299 · Microsoft: bind · POSIX: bind
Looking for a different code? Search another status or error code.