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.
I am viewing Defered Report Status Screen which gives the option to Delete/View/Save the report. I am getting the following error message when I try to save the report in defered report status screen.
An HTTP 500 error has been returned when attempting to communicate with the WebFOCUS web components. The application server log contains information on why this error has occurred.
Reporting Server is running on Unix. Where should I look for error message?
Hi Kar, When the Deferred report is SAVED, the files will be stored under the WebFOCUS\basedir\user as .orw files. Check the permissions on this folder and also look at the Web Server log for some other indications of where the problem is. Rich
WebFOCUS 8202 Win 2012 Test - WebFOCUS 8203 on Win 2012
For HTTP 500 .. you look in the java app server log (for tomcat, it is the log folder under the main tomcat directory - your app server will vary). Bit first, run diagnostics from the WF admin console, it looks for permission problems, etc.
Brian Suter VP WebFOCUS Product Development
Posts: 200 | Location: NYC | Registered: January 02, 2007