| Previous | Next |
| SCARD_W_CACHE_ITEM_STALE | COMADMIN_E_OBJECTERRORS |
SCARD_W_CACHE_ITEM_TOO_BIG
The cache has a per-item size boundary
SCARD_W_CACHE_ITEM_TOO_BIG means that a new smart-card cache item exceeds the maximum size allowed for one entry. The result is about the Windows Smart Card Resource Manager cache, not necessarily about reader memory, card storage, or the total amount of cached smart-card data. A large certificate chain, serialized profile, or application blob may be valid data but still be inappropriate for this cache interface.
Do not work around the limit by silently truncating security-sensitive data. A truncated certificate, public-key object, or encoded profile can later fail validation in a less obvious way. Store only the small value needed for the cache key, or use the provider's normal persistent storage path when the object is genuinely large.
Design and diagnosis
- Measure the serialized value before
SCardWriteCacheand log only its size and type, not secret contents. - Separate metadata suitable for caching from full certificates, file images, or large provider records.
- Confirm that the lookup name and card identifier identify the intended card before changing the cache design.
References
Looking for a different code? Search another status or error code.