| Previous | Next |
| STATUS_SECRET_TOO_LONG | STATUS_FULLSCREEN_MODE |
STATUS_INTERNAL_DB_ERROR
The LSA policy database is internally inconsistent
This status comes from the Local Security Authority database path and should not be reduced to a failed password check. LSA Policy objects, trusted-domain information, account rights and private-data objects depend on security-policy database state. An internal inconsistency can therefore affect several security operations.
Preserve the exact LSA API or RPC operation and object type that first returns the error. Correlate it with LSASS, storage and system events before attempting repairs. Repeatedly creating or deleting policy objects can make the diagnostic timeline harder to interpret.
What to inspect
- Record the LSA operation, target object type, name or SID, and desired access.
- Collect LSASS and System event data plus storage-health evidence around the first failure.
- Avoid bulk policy edits until the scope and persistence of the inconsistency are known.
References
- Microsoft: LsaOpenPolicy
- Microsoft Open Specifications: LsarOpenPolicy2
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.