EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB33189: "Error Code=0x80040310: Model size exceeds maximum" error appears when training or using a predictive metric in MicroStrategy Developer 9.x-10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


SYMPTOM
A user tries to use a predictive metric in Strategy Developer 9.x-10.x. The metric may have been created in Strategy by using a training metric and report, or the metric may be based on Predictive Modeling Markup Language (PMML) imported from another statistical package.
 
An error appears stating, "Model size exceeds maximum." Executing a report with an affected predictive metric fails as shown:
 

ka02R000000kcCQQAY_0EM440000002E5j.gif

 
Attempting to use the Predictive Model Viewer produces a similar error.
 

ka02R000000kcCQQAY_0EM440000002E5h.gif

 
In all such cases, an error like the following will be logged into DSSErrors.log. It could be seen on either the Developer or Intelligence Server error logs.
 


CPmmlrSupport::ValidateFile(790): Model size (0x0043F3BC) exceeds maximum (0x00300000 bytes).
CDmxPmmlrPKG::LoadModel(901): Model size (0x004A1D54) exceeds maximum (0x00300000 bytes).

 
CAUSE
The maximum size of a predictive model that will be allowed to import or used in Strategy is configured in the Microsoft Windows registry, under the key:
 

HKEY_LOCAL_MACHINE\SOFTWARE\MicroStrategy\DMX\Pmml\XMLSizeLimit

 

ka02R000000kcCQQAY_0EM440000002E5y.gif

 
The default value is hexadecimal 0x300000 (decimal 3,145,728, or 3MB).
 
Complex models, particularly those with relatively high cardinality for Tree variables, can exceed this size and fail to load into the Analytical Engine or into Desktop editors.
 
ACTION
Increase the registry key's value. The error recorded in DSSErrors.log includes the actual size of the model in hexadecimal. Use this as a guide for the new value.
 
Depending on user actions taken and the type of session (two-tier, three-tier or four-tier), the PMML may be loaded into either Strategy Developer, Strategy Intelligence Server or both. It may be necessary to update the registry not only on the Strategy Intelligence Server machine, but also on any Strategy Developer client machines that need to use predictive metrics.
 
To ensure that the new registry value takes effect, restart Strategy Intelligence Server and (if necessary) close and reopen Strategy Developer.
 
In Strategy Intelligence Server Universal environments running under UNIX/Linux, the registry key may be found in the registry file at /MSIReg.reg.
  


"CardinalityLimit"=dword:0000001e
"ModelLoadTime"=dword:00002710
"SVDIterations"=dword:0000001e
"XMLSizeLimit"=dword:00300000

 
Administrators should edit the last value for XMLSizeLimit (in hexadecimal) and then restart Strategy Intelligence Server.
 
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user`s own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.


Comment

0 comments

Details

Knowledge Article

Published:

May 22, 2017

Last Updated:

May 22, 2017