Don't know the specifics but I worked with a large variety of Crystal reports
recently and had similar experience with the large/huge ones.
The workaround is a lot of times that they need to be processed separately,
i.e. one of 3000 processed crystal reports do this - don't process it - make
it an exception - process it "manually" outside of the production system
(might
or might not apply to you - probably not from what I can tell).
I'd suggest you'll somehow identify these huge Crystal Reports (good way
is to just load them on a development machine - define the data source -
let it run and see how long it takes to process - sometimes minutes!!!??).
"DotNet Guerrilla" wrote:
A huge web form Crystal Report hangs the aspnet_wp.exe process, so I have to
stop the aspnet_wp process to brig the site a live. This error is driving me
crazy. Please, advice!
Thanks
--
DotNet Guerrilla