Error WIS 30553 - Session timeout

Error Message: Your Web Intelligence session has reached timeout. Log out and log in again to Infoview (Error : WIS 30553) 




EnvironmenT BO XI R 3.1 SP4
After getting this error message we have been not able to use the same session to create the reports successfully.

Solutions

The timeout parameter in web.xml is for Infoview web application.

Can you try changing Web Intelligence Server Timeout properties from CMC.

CMC->WebIntelligence Server ->Properties.


More complex solution

for JSP increase the application session-timeouts for the web.xmls for the three application locations as follows:

Business Objects XI 31\Tomcat55\webapps/WEB-INF/web.xml
Business Objects XI 31\Tomcat55\webapps\InfoViewApp/WEB-INF/web.xml
Business Objects XI 31\Tomcat55\webapps\CmcAppActions/WEB-INF/web.xml

2.
Increase the attribute value under to perhaps 60 in this example:
   20

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

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


Open web.config in a text editor like Notepad and search for the following 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"
/>

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

4.
Log on to the CMC and browse to Home > Servers > Web_IntelligenceReportServer > Connection Time Out.

Set this number to a value that is lower than the application timeouts, for example 50.

5.
Ensure that the universe timeouts are coordinated as well. 
In Designer, click File > Parameters > Control > Limit execution time to, and set this value to be equal to the Web
Intelligence Connection Time Out.


Cluster Environment solution


We were  able to resolve the timeout error by following steps:
- Turn off services running on one of the two servers that are part of Cluster, say server A.
- Restart BO services running on server B.

After that, when we restarted services on server A, services on server B worked fine. If two CMS are part of a cluster, then the timing on both servers must be in sync. In our case, two underlying servers were out of sync by few seconds.


See also:

BUSINESS OBJECTS ERRORS LIST

Comments

Popular posts from this blog

SAP Dashboard Error - Cannot find the BusinessObjects Enterprise report source. (LO 26608)

SAP HANA Introduction

SAP BusinessObjects 4.0 - Suite Presentation