The error is printed in terse mode because there was error during formatting

On Wednesday, the monitoring tool sent an alert on an instance which was running low on memory. The alert read

Error: 14667, Severity: 16, State: 1. (Params:).
The error is printed in terse mode because there was error during formatting.
Tracing, ETW, notifications etc are skipped.

This instance is running SQL Server 2005 and I realized that we just bumped on a bug. As per this BUG listed for SQL Server 2005, this error message is generated because of an incorrect line the code of sp_readrequest stored procedure in MSDB database.

SET @localmessage = FORMATMESSAGE(14667, convert(NVARCHAR(50), @mailitem_id))

should be changed to

SET @localmessage = FORMATMESSAGE(14667,  @mailitem_id)

This error message does not mean anything critical, I started receiving few more extra alerts in my already flooded mailbox. Hence a Change Control has already been processed to modify this stored procedure as suggested.

I quickly looked up in SQL Server 2008 to see if this BUG has been fixed or not. Not yet. Even SQL Server Denlai still has the same line in sp_readrequest stored procedure. I am trying to inform about this BUG on MS Connect but due to some reasons I am unable to create a new feedback. Not a great BUG to report but fixing this would surely reduce some unwanted emails in the DBA’s inbox.

Update:

Aaron Bertrand (blog | twitter) has just posted a BUG on MS Connect regarding this. Please vote up for it here. Thanks Aaron for your help!

One thought on “The error is printed in terse mode because there was error during formatting

  1. Pingback: Tweets that mention The error is printed in terse mode because there was error during formatting | SQL Server DBA Diaries of Pradeep Adiga -- Topsy.com

Comments are closed.