| Previous | Next |
| RPC_NT_FP_UNDERFLOW | RPC_NT_CALL_IN_PROGRESS |
RPC_NT_FP_OVERFLOW
Floating-point overflow in server-side RPC code
RPC_NT_FP_OVERFLOW belongs to the Windows RPC runtime NTSTATUS facility. MS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.
This status means that a floating-point operation overflowed in the RPC server during remote procedure execution. The call was dispatched; the failure is in server computation, not in endpoint discovery.
Investigate values that become too large after scaling or aggregation. If the same call works with smaller parameters, the RPC status is only the transport-visible form of a server numeric-range bug.
What to check
- Log numeric ranges at the server boundary, especially array sizes, scale factors, and accumulated totals.
- Check whether the generated IDL types match the server implementation types.
- Use server-side dump or tracing to identify the failing operation; client retry cannot fix deterministic overflow.
References
- Microsoft Open Specifications: MS-RPCE overview
- The Open Group: DCE 1.1 RPC introduction
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.