| Previous | Next |
| ERROR_LOGON_NOT_GRANTED | ERROR_SECRET_TOO_LONG |
ERROR_TOO_MANY_SECRETS
LSA secret-object creation reached the system’s secret-count limit
LSA secret objects are policy-database objects managed through methods such as LsarCreateSecret, LsarOpenSecret, LsarSetSecret and LsarQuerySecret. ERROR_TOO_MANY_SECRETS refers to that secret-object facility; it does not mean a user has too many passwords or that an application has supplied excessive random data in one request.
Inventory the component creating secrets and the secret naming pattern before deleting anything. Services and trust-related features can use LSA-protected private data, so an arbitrary cleanup of policy secrets can break authentication or service startup. If a custom application owns a large number of secrets, confirm its lifecycle deletes obsolete objects and reuses a stable secret name when it is storing successive versions of one value.
What to inspect
- Identify the LSA/Policy API or component creating secret objects.
- Review object lifecycle and naming for application-owned secrets.
- Do not delete unknown LSA secrets merely to free a slot; determine ownership and purpose first.
References
Looking for a different code? Search another status or error code.