Why do I receive an ASP error when exporting reports?

KB#: KKB000673


Why do I receive an ASP error when exporting reports?

Customer receives the following error when they try to generate a large machine summary report and export to a excel file: -

The page cannot be displayed

There is a problem with the page you are trying to reach and it cannot be displayed.

HTTP 500.100 - Internal Server Error - ASP error

Internet Information Services

Error Type:
Response object, ASP 0251 (0x-7fffbffb)
Execution of the ASP page caused the Response Buffer to exceed its configured limit.
/install/ExpFiles/column-ho/E0038791.asp, line 2

Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)


The message and information provided indicated that the server did not have enough resource to process the export - the Machine Summary report contains a large amount of data.



Ensure OS and SQL Server are at latest service pack, and fully patched

Consider upgrading server hardware - a RAM upgrade would be the most likely solution

As a workaround, split the report into smaller groups of machines

Please refer to Microsoft documentation for descriptions of IIS error codes

This fix is from a third party site

If you get the above error when you click on an attachment, the attachment is larger than IIS is configured to allow. Change the AspBufferingLimit setting in Metabase.xml to a larger size. The default value is 4194304, which is about 4 MB. Change this to whatever limit is reasonable for the types of files your users will be attaching.

This change does not require stopping IIS, but to make the Metabase.xml file write-able, you need to go to the IIS control panel, right click the server, select properties, and check off the box that says “allow changes to MetaBase configuration while IIS is running”.



Kaseya Server - all versions
IIS - all versions

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section