Has anyone seen this error before?
The report has a run time of 25 - 30 mins
I can refresh the report on-demand with no problems
p_b_bradley (BOB member since 2006-03-15)
Has anyone seen this error before?
The report has a run time of 25 - 30 mins
I can refresh the report on-demand with no problems
p_b_bradley (BOB member since 2006-03-15)
Good day, I just started looking into tis. We are getting this error when scheduling somedesktop intelligence reports. that are being saved as a pdf file.
Sandra Kruse (BOB member since 2006-10-25)
I’m trying a fix I found doing a search on BOBJ support
Go into the CCM and stop the WEBI job server
add RequestTimeout 10800000 to the command line right before object type as seen below
Also check that the Connection Time for that job server in the CMC is not less then 20 mins
I’ll let you know if this works
“\SERVERNAME\E$\Business Objects\BusinessObjects Enterprise 11.5\win32_x86\procWebi.exe” -service -name SERVERNAME.Web_IntelligenceJobServer -ns SERVERNAME -RequestTimeout 10800000 -objectType CrystalEnterprise.Webi -lib procwebi -restart -jsTypeDescription “Web Intelligence Job Server”
When the- RequestTimeout is more then 20 mins, you must ensure that the Connection Time
p_b_bradley (BOB member since 2006-03-15)
The Above Fix Worked
p_b_bradley (BOB member since 2006-03-15)
This resolved my issue as well. In my case it was a Webi report that was scheduled and the processing time exceeded 30 minutes.
Platform:
Business Objects XI R2 revision:11.5.7.603
jdh2n (BOB member since 2006-11-13)
This solution worked for me as well. Why the default timeout for a scheduled job would be only 10 minutes is beyond me
I’d like to see BO increase the default timeout to something more reasonable, say 30 minutes.
DJ
DJ06482 (BOB member since 2002-11-22)
Pardon me for appearing dense, but there are still three things I don’t understand in this thread. One is, where does the number 10,800,000 come from? The second is, where does the idea that 10 minutes is the default come from? And the third is, where does one see the connection time in the CMC for the job server? (In all fairness, the post that mentions this last item appears to be cut off in mid-sentence.)
joel6653 (BOB member since 2006-11-22)
We are having the same issue could you please eloborate how you resolved the same at your site
thanks in advance
Bobby (BOB member since 2004-05-05)
This link will give you the entire picture of the issue.
venira (BOB member since 2004-12-07)
Thanks, but we are having issues when we schedule Deski Documents, most of the deski document=s format are messed, after applying MHF1 any ideas how to resovle this
thanks in advance
Bobby (BOB member since 2004-05-05)
Hi,
Firstly - thanks to the person who suggested this - it worked for us too ! . However I am curious to know why this is still an issue with XI Release 2 and MHF1. That bug (ADAPT00388456) was recorded for XI Release 1. Has this never been fixed or has the bug crept back in? It seems a bit clumsy having to modify the service parameter line - wouldn’t it be better to modify this timeout in the CMC or via an XML file? (cue someone telling me where to check
)
Thanks
Rod
rodallen (BOB member since 2006-02-10)
Rod -
I agree that this still shouldn’t be an issue in the current version of the software. I’ve never tracked that ADAPT number, but my guess is that they thought they had it fixed only to discover that they hadn’t. IMHO, a 10 minute default timeout for scheduled jobs is much too short.
I don’t know of another way to change this timeout other than through the command line parameter in the CCM…
DJ
DJ06482 (BOB member since 2002-11-22)
I am also confused by how all these timeouts interact with each other. We are running into an issue where a long running report seems to be failing with this Transport Error: Communication Failure message after about 2 hours.
Our CCM command line for the Webi Job Server has a timeout of 3600000, which should be 60 minutes.
I’m just struggling on how a timeout of 10 minutes, 60 minutes or whatever correlates to a timeout happening at the two hour mark? Could it be a combination of timeouts?
Forgot to add that we are XIR2, MHF1, and CHF15EDT
Thanks, Marvin
mwendorf (BOB member since 2006-09-26)
Does any one know if the command that is fixing this is case sensitive. I have add the command to my ccm and adjusted my job server but it is still not resolving this error
nrusse (BOB member since 2006-06-27)
Greetings,
The latest Kbase article on this subject can be found here:
I believe you still need the latest and greatest service pack and fix pack to resolve. I’m currently testing on XIR2SP2FP2.4
Have a great day!
MayhewM (BOB member since 2003-10-22)
Helped me to fix my issue too… I used -RequestTimeout 14400000 in my WebI Job server. Actually we had the setting in other WebI Job servers, when a new WebI Job server was added, the parameter was missed.
Thank you for the help!
sivackumar (BOB member since 2007-08-22)
All,
I am facing a similar problem of getting a Transport error when the report takes more than 30 minutes for scheduling.
However, my setup is BOXIR2 on Solaris. The Kbase article gives instructions for Windows setup. Does anybody know the solution for unix environment for this problem?
Thanks.
smartrisk (BOB member since 2006-05-25)
Hi
This is FYI.
I used the same parameter name in unix (’-RequestTimeout xxxxxx’) and it worked!
Thanks
smartrisk (BOB member since 2006-05-25)
Can the “RequestTimeout” parm be added to other servers like the Deski Report server, same as Webi Report Server? We get Transport errors for multiple servers, not just WRS.
ccermak (BOB member since 2007-11-13)
Sorry can’t help you on that. I have set it up only for WebI Report server. But I think you may try it out on development instance.
smartrisk (BOB member since 2006-05-25)