Error Message: The Size of this Object Exceeds the Maximum Size Set by the Administrator (271297)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
This article was previously published under Q271297 SYMPTOMS
When you deploy a large MSI file through Windows 2000 Group Policy, the following error message is generated:
The size of this object exceeds the maximum size set by the Administrator.
CAUSE
This is a design detail of the schema used to represent the package's class information in the Active Directory database implementation. The net result is that if the number of CLSIDs plus the number of programmatic identifiers (PROGIDs) exceeds 800 or so, then the limit will be exceeded.
RESOLUTION
Remove all the entries from the Class table and the ProgId table and put them in the registry table (if they are not already duplicated there) of the MSI package.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
This error is usually caused when you use a package created by a repackaging tool rather than a fully authored package. If the package tries to advertise large numbers of CLSIDs and PROGIDs, this problem will occur.
MSI packages use tables that allow for COM advertisement. The Class table is what determines the entries for HKCR\CLSID\{-GUID-}. The ProgId table is what determines the entries for HKCR\{ProgId}.
NOTE: The ProgId table cannot be used without the Class table.
A CLSID is a globally unique identifier (GUID) used to map information about a component class. COM uses the information mapped by the CLSID to locate and create an instance the object associated with the CLISID.
A PROGID is an identifier in the form OLEServerName.ObjectName (for example, Excel.Sheet or PowerPoint.Slide) that is used by the Windows registry to uniquely identify an object.
| Modification Type: | Major | Last Reviewed: | 9/22/2003 |
|---|
| Keywords: | kbbug kberrmsg kbnofix KB271297 |
|---|
|