Load Report Failed

[Former Member]

Hello,

Could someone please help me on this? I use Crystal Report bundled with VS.NET 2005 and I am getting "Load Report failed" from time to time in production. Most of times it works fine. It seems the problem appears when more people are viewing the reports. The only solution now is to restart the IIS but it becomes very difficult as it is production box. I have assigned full control on c:\windows\Temp to Network Service account, and dispose the Crystal Reports objects when page is unloaded. Any advice will be very appreciated.

Frank

[ted_ueda · Accepted solution]

Intermittent under load issues with ASP.NET resolved only by restarting IIS is suggestive of memory fragmentation issues, i.e., long-lived processes may have free memory so fragmented that a alloc of some size may fail, leading to strange IO or loading errors.

I'd try recycling the IIS app pool more regularly, if you haven't tried that already. A basic guide can be found here:

[http://technet.microsoft.com/en-us/magazine/cc161040(TechNet.10).aspx|http://technet.microsoft.com/en-us/magazine/cc161040(TechNet.10).aspx]

Sincerely,

Ted Ueda

[Former Member · Accepted solution]

Ted,

Thanks for your suggestion. The application pool has already been scheduled to recycle once a day but the problem still exists. The problem seems like that Crystal Reports does not release temporary files (~cpe{<random number}.tmp) under the C:\windows\Temp directory for some reason. If IIS gets restarted, the problem is solved right away and at the same time it generated about 288 ~cpe{<random number}.tmp files, then Crystal Reports starts to work. Any other suggestion?

Thanks a lot,

Frank

Edited by: Frank Yu on Jun 5, 2008 12:24 PM

[ted_ueda · Accepted solution]

Hello Frank,

The CR.NET creates temp rpt files that it then processes - your post suggests issues with cleanup.

I'd recommend, if not being done already, more stringent cleanup be done after a Report object is done with:

crReport.Close();

crReport.Dispose();

// If above does not resolve, explicitly invoking a GC cycle afterwards may help:

// GC.Collect();

You've indicated that it's not a permissions issue with the Temp folder, and I'm also inferring that the Temp folder still has plenty of space when the issue happens.

Sincerely,

Ted Ueda