As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
we've got the following problem with one of our reports (the report gets called with the same input data and parameters): - in 29 out of 30 times, the report runs fine - in the 30th time, the report gives an EDASERVE error - in the 31th time, the report runs fine again
The numbers are varying, but it makes it very hard to reproduce the problem.
We can't reproduce the problem in a simple TABLE FILE CAR fex, so it makes debugging a lot harder for us.
We tried to switch traces on, which gave the EDASERVE error a lot more often, so the traces were spammed with other EDASERVE errors.
Some more details about the report: - using several INCLUDEs - using a lot of variables - using a lot of labels, loops and GOTOs - reading large .foc files (around 6 GBs per file) - output format is HTML - there is enough free space on the file system
Does anyone know, how we can further debug this EDASERVE error?
Platform: - Windows 2003 VMWare Server - WebFOCUS 7.6.11 - Self Service application, no MRE installed
Thanks in advance, TobiasThis message has been edited. Last edited by: Kerry,
WebFOCUS 7.6.11 Reporting Server on z/OS 1.10 WebFOCUS Client / Caster on AIX Windows FFS on Windows 2k3 Output: Excel, PDF, HTML, CSV, XML, ...
Although this adds to the fexes, I would add in log file functionality.
FILEDEF a file outside the temp directory, in APPEND mode, and write where the execution is up to, to the file. This way you can at least determine if the crash is at the same place, or varies, and what code is potentially involved with the crash.
The other thing is what are the settings for Agent Refresh on the WebFOCUS server ?, are they set to one.
You may want to try to lower the agent_refresh first. Set it to 10 and see what happens. It may very well be that something is corrupting the agent's environment and it breaks the agent after so many attempts. If you set agent_refresh to 10 then you refresh the agent's environment before it gets to the corrupting point, tehreby effectively preventing crashes.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
thanks for the suggestion. I've changed the setting and I'll monitor if the problem still occurs.
I managed to save the generated .html file when the error occured with -SET &ECHO = ALL;
Looks like nearly the whole FEX ran fine, except one last -HTMLFORM statement.
The title bar of the generated HTML document sais: "WebFOCUS Message[0]: NO_WEBERROR"
If the problem still occurs, I'll upload the HTML file to IBI.
Thanks again for your suggestions, Tobias
[edit on 2011/09/21] We solved the issue. We had a HEADALIGN=BODY in our HEADING / FOOTING which caused the crash. The issue is fixed in 7.6.12.This message has been edited. Last edited by: tgall,
WebFOCUS 7.6.11 Reporting Server on z/OS 1.10 WebFOCUS Client / Caster on AIX Windows FFS on Windows 2k3 Output: Excel, PDF, HTML, CSV, XML, ...