|Applies To||RSA Product Set: Archer|
Platform (Other): IIS
O/S Version: Windows Server
Product Name: IIS
When attempting to export large reports containing thousands or tens of thousands of records, users may receive the message below:
An error has occurred during the export process. The export file cannot be completed.
Primarily seen with CSV and XLS however the failures are not exclusive to these formats.
One possible cause of this failure can be found in the Application Pool Recycle settings.
If you have the Application Pool configured to recycle based on a memory threshold, this threshold can be easily reached when exporting large reports which causes the Application Pool to reset and the export to fail.
Change the Application Pool Recycle setting to a time based limit rather than a memory based thresholds.
(example of recommended setting below)
From experience, I recommend setting this to 1440 (24 hours) and also setting it to a fixed time (like 4am if you’re EST, 1am PST) Setting this to a fixed time each day during the lowest anticipated traffic times will minimize any impact and also allow you to troubleshoot easier if you run into any issues. If you have multiple application pools, it might be wise to stagger them to avoid overloading the server with recycles. Also note that IIS ‘overlaps’ the app pool when recycling so there usually isn’t any true downtime during a recycle. Existing actions will continue to process until complete and any new actions will be picked up by the newly spawned worker process. However, in-memory information (session state, etc) would be lost.
|Workaround||Other than "Export smaller reports", No other workaround is currently known.|
|Notes||Note the information included below |
Application Pool Recycle times