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.
A user is getting this error: "Reporting Server messages exceeded IBIF_max_messages, report retrieval aborted. This message occurs when the user attempts to run a web-focus report. A JAVA screen for user selections suppose to come up and the user selects the report. It is not even getting to the selection screen before the error occurs. Counties are upgrading their computers will this cause the above error? Has anyone else experience this problem? If so, how can this be fixed?
Thanks, JeanetteThis message has been edited. Last edited by: Kerry,
Also if you will do a search on the Forum with that exact phrase you will see a bunch of ideas - and also on the tech site. Unfortunetly this could mean a lot of things.
Posts: 1903 | Location: San Antonio | Registered: February 28, 2005
In my experience the most common reason is that FEX code output exceeded the IBIF_max_messages limit. If this is the case, one solution is to make sure that &ECHO is set to OFF.
That is such an annoying problem to run into! If it would show the messages up to where the limit got exceeded, you'd at least have some idea what's going on... Unfortunately, all you get is "The limit got exceeded" and you have to guess why.
The message is even less helpful than IE's "A javascript error occurred at line n in <some output I won't be specific about>" (which is one of the reasons why most web-developers develop in other browsers before trying their code in IE).
I opened a case about this a while ago, don't know the status.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Thanks for all the support. The client's profile was not added to the fex that checks the person's ID. Basically, the program went into an endless loop. Thanks, the mystery is solved.