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.
It seems like we go months without issue and then this starts randomly popping up throughout the day. It occurs after an HTML report has refreshed on screen and the user press the export to excel button.... Most times its flawless for months, then all of a sudden we get a week of failures about 1 in 10 times....
- -
-
This message has been edited. Last edited by: FP Mod Chuck,
Originally posted by MartinY: Robert, Use the code tag when posting sample code. Last one on the ribbon
</>
And if you are posting markup language code (XML, HTML, etc) in the code section, surround your ML code with:
<xmp> </xmp>
Or (since technically the xmp tag has been deprecated), you'll need to change every "<" symbol with "<" [no quotes] so the browser does not render your code
So, when inspecting the code of this forum post, it looks like you were trying to post the following code, correct?:
The underlying agent that was running the report crashed for some reason. The edaprint.log may show something but I doubt it. You will see crashed agents under the Workspace in the reporting server console. If they start happening more frequently you can turn on the server traces with the following code in the fex that is crashing otherwise you will generate a zillion unwanted traces.
SET TRACEUSER = ON SET TRACEON = ALL
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005