What does HRESULT 0x80093002 (OSS_NEGATIVE_UINTEGER) mean?

 
Previous Next
OSS_MORE_BUF OSS_PDU_RANGE

OSS_NEGATIVE_UINTEGER

OSS_NEGATIVE_UINTEGER (0x80093002) is an OSS ASN.1 runtime result for negative value in a nonnegative INTEGER domain. A value represented by the generated API as an unsigned or nonnegative ASN.1 INTEGER is negative when the encoder evaluates it. Because the ASN.1 lower bound and generated member type is central to this condition, Microsoft’s HRESULT range and the OSS Nokalva return-code documentation should be read together. Start the investigation by recording the value before conversion or sign extension, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.

What the return code narrows down

At the negative value in a nonnegative INTEGER domain boundary, capture the first OSS function returning the value and note whether the operation was encode, decode, copy, compare, constraint validation, or trace setup. Preserve the selected PDU, encoding rules, and the source field and any sentinel convention; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.

Test one variable at a time

  1. encode the smallest legal boundary value
  2. trace signed-to-unsigned casts at the producer
  3. Compare the value with the schema used to generate this build

Build a useful capture

  • the ASN.1 lower bound and generated member type
  • the value before conversion or sign extension
  • the source field and any sentinel convention

Neighboring statuses: the result

This is a value-domain failure, not malformed BER received from the network and not an integer too large for an implementation limit.

Instrumentation

Where the ASN.1 lower bound and generated member type can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use the value before conversion or sign extension together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.

Verify the repair: the result

Correct the producer or schema mapping and retain negative and zero boundary tests.

Technical references


Looking for a different code? Search another status or error code.