December 14, 2011 at 9:35 pm
Hi All,
In DB Server i am getting below error.
Event Id : 18053
Error: 17066, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
How to resolve this error?What is the rootcause for this error.
Please reply.
December 14, 2011 at 11:25 pm
Appreciate for quick replay. Is it critical issue.
December 15, 2011 at 2:06 am
the standard SQL error messages are held in master db, so you can execute this
select *
from master..sysmessages
where error in (18053,17066)
and msglangid=1033-- English (substitute yours or comment this whole line)
order by error
so I deduce some overrun (system producing warning/ETW/Profiler messages quicker than you are able to consume them so has to drop some to avoid the subject workload suffering)
Example: you are running Profiler to record all events with no filtering to your PC over a slow network.
Appropriate action would be to do server-side tracing and/or reduce (filter) the number of events that you want to receive. Also stop tracing when you have captured the event you care about as overhead especially if you're not going to analyse the captured data.
HTH
Dick
PS congrats to Jeff Moden for winning X-DBA, but at least I answered this thread before he jumped in (phew!)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply