Issues resolved by increasing IIS 6 Metabase Property “AspMaxRequestEntityAllowed”

The behavior that takes place due to the value for this IIS metabase property being too low are varied and do not point to IIS as being the culprit. If you have seen any of these issues, even intermittently, you may want to test your ProClarity Analytics Server after increasing the value for the “AspMaxRequestEntityAllowed” property in the IIS metabase to see if the increase resolves your issue. These issues will only occur within the ProClarity Web Standard client:

  1. ProClarity Web Standard users My View does not show up after being saved.
  2. When there are many members in a slicer dropdown, Internet Explorer displays a message stating that the page cannot be refreshed.
  3. Request object error ‘ASP 0104’:80004005.
  4. ProClarity Web Standard users are not able to use slicers or cross drill.
  5. Changing a ProClarity Web Standard view has no effect, the view is unchanged.
  6. The ProClarity Web Standard client may become unresponsive.
  7. A message stating “Your request could not be completed” may be received in the ProClarity Web Standard when attempting to render a published view.

The metabase can be exposed in a user-friendly application called the Metabase Explorer, which is included with the IIS 6 Resource Kit, which can be downloaded here:

Once the IIS 6 Resource Kit is installed, access it by browsing to Start > Programs > IIS Resources > Metabase Explorer. Once the interface is open, on the left hand pane, expand the machine node, and then expand the LM node. You should see the W3SVC node, click it to highlight it and locate the 7053 ID in the right hand pane:

Double-click the 7053 line or right-click to get the properties, at which point you will be able to modify the value, which by default in Windows Server SP1 is 204800 bytes, or about 200Kb. It is possible to identify the size of the “entity” by using a tool such as Fiddler ( to analyze the http traffic between the client and server. This would allow you to establish the value for this property using a logical method versus some random, large value. For our testing purposes and for identifying this property as a bottleneck, we usually set it to 1Gb (1073741824 bytes) and then recommend reducing it. Once you have modified the value, click OK and reset IIS. Test by repeating the steps that produced the symptom to see if the issue is resolved. Here is the TechNet explanation for this metabase property: