Error: 7884, Severity: 20, State: 1. (Params:). The error is printed in terse mode because there was error during formatting.

Tilicho 1 Reputation point
2021-09-14T20:04:16.377+00:00

Error seen:
Error: 7884, Severity: 20, State: 1. (Params:). The error is printed in terse mode because there was error during formatting.

This is for 2014 SQL server with alwaysOn group that hosts databases for Sharepoint. All are virtual machines on esxi. Over a week back this noticed popped up (the server has been in production for about two years and first time witnessing the error). Ran consistency check on the databases and no errors.

The error popped up again after a week yesterday. Ran checksum and no errors. And again this afternoon.

I have gone through numerous links in the web and none seem to be helpful. There are no errors in sql log prior to or after that one particular error shows. No error in event viewer either during that time.

Looking at sessions, one time the session id seem to point the web front end of sharepoint as source with secure store database as backend. Second time the session id showed the application server as source that was using the search database.

https://social.msdn.microsoft.com/Forums/en-US/5d9a6149-043b-4fed-9909-078b7b870239/the-error-is-printed-in-terse-mode-because-there-was-error-during-formatting?forum=sqldatabaseengine

wasn't helpful in that it talks about sql profiler (since the error is sporadic running profiler forever doesn't help) and also the microsoft connect sites some of these articles references are no longer in use. I have "googled" and not found anything substantial.

Any tips or recommendations would be appreciated.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,141 questions
Transact-SQL
Transact-SQL
A Microsoft extension to the ANSI SQL language that includes procedural programming, local variables, and various support functions.
4,586 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Erland Sommarskog 104.3K Reputation points MVP
    2021-09-14T21:32:37.2+00:00

    Rather than using Profiler, you can use an Extended Events session. This is useful so far, that you can capture only the even error_reported, but with this event also get the statement which produced this error. This is difficult to achieve with Trace/Profiler.

    I have an article on my web site on how to set up such an event session and how to query it: https://www.sommarskog.se/Short%20Stories/trace-exceptions.html.


  2. Tom Phillips 17,721 Reputation points
    2021-09-15T11:49:35.863+00:00

    This kind of error is almost always related to a memory allocation error. I would try reducing your max server memory setting a little and see if you get a real error message.

    0 comments No comments

  3. Erland Sommarskog 104.3K Reputation points MVP
    2021-09-23T21:42:39.437+00:00

    I don't think we come any further with this. If you want to know more, I think you need to open a support case. Which means that you must have purchased extended support, since you are on SQL 2014. To me, this seems like something internal in SQL Server.

    Then again, beside the mystery, have you any real problems with things not working properly?