Which registry setting to change for long running reports

Question

Hi, We are on BOXI R2 SP3 on IIS 6.0. We have web servers in DMZ and have ports opened. We have reports running longer than 25 mins in production and business is facing issue as reports are timedout  ( Errors ;oke The request timed out because there has been no reply from the server for 600,000 milliseconds .) after 20 mins. We would like to increase this value.  I read KB 1324139  but its for Tomcat and we are on IIS 6.0.
I am planning to increase the values of below registry entry and also add command line parameter like "-requesttimeout 3600000 in RAS servers.
Anyone knows if I am overdoing or doing less?
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Report Application Server\Client SDK\CorbaAdapter]
"WaitReplyTimeout(ms)"="600000"==============================================>>>>>>> Want to increase this
"SendRequestTimeout(ms)"="10000"
"UpdateServerListInterval(ms)"="60000"
[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Report Application Server\InprocServer]
"EnterpriseRequestTimeout(min)"="600000"==============================================>>>>>>> Want to increase this
[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Report Application Server\Instances]
[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Report Application Server\Instances\xxxxx505.RAS\Server]
"EnterpriseRequestTimeout(min)"="600000==============================================>>>>>>> Want to increase this
[HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 11.5\Report Application Server\Server]
"EnterpriseRequestTimeout(min)"="600000" ==============================================>>>>>>> Want to increase this

Answer 1

Hello Pandeyji and others,
I was having the same problem, and I referred to your thread for fixing it. I got some different results which I want to share with everyone.
First of all, how is my application different? My application is actually just a jar file which is invoked through command line. There is no web-interface, so there is no app servers/web servers that need to be configured, unlike Pandeyji's configuration.
All you need is a JDK and some dependent jar files such as log4j etc to run my jar. I was getting timeout when I was calling the byteoutputstream method to export my published crystal report into a flat file. I went through a lot of registry settings as illustrated in Pandeyji's summary above, but that did not fix the issue. I kept on getting, timeout after 600,000 milliseconds and I was trying to figure out from where it's reading this value.
Then I installed procmon to see from where it's reading the clientsdkoptions.xml file. Once I found that, I replaced that file with my version of clientsdkoptions.xml file.
Now here's the interesting part - After I replaced it with my version of clientsdkoptions.xml file, I could see in ProcMon that the RAS api was indeed reading my file, but even after I had put in a different timeout of 240,000 it kept on ignoring it, and continued timing out after 600,000 milliseconds. That was crazy...and I couldn't figure out what was happening.
I strongly suspect and believe that a majority of us have had the same results, and so none of us was sure from where it is reading that 600,000 value. Finally, with my java xml background, I kindda suspected that maybe at the time I was editing the clientsdkoptions.xml file (which I obtained from our BOE default installation directory), I probably introduced some special characters, and so kindda distrubed the default encoding of the file, and maybe that's why even though RAS is reading my clientsdkoptions.xml file, it's not using the timeout value from there.
SO.......I recopied the default clientsdkoptions.xml file from our default BOE installation, and this time opened it in notepad, and edited the timeout value there....and voila it worked...I also changed the <server> tag to a different value, say TEST_SERVER, and it still worked. Then I went back and changed all the registry values back to default 600,000 and IT STILL WORKED....meaning, the RAS API picked up my customized timeout from clientsdkoptions.xml file and not from the registry.
I've searched this issue and read it at several forums where I've seen people struggling to fix this timeout or increase it and failing even after doing all the changes..I thought let me post my experience and let everyone know..maybe it's only one change at one place that's required to be done, and not like 10 different changes at 10 different places.
Hopefully, as always, SAP Support will read this and publish a note for us developers to ease this pain. Thanks & please let me know if anyone has any questions.