It seems to be well known issue, but the solution is not so trival
Obviously the reason is that your managed heap is overly fragmented that FW
couldn't find free 64mb heap segment to allocate memory.
There are several descriptions in the net about how to investigate this
problem, especially Tess blog (MS escalation engineer)
I recomend to read this recend article
http://msdn.microsoft.com/msdnmag/is...t/default.aspx that
describes your aspect of problem
--
WBR,
Michael Nemtsev :: blog:
http://spaces.live.com/laflour
"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
"karups" wrote:
My application will have a fetch button.
As soon as we click the fetch button..It calls a Stored Procedure.
The stored procedure will return a dataset back(huge on with rows 25000
and col:52)...
I export this dataset to excel using this code
Response.Clear();
Response.AddHeader("content-disposition",
"attachment;filename="+filename+".xls");
Response.Charset = "";
this.EnableViewState=false;
Response.Cache.SetCacheability(HttpCacheability.No Cache);
Response.ContentType = "application/vnd.xls";
System.IO.StringWriter stringWrite = new System.IO.StringWriter();
System.Web.UI.HtmlTextWriter htmlWrite = new
HtmlTextWriter(stringWrite);
DataGrid myDataGrid=new DataGrid();
myDataGrid.DataSource=dsReport.Tables[1];
myDataGrid.DataBind();
myDataGrid.RenderControl(htmlWrite);
Response.Write(stringWrite.ToString());
Response.End();
While doing this i get the OutOfMemoryException..