cancel
Showing results for 
Search instead for 
Did you mean: 

Lost connections

Former Member
0 Kudos

Hi, we are running XIr2 over Citrix. After a certain period of time (a few minutes) of leaving a deski session, if I return to it, and attempt to refresh the data, or access the universe in any way, it appears as though I have lost connection to the universe.

I am presented with errors like "Connection or SQL sentence error: (DA0005); Exception: CS, Unexpected behaviour", and "A connection required to refresh this document is unavailable (DA0004)".

Thanks.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Following solutions will be helpful for you to resolve the issue.

Web Client or Browser TCP Timeout (also applicable to Desktop Intelligence in 3-tier mode)

By design, Internet Explorer imposes a time-out limit for the server to return data. The time-out limit is five minutes for versions 4.0 and 4.01 and is 60 minutes for versions 5.x and 6. Also, the time-out limit is 30 seconds for Windows Internet Explorer 7. As a result, Internet Explorer does not wait endlessly for the server to come back with data when the server has a problem.

This timeout is applicable to workflows that involve Internet Explorer browser (Infoview, CMC etc) or Desktop Intelligence in 3-tier mode

This timeout is specifically applicable to workflows that involve large request wait times (eg. > 60 mins).

To change the Web Client connect timeout impacting the Internet Explorer and Desktop Intelligence 3-tier, the TCP timeout needs to be changed on the client workstation as follows -

a. Add a ReceiveTimeout DWORD value with a data value of (<number of seconds>)*1000 in the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

For example, if you want the timeout duration to be 90 minutes, set the ReceiveTimeout data value to 54000000 (<5400>*1000)

b. Restart your computer.

Business Objects Enterprise Server CORBA timeouts

Business Objects servers communicate via CORBA and can sometimes timeout if requests are not returned within 20 minutes (default CORBA timeout). In such cases, timeouts on these servers can be adjusted to meet our requirements.

While the below switch can be applicable to all processes, this is generally useful switch for your Crystal Page server, RAS server, WebIntelligence & Desktop Intelligence Report Servers and All Job Servers, and Connection Server processes.

Command Line Switch for adjusting Corba timeout -

-RequestTimeout, where the value is set in milliseconds.

(1 minute is equal to 60,000 milliseconds)

This timeout is set in Central Configuration Manager, for all applicable processes.

Just stop the process, Edit the Command line and add u201C-RequestTimeout 5400000u201D at the end of Command Line, without double-quotes which should bump the corba timeout to 90 minutes.

For timeout issues relating to 3-Tier Desktop Intelligence processing, go to Servers > Connection Server, and change the connection pooling timeouts to 90 minutes.

WebIntelligence Server Swap timeout u2013 registry setting

This timeout is only applicable to user workflows involving the creation and modification of WebIntelligence reports on Windows platform.

Timeouts can occur because the Web Intelligence Report Server time-out value is set to a low value, usually the default value of 300 seconds. The temporary file that holds the report will be discarded after that time, hence the timeout needed to be increased.

1. Click Start > Run. The Open dialogue box appears.

2. Type u201Cregeditu201D in the Open field of the Run dialogue box. The Registry Editor appears.

3. Navigate to registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5default\WebIntelligence\Server\Admin\SwapTimeOut.

4. Edit this value to 5400 seconds (90 minutes).

5. Alternately, 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.

6. Close the Registry Editor.

7. Restart the Web Intelligence Report Server for the changes to take effect.

Other timeout considerations

1. Universe Connection timeouts

There is no time-out value which can be set directly at the universe level, however, the Limit execution time to setting is important. It sets a limit on how long the SQL query is allowed to execute and provides control over the processing load that users can put on the database server. The setting can be found in the Designer by going to the File > Parameters > Controls tab. The default is set to a maximum of 5 minutes. If it takes longer than this time to retrieve data from the database, the query is aborted.

2. Database client timeout Settings

3. Database Server side timeouts and thresholds.

4. Any intermediate Firewall timeout settings

5. 3rd party timeouts u2013 for 3rd party integrated applications like Siteminder, GetAccess, LDAP, AD etc.

6. Other network hardware/software related timeout settings (e.g. proxy server, proxy configuration scripts etc)

Regards,

Sarbhjeet Kaur

Former Member
0 Kudos

Hi Louise,

Could you please test the following solution.

To resolve you will need to increase the value for the "IdleSessionTimeout" parameter. Here are the steps:

Go to Start > Run.

Type "Regedit" and click on OK.

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\CMS\Instances\<HOST.cms>.

Increase the value for the "IdleSessionTimeout" parameter to 3600000(60min). The default value is 600000 (10 min).

Regards,

Sarbhjeet Kaur