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,

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.

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.

In addition, you often see this when you have a piece of dynamic code, like a loop, that is creating a lot of code.

...Or when a field value overflows the data type of the field in the master file.

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.

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.

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

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.