Hi All,
For This the first case:
1) Go to windows explorer.
2) Go to C drive (or wherever your Tomcat is installed) c:\programfiles\Tomcat\webapps\businessobjects\enterprise115\desktoplaunch\WEB-INF\classes\webi.properties
3) open this file webi.properties with a notepad and add MAX_HEAP_SIZE=1024000000 as the bottom most line of the file.
4) Save the file.
5) Restart the tomcat server and webi as well.
KBase Article ID:1026601
Article refers to: BusinessObjects Enterprise XI
Cause
The error message appears because the Web Intelligence server stresses the memory resources when processing many reports containing a large amount of data.
Resolution
To resolve the error message, it is necessary to increase the memory heap size value. Complete these steps:
Click Start > Run. The Run dialog box appears.
Type "regedit" in the Open text field. Click OK. The Registry Editor appears.
Navigate to the HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager.
Click Subsystems > right-click Windows key > click Modify.
Edit the SharedSection value from 1024,3072,512 to 1024,3072,1024.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite
11.5\default\WebIntelligence\Server\Admin\SwapTimeOut.
Edit this value to 1500 seconds. Alternatively, set this to a value higher than the Web Intelligence Report Server connection time out value found in the Central Management Console. This value is written in minutes. The default value is 20.
Close the Registry Editor.
Restart the Web Intelligence Report Server for the changes to take effect.
Second case:
Probable Resolution:
Log onto Central Management Console (CMC).
Click on Servers.
Click on Web_IntelligenceReportServer.
Click on Properties tab.
Reduce the "Cache Timeout (minutes)":to 20 minutes.
Reduce the "Document Cache Cleanup Interval (minutes)":to 20 minutes.
Click on Apply to Update.
Restart the Buisness Objects Servers.
Final this is answers
The problem is pretty much exactly what the error says.
Your Webi Report Server has run out of memory.
This could be to 2 things :
1. Bad report design that brings too much data in or has too many report side calculations and combination of that make WIRS run out of memory
2. The server is overloaded with requests, too many reports are being processed at the same time
3. There are some bugs in early product versions that contribute to this and fixed in later Service Packs/Fix Packs
Regards
Narasimhulu M