| Previous | Next |
| CS_E_NETWORK_ERROR | CS_E_SCHEMA_MISMATCH |
CS_E_ADMIN_LIMIT_EXCEEDED
The size of this object exceeds the maximum size set by the Administrator.
When Windows returns CS_E_ADMIN_LIMIT_EXCEEDED—HRESULT 2147746157, 0x8004016D, signed -2147221139—The documented description is “The size of this object exceeds the maximum size set by the Administrator.” The actionable meaning is the directory software-installation object exceeds an administrator-defined size limit. The surrounding operation is creating or updating legacy Class Store package metadata.
Precise failure point
These CS_E values describe the legacy directory-backed COM Class Store. Public documentation is limited; the exact owner is the component performing automatic installation or directory lookup, so traces must identify that component rather than assigning the HRESULT to every modern COM activation path.
- Associate this result with one exact operation in automatic class installation or lookup through COM Class Store policy and directory-backed software-installation objects.
- Confirm that this result came from creating or updating legacy Class Store package metadata, rather than from cleanup or a wrapper that ran afterward.
Diagnostic evidence
A useful incident records the requested CLSID or ProgID, directory object DN, package identifier, version, deployment path, domain controller, schema version, policy state, bind result, and object size.
- measure object and attribute sizes before submission.
- Identify the attributes responsible for growth and duplicate values.
- Record the applicable directory limit and whether the operation partially changed other objects.
Resolution path
- Identify the exact object, method, and lifecycle phase involved in creating or updating legacy Class Store package metadata.
Distinct causes
- It can result when large embedded metadata or excessive class mappings make the object too large.
- It can result when an update appends duplicate entries instead of replacing them.
- It can result when directory administrative limits are lower in the target environment.
Retry policy
Correction. remove redundant metadata, split publication where supported, or adjust the documented administrative limit after capacity review. Retry condition. Retry only after reducing the object or intentionally changing the limit; chunking an atomic object arbitrarily can corrupt semantics. Before repeating the operation, determine whether directory metadata, package staging, or a local installation changed before failure and avoid deleting a directory object whose ownership is not established.
Practical scenario
A package publication repeats thousands of CLSID mappings on every update; deduplicating the multi-valued attribute brings the object under the limit.
Difference from related HRESULTs
E_OUTOFMEMORY is a runtime allocation failure; it is an explicit directory policy or object-size boundary.
Developer and administrator guidance
Involve the Active Directory or software-deployment owner, verify policy and domain-controller evidence, and use the management system that created the package or class-store object.
References
Looking for a different code? Search another status or error code.