| Previous | Next |
| CRYPT_E_NOT_IN_REVOCATION_DATABASE | CRYPT_E_INVALID_PRINTABLE_STRING |
CRYPT_E_INVALID_NUMERIC_STRING
NumericString has a deliberately narrow alphabet
CRYPT_E_INVALID_NUMERIC_STRING is raised while CryptoAPI is encoding or validating an ASN.1 value declared as NumericString. This ASN.1 type is not a general text field: its permitted characters are decimal digits and the space character. A sign, decimal point, tab, line break, non-ASCII digit, or letter makes the value invalid even when the application considers it numeric text.
The error therefore identifies a schema/type mismatch rather than a failed integer conversion. Certificate names and request attributes are often represented through CERT_RDN_ATTR or CERT_NAME_VALUE; the selected dwValueType determines which ASN.1 string rules CryptoAPI applies.
What to inspect
- Log the exact Unicode code points, not only the rendered value.
- Check the RDN or object schema that selected NumericString.
- Remove locale-specific thousands separators and non-breaking spaces.
- Use a different ASN.1 string type only when the receiving schema permits it.
References
- ITU-T X.680: ASN.1 basic notation and restricted character strings
- Microsoft: certificate enrollment string types
- Microsoft: CERT_RDN_ATTR value types
Looking for a different code? Search another status or error code.