| Previous | Next |
| STATUS_SEMAPHORE_LIMIT_EXCEEDED | STATUS_SECTION_NOT_IMAGE |
STATUS_PORT_ALREADY_SET
The target object already has its one-time port association
This NTSTATUS is intentionally broader than debugger attachment. The documented cases include setting a process DebugPort or ExceptionPort, assigning a completion port to a file, and associating a completion port with an ALPC port. In each case an association already exists and the new set operation is rejected.
The first diagnostic step is to identify the object type and information class used by the native call. A completion-port association on a file is not repaired with debugger settings, and a process DebugPort conflict is unrelated to I/O completion. Capture the existing association where the API allows querying it and find the earlier initialization path that set it.
What to inspect
- Record the target object type and native information class.
- Locate the first successful port-association operation for that object.
- Do not clear or replace an existing association without understanding the owner and pending work.
References
- Microsoft Open Specifications: NTSTATUS values
- System Informer PHNT: process and thread Native API
- System Informer PHNT: native debugging API
Looking for a different code? Search another status or error code.