| Previous | Next |
| STATUS_REQUEST_OUT_OF_SEQUENCE | STATUS_ELEVATION_REQUIRED |
STATUS_IMPLEMENTATION_LIMIT
Find the concrete capacity that was exceeded and compare it with the requested value
STATUS_IMPLEMENTATION_LIMIT means an operation crossed a limit imposed by the implementation. It is more specific than a temporary resource shortage: the request shape itself is outside the supported capacity. The limit can depend on a device, provider, algorithm, or object created with a particular configuration.
The Network Direct Kernel Provider Interface gives a concrete example. NdkInitializeFastRegisterMr returns STATUS_IMPLEMENTATION_LIMIT when an adapter does not support the requested AdapterPageCount for a fast-register memory region. The useful diagnostic is the requested page count and the adapter/provider capability, not system free memory. Other users of the generic status can define different implementation limits, so the returning API remains the authority.
Log the quantity being limited, its unit, the provider or device identity, and any advertised maximum. Check arithmetic and unit conversion before concluding the limit is genuinely exceeded; pages, bytes, descriptors, and entries are easy to mix. If work can be split without changing semantics, partition it according to the documented maximum. Otherwise surface the capability failure. Immediate retry with the same value cannot change a fixed implementation limit.
What to inspect
- Identify the exact bounded quantity and unit at the returning interface.
- Compare requested and advertised maximum values and verify unit conversions.
- Split the operation only when the interface guarantees equivalent semantics across smaller requests.
References
- Microsoft: NDK_FN_INITIALIZE_FAST_REGISTER_MR
- Microsoft: NDKPI overview
- Microsoft: Using NTSTATUS values
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.