Error when exporting EPiServer pages

Vote:
 

I'm getting the following error message when I try to export pages using EPiServer's "Export data" utility:

 [ObjectDisposedException: Can not access a closed Stream.]
   System.IO.Compression.DeflateStream.Flush() +1852399
   MS.Internal.IO.Packaging.CompressStream.Flush() +23
   MS.Internal.IO.Zip.ProgressiveCrcCalculatingStream.Flush() +17
   MS.Internal.IO.Zip.ZipIOLocalFileBlock.FlushExposedStreams() +10
   MS.Internal.IO.Zip.ZipIOLocalFileBlock.UpdateReferences(Boolean closingFlag) +97
   MS.Internal.IO.Zip.ZipIOBlockManager.SaveContainer(Boolean closingFlag) +174
   MS.Internal.IO.Zip.ZipIOBlockManager.SaveStream(ZipIOLocalFileBlock blockRequestingFlush, Boolean closingFlag) +64
   MS.Internal.IO.Zip.ZipIOFileItemStream.Flush() +24
   MS.Internal.IO.Packaging.CompressStream.Flush() +56
   MS.Internal.IO.Zip.ProgressiveCrcCalculatingStream.Flush() +17
   MS.Internal.IO.Zip.ZipIOModeEnforcingStream.Flush() +17
   System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) +154
   System.IO.StreamWriter.Flush() +11
   System.Xml.XmlTextWriter.Flush() +9
   EPiServer.Enterprise.DataExporter.Close() +75
   EPiServer.Enterprise.DataExporter.Dispose() +18
   EPiServer.UI.Admin.ExportData.OnLoad(EventArgs e) +1092
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

This error pops up after the export has finished or almost finished processing about 800 pages. If I browse away from the export page and return to it again the error message is still there - it takes a web server reset to clear it. Could it be a timeout issue or similar?

#23528
Sep 08, 2008 20:43
Vote:
 
Version of EPiServer CMS is 5.1.422.256 SP2 BTW...
#23529
Sep 08, 2008 20:46
Vote:
 

Hi,

I would try exporting again but with EPiServers logging enabled at Debug level. FAQ about logging: http://world.episerver.com/en/FAQ/Items/How-do-I-create-a-log-in-EPiServer/

Then check the log file for more clues about the problem. It usually tells you alot more than the stacktrace.

--Per

 

#23533
Sep 08, 2008 22:53