Out of Memory error on 9.05.605 BAQ Report

Yahoo Archive
1
This is a bug in the print subsystem (Epicor.Mfg.BO.ReportMonitor.dll) fixed in 9.05.606 from the SCRS matrix.
They recently changed the way the data is access from UNC to transferred though the appserver, this means it can benefit from the compression settings but there was some incorrect string handling that causes large XML documents to run out of memory.
There is a hot fix around from Epicor but I don't know the reference, I had the issue with large WIP reports.

Regards,
Stephen

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of dyoderbx
Sent: 04 August 2011 20:11
To: vantage@yahoogroups.com
Subject: [Vantage] Out of Memory error on 9.05.605 BAQ Report



Recently upgraded to 9.05.605. Now, some of our larger BAQ reports are getting this message: System:OutOfMemoryException was thrown.

Epicor's answer is to retrieve less data by filtering out some records. They claim this is a Windows message and they cannot do anything about it.

Anyone have any suggestions or work-around?

The BAQ returns all the records when I run it manually. And when the report runs, the XML is created. (Around 44 MB) If I bring the XML into the Crystal report, the report will run fine.

Denton



[Non-text portions of this message have been removed]
2
Recently upgraded to 9.05.605. Now, some of our larger BAQ reports are getting this message: System:OutOfMemoryException was thrown.

Epicor's answer is to retrieve less data by filtering out some records. They claim this is a Windows message and they cannot do anything about it.

Anyone have any suggestions or work-around?

The BAQ returns all the records when I run it manually. And when the report runs, the XML is created. (Around 44 MB) If I bring the XML into the Crystal report, the report will run fine.

Denton