Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] IBFSException 6000: Too Many Messages

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] IBFSException 6000: Too Many Messages
 Login/Join
 
spp_123
Member
posted
We recently added a new field to a table (it's a Survey Monkey question) and each time we run any report with the table, we receive the IBFSException 6000: Too Many Messages error. Has anyone seen this error and figured out how to fix it?

We query the table in the SQL server for the same amount of time and parameters as a report we run, and the SQL Server pulls the data in less than a second.

This message has been edited. Last edited by: FP Mod Chuck,


WebFocus 8105, Windows 2016, HTML
 
Posts: 10 | Registered: September 11, 2017Report This Post
MartinY
Virtuoso
posted Hide Post
Try running your fex with
1- SET &ECHO = ALL at the beginning of your fex
2- Add " WHERE RECORDLIMIT EQ 1000; " in the filter section of you TABLE FILE... END
3- -EXIT right after the extraction

You may then see what cause so many error message

If nothing found, then increase the RECORDLIMIT and try again.


WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF
In Focus since 2007
 
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013Report This Post
FP Mod Chuck
Virtuoso
posted Hide Post
Spp_123

If Martin's suggestion doesn't work, there is a setting on the client administration console for Maximum messages that you can temporarily change the value to 0 which means unlimited and it will prevent the too many messages error.


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, 2005Report This Post
Frans
Guru
posted Hide Post
In addition, you often see this when you have a piece of dynamic code, like a loop, that is creating a lot of code.


Test: WF 8.2
Prod: WF 8.2
DB: Progress, REST, IBM UniVerse/UniData, SQLServer, MySQL, PostgreSQL, Oracle, Greenplum, Athena.
 
Posts: 454 | Location: Europe | Registered: February 05, 2007Report This Post
Wep5622
Virtuoso
posted Hide Post
...Or when a field value overflows the data type of the field in the master file.


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 :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
LarissaB
Gold member
posted Hide Post
Our environment gives the same message if we use one to many joins on large tables. Since we have yet to find a really solid reason to use one to many joins, we've just made sure to use unique one to one joins and have not received that error since. We had also increased our setting on the client admin console for Max messages and still got the errors. Never set it to 0 however, since the message is generated for a reason.


Version: 8.2.03M, OS/Platform: Windows 7 & 10, Output: Excel, pdf, html
 
Posts: 63 | Location: Liberty Lake, WA - USA | Registered: June 23, 2016Report This Post
spp_123
Member
posted Hide Post
Thank you everyone for your responses. The problem was caused by incompatible format usages verses actual format in the master table. I noticed another field had the exact same dropdown options from the same Survey Monkey survey, but the formats were different in the master table. I changed the problematic field from TX256 to A255V (Usage) - which matches the other similar field that works. This change removed the error and the field is now showing the correct data.


WebFocus 8105, Windows 2016, HTML
 
Posts: 10 | Registered: September 11, 2017Report This Post
TobyMills
Gold member
posted Hide Post
Thanks for the follow up. Glad you have it all fixed up now.

Just for future refernce, if you typed in your exact error text in techsupport you would have found:

Report fails with error message "Too Many Messages"

After reading your post, I noticed nobody asked what your error message was. Sounds like you have it all squared away.

When you get a specific error message from WF, it's worth surrounding it in " quote marks and putting it in the techsupport search engine.

Toby
 
Posts: 62 | Registered: October 31, 2006Report This Post
MartinY
Virtuoso
posted Hide Post
quote:
Just for future refernce, if you typed in your exact error text in techsupport you would have found: Report fails with error message "Too Many Messages"


Hi Toby,
The "Too many messages" error may be caused by several things and may not be caused by a coding error. Just too many warning message or traces (-TYPE) may cause that especially when you have a loop and have &ECHO = ALL.
It basically tell you that you have exceed the maximum number of message set at : Administration Console/Configuration/Client Settings/General/IBIF_max_messages.

So except if you know which log to look at (and it's normally not the case especially for someone new with FOCUS) you may search for ever.
Using the debugging technic such as using SET &ECHO = ALL and limiting the number of data may help.

No offense, just to clarify.


WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF
In Focus since 2007
 
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] IBFSException 6000: Too Many Messages

Copyright © 1996-2020 Information Builders