This content has been marked as final. Show 13 replies
extract of the 277942.1 note on metalink:
perhaps (!!) an explanation :
The crash no longer occurs when Reports Server tracing is switched off. This may be due to the size of the trace file and that there was insufficient disk space / memory/cpu available to create it.
Switch off Reports Server tracing by commenting out the xml tag relating to tracing in the Reports Server conf file.
------------------------------------------ end of note
Just a thought
I can cause my report server to crash quite easily
( not with your frm error ) but reason and solution may help
Default cache size is 50mb on 9i report server
If i change to 1mb and run a report which generates a cache file > 1mb ( a simple graph in this case ), form calling report will hang along with report server
Change cache to say 10Mb, restart report server and report runs without any problems
Can see the report failing in reports/rwservlet web page
Look in <appserver home>/reports/cache to see files created
edit <appserver home>/reports/conf/<report server>.conf
and look at cache size value
Hope this helps
I've been having exactly the same problem.
When I run the report and limit the amount of data, it works fine.
When I go over some amount, it fails.
I've played with the cache (and numerous other settings, including trace) and nothing has resolved this.
btw, I'm using this to create a delimited file, and the headers for thet file do show up in the cache directory, but no data.
Anyone have any luck so far?