sessions and licenses are not released after the session timeout is reached

For Infoview, in addition to setting the timeout parameter, users need to uncomment the following line in web.xml to make a listener explicitly log off the session objects when they are invalidated:


'

'com.businessobjects.sdk.ceutils.SessionCleanupListener

'

For the CMC, users need to set the timeout parameter in the web.xml file

Changing the default session timeout value for .NET CMC or InfoView

To change the default session timeout value for licenses for the CMC and InfoView, perform the following steps:

1. Search for the web.config file.

• To modify the default session timeout value in the CMC, search for web.config in the C:\Program Files\Business Objects\BusinessObjects Enterprise 11\Web Content folder.

• To modify the default session timeout value in InfoView, search for web.config in the C:\Program Files\Business Objects\BusinessObjects Enterprise 11\Web Content\Enterprise11\InfoView folder.

2. Open web.config in a text editor like Notepad and search for the following 'sessionState' section.


mode="InProc"

stateConnectionString="tcpip=127.0.0.1:42424"

sqlConnectionString="data source=127.0.0.1;user id=sa;password="

cookieless="false"

timeout="20"

/>

3. Change the 'timeout' attribute to set a new default session timeout value (in minutes).

Upon completing these steps, the default session timeout value in the CMC and InfoView is updated.

How to install the ActiveX viewer manually

How to install the ActiveX viewer manually in BusinessObjects Enterprise XI Release 2

Here are the steps:

1. Navigate to the ActivexViewer.cab located in the \Business Objects\common\3.5\crystalreportviewers115\ActiveXControls folder.

2. Extract the following .dll files:

CRViewer.dll
sviewhlp.dll
swebrs.dll
reportparameterdialog.dll

3.Copy the files to a folder on the client computer (for example, C:\Temp).

4. Register the .dll files from the command prompt using regsvr32 as follows:

regsvr32 C:\Temp\CRViewer.dll
regsvr32 C:\Temp\sviewhlp.dll
regsvr32 C:\Temp\swebrs.dll
regsvr32 C:\Temp\reportparameterdialog.dll

Desktop Intelligence Permission Problem

Platform:
Desktop Intelligence
BusinessObjects XI, XI Release 2

A
common problem is when you delete a report from the repository and then
realises that it was a mistake removing it. Even though you have a
local copy of the report you can't open it. This is because BOE is
validating the rights against the repository and when the report does
not exist there it can't be opened.

If you try to open that report in Desktop Intelligence you will get an error stating: You are not authorized to use this document. (FRM00008).



There
are a number of possible workarounds for this problem, one being that
you create a dummy report in the repository with the same name as the
report you just deleted. Then you find out the path and file name
through Central Management Console. Browse to the report folder in
Input File Repositry Server and delete the file (remember the file
name). Add the original report to the same place and change it's name
to the same as the deleted file. Now you are able to import it into
Desktop Intelligence.

This solution doesn't work in all
situations and it's not a supported method. Manually deleting files
from FRS is NOT a good idea in most cases. With this particual problem
there exist a different solution that will solve this.

1. Open Desktop Intelligence - check the Use in Offline Mode checkbox when logging in.
   
   
   
2. Open the report.
3. Save your report - check the Save for all users
   
   
   checkbox.
4. Close Desktop Intelligence.
5. Open Desktop Intelligence - login to your repository, not in offline mode.
6. It should now be possible to open the report and publish it to the repository.

And, yes, a backup is also one way out of this...

Web Intelligence Error--RWI 00134

If you receive the error "Could not get an output file for the document." with error code RWI 00134 there is a problem with Tomcat.



The
error source are unknown to me but if there are anyone knowing this it
would be interesting to learn. As this problem is isolated to Tomcat
the problem is only visible in the Java platform. The code RWI stands for ReportEngine Web Intelligence which means that the problem is only affecting Web Intelligence reports.

The solution is to restart Tomcat.

There
exist an error description from Business Objects but it doesn't give
much information other that it could be a memory related problem:

Cause
While serializing a document state, an error occurred. This might be due to insufficient memory or an I/O error.
Action
Ensure that there is sufficient memory available. Also, check for any we bi.properties customization.

BOXIr2 Version Numbers

BusinessObjects Enterprise XI Release 2 Version Numbers

MHF = Monthly Hot Fix.
CHF = Critical Hot Fix.
SP = Service Pack.
FP = Fix Pack.
RTM = Release To Market (first release, without any patches).

* 11.5.0.313 --> RTM
* 11.5.3.417 --> SP1
* 11.5.7.608 --> MHF1
* 11.5.7.682 --> CHF13
* 11.5.7.723 --> CHF14
* 11.5.7.770 --> CHF15
* 11.5.7.811 --> CHF16
* 11.5.7.852 --> CHF17
* 11.5.7.1048 --> CHF20
* 11.5.8.826 --> SP2
* 11.5.8.826 --> FP2.1
* 11.5.8.939 --> FP2.2
* 11.5.8.963 --> FP2.3
* 11.5.8.998 --> FP2.4
* 11.5.8.1030 --> FP2.5
* 11.5.8.1061 --> FP2.6
* 11.5.8.1111 --> FP2.7
* 11.5.9.1076 --> SP3
* 11.5.9.1101 --> FP3.1
* 11.5.9.1138 --> FP3.2
* 11.5.10.1263 --> SP4