SQL generation failed see your business objects administrator (Error:WIS 00

Question

I have a user who in WEBI has refreshes report frequently.
:stupid: . After 5-10 minutes of inactivity it will toss out this error:
SQL generation failed. See your business objects administrator. Error: WIS 00013 Error: INF

Answer 1

Hi Rohit,
could you please test the following settings to resolve the issue.
1. CORBA
-requestTimeout
This is the default CORBA timeout which can be set on any BOE services through command lines in CCM. And this switch is in millisecond.
Registry CORBA Timeout
This is a default hard coded 10 mins timeout for CORBA. WebI and DeskI did get integrated into this regkey:
(1) Go to HEKY_LOCAL_MACHINE -> SOFTWARE -> Business Objects -> Suite 11.5 -> CER.
(2) Modify ConnectionTomeout from 600000 to higher value.
(3) Restart all services in CCM.
2. Infoview Java Application (For example, Tomcat) Session Timeout If a user idles in Infoview for longer than this timeout, the session will be killed automatically. The default session timeout is 20 mins. To change the default session time out for InfoView:
(1) Go to u201Cu2026\Tomcat\webapps\businessobjects\enterprise115\desktoplaunch\WEB-INF\web.xmlu201D
(2) Modify web.xml. Scroll to the following section:
<session-config>
<session-timeout>20</session-timeout>
</session-config>
(3) Edit the <session-timeout> value to the desired value. Save the web.xml file.
(4) Restart Tomcat.
If you meet their sessions are not getting released when they log out, here are two things to check in web.xml:
(1) If the below configuration was set by true, that means they will have another session allocated to them once they begin to move around in Infoview after the user times out. If it was
set by false, the user have to re-logon after they times out.
<context-param>
<param-name>logontoken.enabled</param-name >
<param-value>true</param-value >
</context-param>
(2) All sessions will be cleanup after they times out if uncommented the below configuration. If you are having issues with sessions staying in CMS, try to uncomment the below line and
restart tomcat.
<listener>
<listener-class>com.businessobjects.sdk.ceutils.SessionCleanupListener
</listener-class>
3. Tomcat
ConnectionTimeout
The default value is 20000 milliseconds. To disable it, try to set the value to -1 as below:
(1) Go to u201Cu2026\Tomcat\conf\server.xmlu201D.
(2) Find line u201CConnector on port 8080u201D.
(3) Modify connectiontomeout = u201C20000u201D to ConnectionTimeout = u201C-1u201D.
4. Universes
Execution Timeout
(1) Go to Universe Designer -> File -> Parameters -> Controls.
(2) Check the value of u201CLimit execution time tou201D.
5. WebI
Connection Timeout
The number of minutes before an idle connection to the WebI Report Server will be closed. When Java Report Panel, it is now controlled by this timeout switch:
(1) Log into CMC
(2) Go to Servers -> WebI Report Server
(3) Set Connection Timeout
WebI Report Timeout
WebI designers have the ability to set a limit on how long a query can be run on a database before the query is stopped:
(1) Edit/Create a new WebI report using Java Report Panel.
(2) Choose Edit Query -> Properties.
(3) Now deselect/increase the "max retrieval time" value.
Swap Timeout
In Java Report Panel and you leave it idle for more than 5 minutes (Default), you will notice that you will no longer be able to save your WebI report into CMS or your report will take longer
to generate. This is because SwapTimeOut setting which controls the flushing interval of WebI temp files:
(1) HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\default\WebIntelligence\Server\Admin\SwapTimeOut
Regards,
Sarbhjeet Kaur